perfSONAR User Q&A and Other Discussion

[Pete LG <>]

Hey Andrew, Sorry, I just saw your reply.  I think I caused a lot of confusion with my initial question.  I was concerned about the directory being owned by root:root /etc/maddash*

I can confirm that while the directories ARE owned by root, psconfig is able to populate maddash-server with grids owned by "maddash:maddash".

The original machine I was working on had been an older 4.0.x that had grids written by hand, so I think the perms were just left over and broken from the 4.1.5 update.  When I changed the ownership 'chown -R maddash:maddash /etc/maddash, it allowed it all to complete.  However, on the new box I just used psconfig, and left the directory alone, it it seems to populate it just fine:

I think were good.  I appreciate you looking into this!

Pete

Pete LG

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Thursday, January 31, 2019 5:29 PM, Andrew Lake <> wrote:

Hi,

I have had some time to play with this today and so far haven’t been able to recreate. No matter what I do I get a file owned by the “maddash” group and user as I’d expect. I’ll share the steps I followed so you can compare to the steps you followed and see if we differ:

1. I did a fresh Minimal install of CentOS 7

2. I ran the commands from the docs (http://docs.perfsonar.net/maddash_install.html#installing-maddash-on-centos):

    yum install epel-release http://software.internet2.edu/rpms/el7/x86_64/main/RPMS/perfSONAR-repo-0.8-1.noarch.rpm

    yum clean all

    yum install maddash

3. I installed the psconfig maddash agent with “yum install perfsonar-psconfig-maddash"

I also tried various combinations of removing the file before I installed a package but no luck. It might be something subtle that triggers it, so any insight in how you are able to get the behavior would be appreciated.

Thanks,

Andy

On January 29, 2019 at 6:13:12 PM, Pete LG () wrote:

Hey Andrew, It's on a vanilla CentOS7.  I appreciate you looking into this. 

Thanks!

Pete LG

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Tuesday, January 29, 2019 7:44 PM, Andrew Lake <> wrote:

Hi,

Thanks for the report, that is not expected behavior. A quick look at the .spec file indicates that it *should* be getting set to the maddash user on install. It is possible something else is creating that file first and not setting the permission correctly...though it is not immediately obvious to me what that would be. I’ve created an issue for it here to track: https://github.com/perfsonar/maddash/issues/76. We will investigate and have a closer look. Due to travel schedules it may not be until next week sometime, so apologies in advance for any delay.

Also, on what operating system are you seeing this behavior?

Thanks,

Andy

On January 29, 2019 at 12:03:22 PM, Pete Carmichael () wrote:

Hi, Are we supposed to need to "chown -R maddash:maddash /etc/maddash"?

It was the only way I could get the grid to populate.  On new setups, the perms are 'root:root', but I was having issues generating a new maddash grid, and I noticed this in the logs:

/var/log/maddash/psconfig-maddash-agent.log

2019/01/29 13:12:17 ERROR pid=5911 prog=perfSONAR_PS::PSConfig::MaDDash::Agent::_save_maddash_yaml line=984 guid=A3651200-23F9-11E9-BF77-FFA92F96E832 maddas

h_yaml_file=/etc/maddash/maddash-server/maddash.yaml msg=Can't open /etc/maddash/maddash-server/maddash.yaml: Permission denied at /usr/lib/perfsonar/bin/..

/lib/perfSONAR_PS/PSConfig/MaDDash/Agent.pm line 979. 

Any ideas on what's going on?

Thanks

--

To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user