Subject: [Condor-users] Problems with ProcD under Windows
Hi all,
We run Condor on WindowsXP-based student labs and have run into some problems on a subset of machines. The images on these machines are only slightly different from the others but the startd log is full of errors like:
2/19 09:48:42 start_procd: error received from procd: error: getProcInfo failed on own PID 2/19 09:48:42 ERROR "unable to spawn the ProcD" at line 136 in file ..\src\condor_c++_util\proc_family_proxy.C
2/19 09:48:42 startd exiting because of fatal exception.
The machine attempts to run the job, fails, the startd dies and causes a restart. This behaviour then cycles every 30 minutes. Any ideas as to what would cause this error in the procd (or more specifically how to fix it)?