Description of problem: The condor_schedd init script isn't removing the pidfile created when the schedd process is stopped through the condor_schedd script. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The condor_schedd.init script could leave a pidfile with an invalid pid in it if the schedd crashes. In this case, the pidfile would not be removed and would contain the pid of the crashed schedd. When the schedd is started via the init script, the schedd would still start but the pid file would still contain the pid of the previously crashed schedd. The pid file also wasn't removed when the schedd was stopped in these instances. The script now checks for the status of the process and removes the pidfile before starting. Fixed upstream
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: C: A condor_schedd managed by Red Hat High Availability crashes C: When the condor_schedd is restarted, the pid file will contain the pid of the previous instance and not the current instance. The pid file also will not be removed when the service is shutdown. F: The startup script will look for the existence of the pidfile and remove it before starting R: The pidfile will contain the pid of the running schedd and be removed if the schedd is shut down cleanly.
Tested on RHEL 6.2 x i386/x86_64 with condor-7.6.5-0.11 and condor-7.6.5-0.8 and it works. --> VERIFIED
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. http://rhn.redhat.com/errata/RHSA-2012-0100.html