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

Re: [Condor-users] Newly Added Machines to an Existing Pool Remain Idle



Do condor_q -l on your jobs and check your "requirements" field. Likely
you are submitting from an x86_64 machine and that is getting
entered into the requirements of your job by default. There are
ways to defeat this in the condor manual.

Steve


------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team

On Sat, 24 Jun 2006, Brian Kidd wrote:

hello

i have set up a condor pool with 10 machines that are all x86_64 arch
and this pool runs just fine. i recently added some intel arch to this
pool and they simply sit idle. condor_status shows that they are part
of the pool, however they remain idle. all the log files seem normal,
except no negotiation takes place and jobs are never claimed by any of
the recently added machines. thus, i was wondering if i need to change
a setting so these other machines will work with the cluster? also,
what particular files should i be looking at to debug this situation?

thanks,
-brian

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR