On Thu, Dec 23, 2010 at 4:27 PM, Gautam Saxena <gsaxena888@xxxxxxxxx>
I've been using condor (v7.4, all windows machines running either WinServer2003 or WinXP) for a few months now, but am confused about one thing:
when a job gets evicted because of a user interacting with his machine, the job seems to permanently remain in an "idle" state, at least according to condor_q command. I waited about 30 minutes. I ran
but it didn't tell me anything useful. It just said that
<all machines> are rejected by your job's requirements
As jobs run some of their attributes change. Namely ImageSize and Disk -- they get adjusted to match what the job actually uses. Are you sure one of these didn't inflate high enough to constrain you out of all your machines?
Can you paste the output from -better-analyze? That'd be useful for giving you an analysis of your problem.