perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Brian Candler writes:

    After a "yum upgrade" of a 4.1 node which was a few months old (I think 
    it went for 4.1.2 to 4.1.4), I got the following error after sudo to root:
    ...
    reason:         pidfile.py:48:__exit__:OSError: [Errno 13] Permission 
    denied: '/run/pscheduler-ticker.pid'
    ...
    uid:            1000 (pscheduler)
    ...    
    # ls -l /run/pscheduler-ticker.pid
    -rw-r--r-- 1 pscheduler pscheduler 4 Dec 10 21:45 
/run/pscheduler-ticker.pid
    
    # ls -ln /run/pscheduler-ticker.pid
    -rw-r--r-- 1 1000 1000 4 Dec 10 21:45 /run/pscheduler-ticker.pid
    
    # ls -ld /run
    drwxr-xr-x 39 root root 1400 Dec 11 08:12 /run
 
All of that looks correct.  The PID files are created and chowned by the 
systemd service file (see /usr/lib/systemd/system/pscheduler-ticker.service) 
as root prior to the daemon starting.  The last change to anything related to 
starting programs was in August's 4.1(.0) release.  4.1.3 and 4.1.4 were 
almost non-events for pScheduler, so this shouldn't be anything related to 
the upgrade.

Are you seeing this just for the ticker or for the other pScheduler services 
as well?  Is the system a stock toolkit or have there been site-specifc 
changes made to the system?  Is there a ticker running?  Anything in 
/var/log/pscheduler/pscheduler.log other than the complaint about the failure?

--Mark