[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] starter failed to connect to collector
- Date: Fri, 14 Oct 2005 11:19:21 +0100
- From: Matt Hope <matthew.hope@xxxxxxxxx>
- Subject: Re: [Condor-users] starter failed to connect to collector
On 10/14/05, DeVoil, Peter <Peter.DeVoil@xxxxxxxxxxxxxx> wrote:
> I have a few machines in a 30 node winXP pool that refuse to start jobs.
> I see these in the starter log:
> 10/14 14:59:38 vm2: Received match <192.168.0.162:1353>#4441711918
> 10/14 14:59:38 vm2: State change: match notification protocol successful
> 10/14 14:59:38 vm2: Changing state: Unclaimed -> Matched
> 10/14 15:01:38 vm2: State change: match timed out
> 10/14 15:01:38 vm2: Changing state: Matched -> Owner
> 10/14 15:01:38 vm2: State change: IS_OWNER is false
> 10/14 15:01:38 vm2: Changing state: Owner -> Unclaimed
> 10/14 15:04:50 DaemonCore: Command received via TCP from host
> 10/14 15:04:50 DaemonCore: received command 442 (REQUEST_CLAIM), calling
> handler (command_request_claim)
> 10/14 15:04:50 Error: can't find resource with capability
> and also (after reboot):
> 10/14 16:32:17 Error sending update to the collector : Failed to connect
> to collector
> 10/14 16:32:17 vm2: Error sending update to collector(s)
> 10/14 16:34:18 bind failed: WSAError = 10049
> Any suggestions where to start? wipedisk? (its been a long day...)
Error Number: 10049
Cannot assign requested address.
The requested address is not valid in its context. Normally
results from an attempt to bind to an address that is not
valid for the local machine, or connect/sendto an address
or port that is not valid for a remote machine.
Hope this points you in the right direction...