[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] job evicted but stays idle!


I'm 99% sure that the condor_q -better-analyze did NOT give me the standard output where it would tell me which constraint might be causing the problem -- this is also what I thought was odd. However, I will attempt to reproduce the scenario this week, as I believe it reproduces faithfully every time, and I will provide verbatim screendumps....

Thanks in advance, Ian and all.


On Thu, Dec 23, 2010 at 4:31 PM, Ian Chesal <ichesal@xxxxxxxxxxxxxxxxxx> wrote:
On Thu, Dec 23, 2010 at 4:27 PM, Gautam Saxena <gsaxena888@xxxxxxxxx> wrote:

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 

condor_q -analyze


condor_q -better-analyze

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.

- Ian

Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Gautam Saxena
President & CEO
Integrated Analysis Inc.

Making Sense of Data.
Biomarker Discovery Software | Bioinformatics Services | Data Warehouse Consulting | Data Migration Consulting
(301) 760-3077 office
(301) 358-5499 direct
(301) 560-3463 fax