perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Casey Russell writes:

 

     Since the install, I occasionally get emails from the (new) abrt-cli service in CentOS 7 complaining about a problem restarting the pscheduler-runner service.  It's clearly a permissions error, although I don't see what's wrong with the permissions.

 

That may have cropped up during the restart.  The systemd configuration creates the PID files as root and changes their ownership to pscheduler.  It’s possible that there was some overlap and the old copy of the daemon tried to remove it during that instant and threw an exception because of it on its way to exiting.  I’ve made adjustments that handle that in a better way; look for it in 4.0.2.  For now you can just ignore it.

 

If I hand restart pscheduler-runner, it takes a VERY long time (30 seconds or more) to shut down and the does appear to start again, since a "status" shows it running.

 

The long shutdown is a problem when the daemons have long-running external processes.  The init scripts we have for EL6 took care of it through brute force; the ones for EL7 don’t.  I’ll have a look at what I can do with that in EL7 and will shoot to release some improvements in 4.0.2.

 

--Mark