Am 05.12.2012 16:21, schrieb Morten Wang:
Is there a way for me to find that out myself, e.g.
using qstat? I had a
look at the qstat man-page, but judging by the descriptions it looks like
something I'd have to fiddle around with if/when a job gets queued for a
long time at some point in the future to figure out how to do.
qstat -j <jobnumber>
lists a scheduling info section.
qstat -j 799111
queue instance "short-sol(a)ortelius.toolserver.org" dropped because it is
overloaded: np_load_short=1.252930 (= 1.252930 + 0.8 * 0.000000 with
nproc=4) >= 1.1
queue instance "longrun-sol(a)willow.toolserver.org" dropped because it is
overloaded: np_load_short=2.528320 (= 2.528320 + 0.8 * 0.000000 with
nproc=8) >= 2.0
queue instance "medium-sol(a)ortelius.toolserver.org" dropped because it
is overloaded: np_load_short=1.252930 (= 1.252930 + 0.8 * 0.000000 with
nproc=4) >= 0.8
queue instance "longrun2-sol(a)clematis.toolserver.org" dropped because it
queue instance "longrun2-sol(a)hawthorn.toolserver.org" dropped because it
cannot run globally because it offers only gc:sql-s7-rr=0.000000
As you can see the job cannot run on clematis and hawthorn, because
these queues are disabled. queues on willow and ortelius have temporary
high load. wolfsbane, nightshade and yarrow are missing in this list so
the bot could start on these servers. But the last line "cannot run
globally because it offers only gc:sql-s7-rr=0.000000" shows that
resource sql-s7-rr is not available on any server at the moment. That's
why the job is queued until s7 database is usable again.