Hide Forgot
Description of problem: The configd won't timeout looking for the wallaby store agent. When run as a daemon it's not such a horrible thing, but when run with -r (to retrieve a config), this is bad as the command will never time out if there isn't a contactable wallaby. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Added CONFIGD_WALLABY_CONNECT_TIMEOUT, which defaults to 60 seconds, to control how long the configd will wait to contact wallaby on start up. This most evident when doing a one-off pull of the configuration. Fixed on: BZ745523-configd-timeout-no-wallaby
Just to be sure, does CONFIGD_WALLABY_CONNECT_TIMEOUT=0 mean "timeout immediately if not found" or "do not timeout"?
0 would result in "timeout immediately if not found", which would be immediately because it takes a few seconds to find the agent. A timeout of 0 isn't a good idea, and even if did somehow succeed could produce a spurious error message in the logs.
Reproduced on: condor-wallaby-client-4.0-4.el5 # time condor_configd -r real 4m34.851s user 0m0.429s sys 0m0.176s Retested on all supported platforms x86_64, x86 on RHEL5,RHEL6: condor-wallaby-client-4.1.2-1 # time condor_configd -r Error: Unable to retrieve configuration real 1m0.929s user 0m0.944s sys 0m0.338s Retrieving configuration timeout happened after default 60sec in condor_configd. >>> VERIFIED