AW: [Condor-users] StarterAbilityList and Windows XP SP2

[Björn Baumeier <baumeier@xxxxxxxxxxxxxxxxxxx>]

Update:

As it seems, the group policy is not guilty of causing the problems I
described earlier today. We have now succeeded in joining another computer
to the condor pool running Windows XP SP2 which is configured by the same
policy settings. Still, the test machines we have been using until now have
the problem, which after consulting the file StartLog, one can see:

12/1 14:32:04 ******************************************************
12/1 14:32:04 ** condor_startd.exe (CONDOR_STARTD) STARTING UP
12/1 14:32:05 ** C:\Condor\bin\condor_startd.exe
12/1 14:32:05 ** $CondorVersion: 6.6.7 Oct 14 2004 $
12/1 14:32:05 ** $CondorPlatform: INTEL-WINNT40 $
12/1 14:32:05 ** PID = 524
12/1 14:32:05 ******************************************************
12/1 14:32:05 Using config file: C:\Condor\condor_config
12/1 14:32:05 Using local config files: C:\Condor/condor_config.local
12/1 14:32:05 DaemonCore: Command Socket at <128.176.*.*:2572>
12/1 14:32:05 Failed to execute C:\Condor/bin/condor_starter.exe, ignoring
12/1 14:32:05 Failed to execute C:\Condor/bin/condor_starter.pvm, ignoring
12/1 14:32:05 Failed to execute C:\Condor/bin/condor_starter.std, ignoring
12/1 14:32:05 New machine resource allocated
12/1 14:32:10 About to run initial benchmarks.
12/1 14:32:20 Completed initial benchmarks. 

So, the condor_starter.exe fails. On the machine we managed to join to the
pool, only condor_starter.pvm and condor_starter.std fail - which I
understand should be expected under Windows.
The two mentioned machines are one old Pentium II and a Pentium III
notebook. Condor version is 6.6.7.

If anybody has any ideas what may have caused this failure, please let me
know.

Bjoern


------------------------------------------------------
Björn Baumeier		baumeier@xxxxxxxxxxxxxxxxxxx
Universität Münster
Institut für Festkörpertheorie
Wilhelm-Klemm-Strasse 10
D-48149 Münster
Tel. +49 251 83 - 33583
------------------------------------------------------ 
 
-----Ursprüngliche Nachricht-----
Von: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] Im Auftrag von Björn Baumeier
Gesendet: Mittwoch, 1. Dezember 2004 10:11
An: condor-users@xxxxxxxxxxx
Betreff: [Condor-users] StarterAbilityList and Windows XP SP2

Hello!

So far we are successfully running a Condor pool consisting mainly of
Windows 2000 workstations within an Active Directory domain. However, we
have encountered some trouble trying to get Condor to work under Windows XP
SP2 in this environment. 

While the resprective machines are visible in the pool, submitting jobs to
them fails. We have added the various condor executables to the SP2 firewall
exception list. However, the firewall doesn't seem to be the cause of the
trouble because the problem persists even when the firewall is deactivaed.

"condor_q -ana" shows that the XP machines do not match the requirements.
Specifically, they don't have "HasFileTransfer". 
"condor_status -long" reveals that the whole "StarterAbilityList" entry
remains empty. 

Using two computers that are not members of the AD domain was no problem. 

We now suspect that the domain configuration by group policy is the cause of
the problem. However, we don't now where to look exactly and group policy is
big. 

It might be helpful to know how and when condor determines the
"StarterAbilityList" so that we can pinpoint the interfering settings. 

Any help in this regard is welcome.

Bjoern

------------------------------------------------------
Björn Baumeier		baumeier@xxxxxxxxxxxxxxxxxxx
Universität Münster
Institut für Festkörpertheorie
Wilhelm-Klemm-Strasse 10
D-48149 Münster
Tel. +49 251 83 - 33583
------------------------------------------------------ 
 


_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
http://lists.cs.wisc.edu/mailman/listinfo/condor-users