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

RE: [Condor-users] XP SP2 reboot problem

Just for the record. A simple scheduled task, running net stop condor
and net start condor, say ten minutes after reboot fixes this problem.
Not perfect, but does the trick, I am hoping.

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Wilding, Kevan A
Sent: 15 November 2004 14:45
To: condor-users@xxxxxxxxxxx
Subject: [Condor-users] XP SP2 reboot problem

  A posting by Geraint recently spotted this problem, and I wonder
whether there is a work around?

  Using version 6.6.7

  Our Window Labs machines get rebooted every morning. As condor does
not shut down gracefully, on restarting the services do start, but
appear to do so before the firewall (?). Therefore, the condor system
will not work. If machines are restarted manually, they then state that
the firewall has been enabled, i.e.

11/10 10:57:15 Authorized application C:\Condor/bin/condor_schedd.exe is
now enabled in the firewall. 11/10 10:57:15 Authorized application
C:\Condor/bin/condor_startd.exe is now enabled in the firewall.

  Rather than:

11/10 08:33:59 WinFirewall: get_CurrentProfile failed: 0x800706d9

  Does anyone have a suggestion, apart from setting a separate job to
restart each machine, as it reboots?


Condor-users mailing list