Description of problem:
During reproducing of 667911 I've tried to stop broker on remote configuration server. Configd has started after restarting of Condor and it has tried to connect to broker:

01/25 13:15:24 INFO: Starting Up
01/25 13:15:24 INFO: Hostname is "..."
01/25 13:15:24 INFO: Cleaning up temporary configuration files
01/25 13:15:24 DEBUG: "QMF_BROKER_PORT" is not defined. Using default (5672)
01/25 13:15:24 DEBUG: "QMF_BROKER_AUTH_MECHANISM" is not defined. Using defaults
01/25 13:15:24 DEBUG: Writing configuration file to "/var/lib/condor/wallaby_node.config"
01/25 13:15:25 DEBUG: Connected to broker "..:5672"
01/25 13:15:25 DEBUG: Looking for the store agent

There is information about that configd is connected to broker, but that cannot be true because broker doesn't run.

Before I've switch off broker, I set up pool by remote configuration:
Group "Internal Default Group":
Group ID: 1
Name: Internal Default Group
Features (priority: name):
  0: Master
  1: NodeAccess
  2: ExecuteNode
Parameters:
  ALLOW_WRITE = *
  CONDOR_HOST = ...
  ALLOW_READ = *

Version-Release number of selected component (if applicable):

I see it in:
condor-wallaby-client-3.6-6  RHEL 4/5 x i386/x86_64
condor-7.4.4-0.17
qpid-cpp-server-0.7.946106-22
qpid-cpp-client-0.7.946106-22
python-condorutils-1.4-5
python-qmf-0.7.946106-14
python-qpid-0.7.946106-14
python-wallabyclient-3.6-6

and also in:
condor-7.4.5-0.7.el5
condor-wallaby-client-3.9-2.el5 RHEL 4/5 x i386/x86_64
condor-wallaby-tools-3.9-2.el5
python-condorutils-1.4-6.el5
qpid-cpp-client-0.7.946106-27.el5
python-qpid-0.7.946106-15.el5
qpid-cpp-server-0.7.946106-27.el5

How reproducible:
100%

Steps to Reproduce:
1. set up condor pool by remote configuration
2. add Master,NodeAccess,ExecuteNode (it is the similar without any features on nodes, but this is more ordinary usage of remote configuration, I think)
3. service stop qpidd
4. check /var/log/condor/ConfigdLog
  
Actual results:
It seems that configd is connected to broker which is down.

Expected results:
If configd doesn't connect to broker properly, it start to trying to connect again and again until CONFIGD_CHECK_INTERVAL and addBroker function raise exception.

Additional info:
I think this bug is more QMF bug, because if I've modified code around "Connected to broker":

try:
  self.broker = self.session.addBroker('amqp://%s' % broker_str, mechanisms=broker_auth_methods)
except:
  if stop_running == False:
    log(logging.CRITICAL, self.logger_name, 'Unable to connect to broker "%s"' % broker_str)
    return(False)

log(logging.DEBUG, self.logger_name, 'Connected to broker "%s", %s' % (broker_str, str(self.broker)))
return(True)

I've got "01/25 13:33:30 DEBUG: Connected to broker "10.34.37.168:5672", Disconnected Broker"


but strange thing is that if I connect manually, I get exception:
$ python
>>> import qmf.console
>>> session = qmf.console.Session()
>>> b=session.addBroker('amqp://localhost:5672', mechanisms='ANONYMOUS') #it doesn't matter if there is ip, localhost or hostname 
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.4/site-packages/qmf/console.py", line 639, in addBroker
    ssl = url.scheme == URL.AMQPS, connTimeout=timeout)
  File "/usr/lib/python2.4/site-packages/qmf/console.py", line 2070, in __init__
    raise self.conn_exc
socket.error: (111, 'Connection refused')