Description of problem: 1. You want to start up an additional condor_schedd in a multiple condor_schedd and HA environment. 2. You add configuration for the condor_schedd to both HA nodes. 3. "condor_reconfig" doesn't launch the newly configured condor_schedd. A restart of the condor_master process is required. This requires you to perform an unnecessary HA failover, which is an expensive and production-impacting process. Unless I'm missing a way to accomplish this by other means. How reproducible: 100% Steps to Reproduce: See above. Actual results: See above Expected results: "condor_reconfig -master" should launch any additional daemons added to the configuration.
A condor_reconfig -master will now stop and daemons removed from, and start daemons added from, DAEMON_LIST since master was last configured/started. Fixed in: condor-7.4.3-0.8
condor_master acts as decribed in comment 1. Verified on RHEL 4.8/5.5, i386,x86_64. condor-7.4.4-0.16
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, "condor_reconfig" didn't launch the newly configured condor schedduler daemon and a restart of the condor_master process was required. With this update, "condor_reconfig -master" allows the user to launch any additional daemons added to the configuration.
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