Re: [Condor-users] .master_address on Windows 7 ( 7.5.6)

["Wilding, Kevan A" <kwilding@xxxxxxxxxxx>]

You are correct. Windows 7 has a delayed automatic start option which will fix this problem.

Kevan

 

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Andrew Cunningham
Sent: 19 July 2011 16:44
To: Condor-Users Mail List
Subject: [Condor-users] .master_address on Windows 7 ( 7.5.6)

 

Occasionally when a Windows 7 machine is restarted the condor master "thinks" its IP address  is 169.254.243.121 ( it should be 192.168.0.121)

07/18/11 16:46:48 ******************************************************
07/18/11 16:46:48 ** condor (CONDOR_MASTER) STARTING UP
07/18/11 16:46:48 ** C:\condor\bin\condor_master.exe
07/18/11 16:46:48 ** SubsystemInfo: name=MASTER type=MASTER(2) class=DAEMON(1)
07/18/11 16:46:48 ** Configuration: subsystem:MASTER local:<NONE> class:DAEMON
07/18/11 16:46:48 ** $CondorVersion: 7.5.6 Mar 13 2011 BuildID: 319722 $
07/18/11 16:46:48 ** $CondorPlatform: x86_winnt_5.1-tst $
07/18/11 16:46:48 ** PID = 1232
07/18/11 16:46:48 ** Log last touched time unavailable (No such file or directory)
07/18/11 16:46:48 ******************************************************
07/18/11 16:46:48 Using config source: C:\condor\condor_config
07/18/11 16:46:48 Using local config sources:
07/18/11 16:46:48    C:\condor/condor_config.local
07/18/11 16:46:48 DaemonCore: command socket at <169.254.243.121:49157>

Restarting the condor service corrects the problem.

All I can think is that the condor service is starting before the machine has had a chance to get its IP from the DHCP server.