After shutting down rhcert service with `rhcert-backend server stop`, .pid files referring to non-existent processes remain. redhat-certification-1.0-20150707.el7.noarch redhat-certification-hardware-1.7.1-20150625.el7.noarch reliably reproducible Steps to Reproduce: 1. install redhat-certification 2. `rhcert-backend server start` to create /var/rhcert and files in it 3. check contents of /var/rhcert/*.pid 4. `rhcert-backend server stop` 5. check /var/rhcert/*.pid again 6. compare with output from ps Actual results: # ls /var/rhcert tasks.in| tasks.out tasks-RedHatCertDaemon.pid tasks-RedHatCertificationListener.pid In certain cases, the .pid files can interfere with detection of running process in the tool itself. Looking for reproducible cases there, I've seen it happen once. Expected results: pid files erased on shutdown. This makes it possible to determine whether the daemons crashed or gracefully shutdown, indicating whether or not some types of errors occured and reflecting the actual state of the system. Additional info: pid files usually reside in /run (/var/run symlinked to there)
verified in redhat-certification-2.0-20150916.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2479.html