[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Issue with connecting nodes to pool/master

On Tue, Jun 27, 2006 at 05:18:30PM -0400, Robert Wright wrote:
> Still have not figured how to get my problem resolved.. Below is a cat of
> NegotiatorLog on node0... TRANSLTR is at .102 and is the master.

First - some terminology - the "master" is a program, which runs on 
every machine. In a condor pool, there is one machine called the
"central manager", which runs a condor_collector and condor_negotiator.
You probably mean for you to be your central manager. 

What machine is the log file below from? You should only have
a NegotiatorLog on one machine, the central manager.

Errno 113 is "No Route To Host". Do you have your networking properly
configured (ie can you ping your central manager from all your other 

The interesting logfiles are the CollectorLog from your central 
manager, and a StartdLog file from an execute node.


> 6/21 09:48:02 Phase 1:  Obtaining ads from collector ...
> 6/21 09:48:02   Getting all public ads ...
> 6/21 09:48:02 Can't connect to <>:0, errno = 113
> 6/21 09:48:02 Will keep trying for 10 seconds...
> 6/21 09:48:12 Connect failed for 10 seconds; returning FALSE
> 6/21 09:48:12 Couldn't fetch ads: communication error
> 6/21 09:48:12 Aborting negotiation cycle
> could someone please take a look at my configs?

> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> The archives can be found at either
> https://lists.cs.wisc.edu/archive/condor-users/
> http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR