[Condor-users] {Disarmed} RE: Condor Startup Issue on Windows

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

Hi,

    We had this problem with XP with earlier versions, and we restarted Condor after a reboot. In Windows 7 there is an automatic delayed start that is available which cured this problem. Without this, most machines were starting too quickly and getting a local ip-address.

Kevan

 

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Willem Hough
Sent: 22 October 2010 09:17
To: condor-users@xxxxxxxxxxx
Subject: [Condor-users] Condor Startup Issue on Windows

 

Hi,

 

I experience problems starting Condor on some Windows XP and Windows 7 machines. Shown below is part of my MasterLog file when the problem occurs.

 

Condor is started via a Windows automatic start service. My suspicion is the Condor service is started before the Windows networking has initialised properly (DaemonCore: Command Socket at 169.254.237.49 is incorrect and the inability to ping the server address segcondor.kentron.co.za).

 

I also notice the Condor Service has no startup dependencies associated with it (TCP/IP, DNS, etc).

 

Can anyone confirm my suspicion? On Windows 7 there is a work-around to this problem by using the "Automatic (Delayed Start)" way of starting a process.

 

Regards

 

 

 

 

================

Contents of MasterLog

================

 

 

10/22 07:40:57 Locale: English_United States.1252
10/22 07:40:57 ******************************************************
10/22 07:40:57 ** Condor (CONDOR_MASTER) STARTING UP
10/22 07:40:57 ** C:\condor\bin\condor_master.exe
10/22 07:40:57 ** SubsystemInfo: name=MASTER type=MASTER(2) class=DAEMON(1)
10/22 07:40:57 ** Configuration: subsystem:MASTER local:<NONE> class:DAEMON
10/22 07:40:57 ** $CondorVersion: 7.4.4 Oct 13 2010 BuildID: 279383 $
10/22 07:40:58 ** $CondorPlatform: INTEL-WINNT50 $
10/22 07:40:58 ** PID = 1716
10/22 07:40:58 ** Log last touched time unavailable (No such file or directory)
10/22 07:40:58 ******************************************************
10/22 07:40:58 Using config source: C:\condor\condor_config
10/22 07:40:58 Using local config sources:
10/22 07:40:58    C:\condor/condor_config.local
10/22 07:40:58 DaemonCore: Command Socket at <MailScanner warning: numerical links are often malicious: 169.254.237.49:49157>
10/22 07:40:58 Authorized application C:\condor\bin\condor_master.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_schedd.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_shadow.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_gridmanager.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_c-gahp.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_c-gahp_worker_thread.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_startd.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_kbdd.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_starter.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin/condor_vm-gahp.exe is now enabled in the firewall.
10/22 07:40:58 Authorized application C:\condor/bin\condor_dagman.exe is now enabled in the firewall.
10/22 07:40:59 Started DaemonCore process "C:\condor/bin/condor_schedd.exe", pid and pgroup = 1076
10/22 07:40:59 Started DaemonCore process "C:\condor/bin/condor_startd.exe", pid and pgroup = 1840
10/22 07:40:59 Started DaemonCore process "C:\condor/bin/condor_kbdd.exe", pid and pgroup = 324
10/22 07:40:59 IPVERIFY: unable to resolve IP address of segcondor.kentron.co.za
10/22 07:41:04 Failed to start non-blocking update to unknown.
10/22 08:40:59 Preen pid is 3532
10/22 08:40:59 ERROR: Child pid 324 appears hung! Killing it hard.
10/22 08:41:19 attempt to connect to <MailScanner warning: numerical links are often malicious: 169.254.237.49:49161> failed: timed out after 20 seconds.
10/22 08:41:19 Send_Signal: Warning: could not send signal 15 (SIGTERM) to pid 324 (still alive)

etc.....