[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] I have 4 jobs being held in the queue andnothing is running because of that
- Date: Thu, 26 Feb 2009 17:51:48 -0500
- From: Ian Chesal <ICHESAL@xxxxxxxxxx>
- Subject: Re: [Condor-users] I have 4 jobs being held in the queue andnothing is running because of that
> WARNING: Be advised:
> No resources matched request's constraints
> Check the Requirements expression below:
> Requirements = (OpSys == "WINNT52" || OpSys == "WINNT51") && (Arch ==
> "INTEL") &
> & (Disk >= DiskUsage) && ((Memory * 1024) >= ImageSize) &&
> (HasFileTransfer) &&
> (HasWindowsRunAsOwner && (LocalCredd =?= "Mann.earthdata.com"))
> Is there another way to resubmit that job. I really don't get why is
> rejecting the job due to the requirements if the other jobs previous
> this one were able to run just fine?
There are no machines in your pool that match that job's requirements.
Maybe after the power outage the machine(s) that were previously
matching this requirement didn't come back up? You can search for
machines that match thing requirement by doing:
condor_status -const '(OpSys == "WINNT52" || OpSys == "WINNT51") &&
(Arch == "INTEL") && (Disk >= DiskUsage) && ((Memory * 1024) >=
ImageSize) && (HasFileTransfer) && (HasWindowsRunAsOwner && (LocalCredd
You need to look up what DiskUsage and what ImageSize are for your job
and substitute the actual value into that constraint string before you
do the call though.
If that call returns nothing you've got no matching machines.
You can also try the -better-analyze option -- it'll break down the
requirements string and show you precisely which component is keeping
you from matching any machines with your jobs. Only works on Linux
Hope that helps!
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.