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

Re: [Condor-users] Flocking Issues

This can be further clarified with an excerpt from the flocking source's schedd log

flock_to negotiatorlog:

11/2 10:56:24 Phase 4.1: Negotiating with schedds ...
11/2 10:56:24 Negotiating with user@xxxxxxxxxx at <x.x.x.x:9640>
11/2 10:56:29 condor_read(): recv() returned -1, errno = 10054, assuming failure.
11/2 10:56:29 Failed to get reply from schedd
11/2 10:56:29 Error: Ignoring schedd for this cycle

flock_from scheddlog:

11/3 11:26:58 DaemonCore: Command received via TCP from host <y.y.y.y:9684>
11/3 11:26:58 DaemonCore: received command 416 (NEGOTIATE), calling handler (negotiate)
11/3 11:27:00 Unknown negotiator (<y.y.y.y:9684>). Aborting negotiation.

when y.y.y.y is definitely in FLOCK_TO, and the default settings put it in FLOCK_NEGOTIATOR_HOSTS and HOSTALLOW_NEGOTIATOR_SCHEDD as well. Can anyone tell me why it thinks that it is *not* in there? (my original problems with windows condor point me towards dns stuff, and y.y.y.y as an IP will *not* resolve to anything.... help?)