[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Problem with multiple machines in a Windows pool
- Date: Mon, 22 Aug 2011 13:16:58 -0700
- From: Andrew Cunningham <condor@xxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Problem with multiple machines in a Windows pool
We have a mixed pool of WinXP and Win7 machines running now without any problems - the Win7 machines were initially a bit problematical but the following seemed to smooth over any problems. I suspect you may have done all this, but for what it is worth....
- Uninstalling Condor , deleting C:\condor and re-installing
- Windows Defender or equivalent needing to have the C:\condor directories excluded from scanning. Any real-time virus protection may need to be turned off. Symantec AV was a cause of many problems on one system.
- Making sure "Automatic Windows update" was off on the system
- Making sure the condor service is set to "delayed start" ( I am running <7.6.x)
On Mon, Aug 22, 2011 at 12:34 PM, Ralph Finch <ralphmariafinch@xxxxxxxxx>
The offending machine below still has the same problems even after getting the CREDD stuff to work in the pool (on the master and all machines). But now other machines share one problem: they will not delete the running directory. They do run the model, unlike the machine below, but won't delete the execute directory. Thus the c:\ drive gradually gets full and at some point will quit accepting jobs.
These problem machines are all Win7x64. Our other Windows computers are XPx86 and don't have the no-delete-directory problem. We have no Linux computers in the pool.
It must be some kind of privilege problem but at this point I don't know where to look further. Even my machine which I submit from has the problem. From Windows Explorer I've made sure that users within our Group (DELTA) have full control of the c:\condor directory, and it is shared fully to that Group.
Calif. Dept. of Water Resources