[torqueusers] Torque 2.3.4 - Jobs not running
Wayne Mallett
wayne.mallett at jcu.edu.au
Mon Nov 24 14:05:26 MST 2008
G'day all,
I have recently upgraded to Torque 2.3.4 and have found jobs won't run on some
servers unless I direct them to with a "qrun <jobid>". Using "tracejob
<jobid>" on a job that wasn't forced to run, I get the following output
Job: 85142.pbs.cluster
11/25/2008 06:45:00 S committing job
11/25/2008 06:45:00 S enqueuing into feeder, state 1 hop 1
11/25/2008 06:45:00 S dequeuing from feeder, state QUEUED
11/25/2008 06:45:00 S enqueuing into infinity, state 1 hop 1
11/25/2008 06:45:00 S Job Queued at request of sci-wam at login.cluster,
owner = sci-wam at login.cluster, job name =
STDIN, queue = infinity
11/25/2008 06:45:00 A queue=feeder
11/25/2008 06:45:00 A queue=infinity
11/25/2008 06:45:00 S ready to commit job
11/25/2008 06:45:00 S ready to commit job completed
In the server_logs directory I find the following information:
11/25/2008 06:45:00;0008;PBS_Server;Job;85142.pbs.cluster;ready to commit job
11/25/2008 06:45:00;0008;PBS_Server;Job;85142.pbs.cluster;ready to commit job
completed
11/25/2008 06:45:00;0008;PBS_Server;Job;85142.pbs.cluster;committing job
11/25/2008 06:45:00;0001;PBS_Server;Svr;PBS_Server;svr_setjobstate: setting
job 85142.pbs.cluster state from TRANSIT-TRANSICM to QUEUED-QUEUED (1-10)
11/25/2008 06:45:00;0100;PBS_Server;Job;85142.pbs.cluster;enqueuing into
feeder, state 1 hop 1
11/25/2008 06:45:00;0100;PBS_Server;Job;85142.pbs.cluster;dequeuing from
feeder, state QUEUED
11/25/2008 06:45:00;0100;PBS_Server;Job;85142.pbs.cluster;enqueuing into
infinity, state 1 hop 1
11/25/2008 06:45:00;0008;PBS_Server;Job;85142.pbs.cluster;Job Queued at
request of sci-wam at login.cluster, owner = sci-wam at login.cluster, job name =
STDIN, queue = infinity
Regards,
Wayne
--
Dr. Wayne Mallett
Email: Wayne.Mallet at jcu.edu.au
Smail: High Performance & Research Computing
James Cook University
Townsville Qld 4811
Phone: 0747815084
More information about the torqueusers
mailing list