Description of problem: The configd does not respond to a softkill if the BROKER_HOST is invalid Version-Release number of selected component (if applicable): condor-wallaby-4.0-4 How reproducible: 100% Steps to Reproduce: 1. Comment out BROKER_HOST 2. net stop condor 3. shutdown hangs until hardkill Expected results: clean shutdown on softkill
Issue was that the windows shutdown timer wasn't started until after the configd connected to the broker, so if the configd couldn't connect then the timer was never started. The timer is now started when other signal handlers are setup. Fixed on master.
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 mis-configured QMF_BROKER_HOST in condor's configuration C: The configd would be unable to contact the broker and wouldn't respond to shutdown commands F: Moved the windows signal handling initialization to earlier in the code path R: The configd will shutdown gracefully regardless of whether QMF_BROKER_HOST is configured correctly
The issue does not occur on version "condor-7.4-103_20110124.msi" (the last brewed version what can be running before the patch) neither on version "condor-7.6.1-0.8.msi". Tested on Windows: XP-x86 Server2003-x86 and x64 Server2008-x86, x64 and R2-x64 7-x86 and x64 --> 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/RHEA-2011-0889.html