Red Hat Bugzilla – Bug 543021
Unable to restart collector with condor_restart on remote node
Last modified: 2010-10-14 12:15:11 EDT
Description of problem: Unable to restart collector remotely by condor_restart -subsystem collector -name <target hostname> see https://bugzilla.redhat.com/show_bug.cgi?id=518292#c11 Version-Release number of selected component (if applicable): condor-7.4.1-0.7 How reproducible: 100% Steps to Reproduce: 1. set up condor pool 2. condor_restart -subsystem collector -name <target hostname>
The issue was that the collector was using COLLECTOR_NAME as the name in it's daemon ad, which is assumed to be a resolvable hostname. So if COLLECTOR_NAME was explicitly set to "Bob's Pool", the daemon ad's name would be "Bob's Pool", which obviously isn't resolvable. The collector will now append @FQDN to the COLLECTOR_NAME if the COLLECTOR_NAME does not contain an @, otherwise it is assume the name is valid and will use whatever COLLECTOR_NAME is set to. If COLLECTOR_NAME does not contain a resolvable hostname, then it will not be possible to restart/reconfig a collector remotely. Fixed in build after: condor-7.4.1-0.7.1
Fixed in 7.4.2-0.1
I've tried it with condor-7.4.3-0.13.el5 and condor-7.4.3-0.11.el4 and it works. I cannot move this bug to modified, because those ones are still only devel packages.
Teste on RHEL5.5/4.8 x i385/x86_64 with condor-7.4.3-0.17 and it works. -->VERIFIED
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: Previously, a collector could not be remotely restarted using the "condor_restart -subsystem collector -name <target hostname>" command. With this update, the restart is possible and works as expected.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Previously, a collector could not be remotely restarted using the "condor_restart -subsystem collector -name <target hostname>" command. With this update, the restart is possible and works as expected.+Previously, a collector could not be remotely restarted. With this update, the restart is possible and works as expected.
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/RHSA-2010-0773.html