Re: [Condor-users] MasterLog entries -- what does it mean> - should I worry?

[Rob Fletcher <rpf1@xxxxxxxxxx>]

On Tue, 7 Jun 2005, Rajesh Rajamani wrote:

>
> Rob Fletcher wrote:
> > Hi,
> >
> > In my MasterLog file I get these entries ...
> >
> > 6/7 10:56:51 New Daemon obj (negotiator) name: "NULL", pool: "NULL", addr: "NULL"
> > 6/7 10:56:51 NEGOTIATOR_HOST is set to "192.168.0.3"
> > 6/7 10:56:51 Using name "192.168.0.3" to find daemon
> > 6/7 10:56:51 Port not specified, using default (9614)
> > 6/7 10:56:51 Host info "192.168.0.3" is an IP address
> > 6/7 10:56:51 Destroying Daemon object:
> > 6/7 10:56:51 Type: 6 (negotiator), Name: 192.168.0.3, Addr: <192.168.0.3:9614>
> > 6/7 10:56:51 FullHost: (null), Host: (null), Pool: (null), Port: 9614
> > 6/7 10:56:51 IsLocal: Y, IdStr: (null), Error: (null)
> > 6/7 10:56:51  --- End of Daemon object info ---
>
> Hi Rob,
> What this means is that condor is unable to find a hostname for your
> machine 192.168.0.3.  Do you have a DNS server configured for your
> network?  If you don't, you could try adding an entry for 192.168.0.3 in
> your /etc/hosts file.
>
> Condor relies heavily on the DNS and we would recommend that you set one
> up (if you don't have one already).
> --

Hi Thanks,

The setup is purely local (bar the master linux node with 2 interfaces).
So, only the outward facing interface is known to the campus DNS services.

I did have all addresses and machines in the hosts file (ie the outward
facing interface and the 4 xp machines).

BUT ... I did not have the inward facing 192.168.0.3 interface in this
file ...

Adding it solved this ... AND ... for other readers ...

My condor_status and condor_q commands now go like the wind (wereas they
has previously been stalling!).

Thanks again, all part of the learning process.

Regards,

Rob