Description of problem: Occasionally, "service condor stop" will not stop condor. It appears as if the SIGQUIT signal used to shutdown condor is not being acted upon. Version-Release number of selected component (if applicable): RHEL4 condor*-7.4.4-0.4.el4 How reproducible: Rare. Seen only on first attempted shutdown after system boot. Cannot repro if first "service condor stop" is successful. Steps to Reproduce: 1. boot RHEL 4 system, with condor started as a service 2. use condor configuration as specified in https://bugzilla.redhat.com/show_bug.cgi?id=610773 3. watch /var/log/MasterLog - should see SIGQUIT log message when "service condor stop" done, otherwise condor will not shutdown Actual results: service condor stop fails with an error message. Expected results: service condor stop should succeed and all condor processes should have exited cleanly. Additional info: See https://bugzilla.redhat.com/show_bug.cgi?id=610773 for additional information.
What is the error message? Does the MasterLog say if a signal was received?
The only error message - actually, warning - I have seen is the failure of the condor stop command: [kgiusti@localhost ~]$ sudo /sbin/service condor stop Password: Stopping Condor daemons: [ OK ] Warning: condor_master may not have exited, start/restart may fail No, the MasterLog shows no activity whatsoever during the failed shutdown. During a successful shutdown, the log will contain the following log message: 07/16 08:36:57 Got SIGQUIT. Performing fast shutdown. When the failure occurs, there is NO new activity in the master log. It appears as if the signal is lost/blocked.
What was the state of the broker when stopping Condor?
Possibly related to Bug 625450
Strike comment 4
Ken said broker was present, but the primary issue included no mention of SIGQUIT being received by the master.