On Jan 22, 2010, at 8:43 AM, Nikolay Kutovskiy wrote:
Hello list,
I have installed GRAM5 to use PBS and get the following output of
globus-job-status command:
$ globus-job-submit <gram_hostname>:2119/jobmanager-pbs /bin/hostname
https://<gram_hostname>:
51499/16073727533535086921/7782764993921513916/
[user]$ globus-job-status
https://<gram_hostname>:
51499/16073727533535086921/7782764993921513916/
UNKNOWN JOB STATE 0
[user]$ globus-job-status
https://<gram_hostname>:
51499/16073727533535086921/7782764993921513916/
UNKNOWN JOB STATE 0
[user]$ globus-job-status
https://<gram_hostname>:
51499/16073727533535086921/7782764993921513916/
UNKNOWN JOB STATE 0
[user]$ globus-job-status
https://<gram_hostname>:
51499/16073727533535086921/7782764993921513916/
DONE
Is that a bug? some GRAM5|PBS misconfiguration?
Commands like globus-job-run work fine.
Environment:
gt5.0.0-all-source-installer.tar.bz2
torque-2.3.7-1cri
torque-docs-2.3.7-1cri
torque-server-2.3.7-1cri
torque-client-2.3.7-1cri
torque-scheduler-2.3.7-1cri
Thanks in advance,
Nikolay
That's a bug. In GRAM2, the job manager exited after the job
terminated, so globus-job-status would interpret a connection-refused
response as DONE. In GRAM5, the job manager may still be running but
no longer know about a particular job. You can probably treat this as
"job is done" until this issue is resolved in the job manager.
Joe
