Bug 474446
Summary: | init script restart doesn't always restart condor | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Robert Rati <rrati> |
Component: | grid | Assignee: | Matthew Farrellee <matt> |
Status: | CLOSED ERRATA | QA Contact: | Jeff Needle <jneedle> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | CC: | matt |
Target Milestone: | 1.1 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-04 16:06:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert Rati
2008-12-03 21:30:40 UTC
This is likely the result of switching to -QUIT the condor_master. When killproc is given a signal it never sleep while stopping the daemon. The lack of sleep means that on a restart (which is stop + start) the condor_master still exists when start is executed. The result is start bails out and the condor_master eventually exists. It's probably sufficient to add a sleep 5 (which is the killproc delay) to stop() in the init script. Though that's kinda sad. Actually, when you pass a signal to killproc() it no longer rm's the pidfile for you, so stop() must do that itself. This is address in dffb2e11, will be part of 7.2.0-0.8 I'll buy this, based on code inspection and the fact that I haven't run into this recently. No state "SEEMS_TO_BE_VERIFIED", so moving to VERIFIED. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0036.html |