Bug 761588 – condor_schedd.init script isn't removing pidfile

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 761588 - condor_schedd.init script isn't removing pidfile

Summary:	condor_schedd.init script isn't removing pidfile

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	condor (Show other bugs)
Sub Component:
Version:	2.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	2.1.1
Target Release:	---
Assigned To:	Robert Rati
QA Contact:	Martin Kudlej
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	765607
	Show dependency tree / graph

Reported:	2011-12-08 11:32 EST by Robert Rati
Modified:	2012-02-07 05:40 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	condor-7.6.5-0.10
Doc Type:	Bug Fix
Doc Text:	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.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-02-06 13:18:57 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2012:0100	normal	SHIPPED_LIVE	Moderate: MRG Grid security, bug fix, and enhancement update	2012-02-06 18:15:47 EST

Groups: None (edit)

Description Robert Rati 2011-12-08 11:32:46 EST

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:

Comment 1 Robert Rati 2011-12-13 10:48:26 EST

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

Comment 2 Robert Rati 2011-12-14 14:41:21 EST

    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.

Comment 5 Martin Kudlej 2012-01-09 10:38:28 EST

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

Comment 6 errata-xmlrpc 2012-02-06 13:18:57 EST

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

Note You need to log in before you can comment on or make changes to this bug.