I GOT IT WORKING!!
Thanks to everyone for your help.
In the end, what really helped me was setting ALL_DEBUG = D_FULLDEBUG in condor_config. This showed me what the real problem was. It was a strange issue caused by condor checking if the windows firewall was enabled … and a few other minor issues. The firewall issue actually caused a 10 minute delay in starting the other condor services (condor_collector.exe, etc).
Here is what I had to do to actually get condor working:
1. Installed the windows 6.7.9 condor package (ignored errors about condor_config.local)
2. Converted condor_config.local from unix to dos format (I did this by opening it in wordpad and clicking save)
3. Changed all ‘/’ in paths to ‘\’ in condor_config and condor_config.local (not really necessary because windows is forgiving, but it IS incorrect anyway as it was)
4. Added two constants to condor_config.local to fix the firewall issue (this was crucial to get things to work)
a. ADD_WINDOWS_FIREWALL_EXCEPTION = FALSE
b. WINDOWS_FIREWALL_FAILURE_RETRY = 10
5. Restarted Condor service (It Worked!)
BTW, I also had to convert the examples from unix to dos.
Thanks again for everyone’s help.
condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of John Alberts
Has anyone had any luck using Condor on Windows 2003 Server with/without sp1 as a central manager? I tried, but it didn’t work. It was my first attempt at using condor, so maybe it was user error? J
BTW, my Win2k3 machine is also a DC.