[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Newly Added Machines to an Existing Pool Remain Idle
- Date: Sat, 24 Jun 2006 10:42:19 -0700
- From: Brian Kidd <bkidd@xxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] Newly Added Machines to an Existing Pool Remain Idle
Thank you for the suggestion. Indeed, the IA32 machines are not matched.
My next question is can I change the default requirements to not
require the same OS and Arch as the submit machine? If so, how do I do
On Jun 24, 2006, at 10:07 AM, Erik Paulson wrote:
On Sat, Jun 24, 2006 at 03:37:18AM -0700, Brian Kidd wrote:
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?
Any jobs you submit will have a default requirements expression to
say "require the same OS and Arch as the submit machine". x86_64
have a different Arch than IA32 machines.
If that's the case, jobs will never match with the IA32 machines, and
they'll always stay idle.
You can check this by:
1. condor_q -analyze will tell you what how many machines match and how
many don't match.
2. You can check the negotiator log on the central manager to see how
many machines it is considering for matchmaking.
3. You can check the schedd log on the submit machine to see if you're
running into some problem that prevents running new jobs.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
You can also unsubscribe by visiting
The archives can be found at either