[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [condor-users] condor_status and condor_q failing
- Date: Wed, 17 Dec 2003 15:05:10 -0600
- From: Zachary Miller <zmiller@xxxxxxxxxxx>
- Subject: Re: [condor-users] condor_status and condor_q failing
On Tue, Dec 16, 2003 at 01:23:21PM -0500, Corey Shields wrote:
> CEDAR:6001:Failed to connect to <###.##.#.##:9618>
> Error: Couldn't contact the condor_collector on hostname.domainname.
i'm guessing that it's simply timing out because the collector is not
responding within 20 seconds.
add this to your condor_config:
TOOL_TIMEOUT_MULTIPLIER = 3
then it will wait up to a minute before giving up. you can also add this
to your condor_config:
TOOL_DEBUG = D_NETWORK D_SECURITY
or even more extreme:
TOOL_DEBUG = D_NETWORK D_SECURITY D_FULLDEBUG
and you will get more information.
> Also, when this happens, there is no corresponding entry in the MasterLog or
> CollectorLog to indicate a problem.
hmmm. i would expect to see something... try upping the debug level for the
collector in your condor_config:
COLLECTOR_DEBUG = D_NETWORK D_SECURITY D_DAEMONCORE D_COMMAND
if there really is no sign of it in the log, there is some problem than
a simple timeout. please let me know if that is the case.
Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>