Hi Nikolay,
Strange. Yea - looks like a bug. Is that repeatable / happens for every PBS
job?
Are you using the SEG for PBS job monitoring? If not, try using the SEG and
see what happens.
http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/admin/#gram5-Interface_Config_Frag-seg_module
http://www.globus.org/toolkit/docs/5.0/5.0.0/execution/gram5/admin/#id2545819
-Stu
On Jan 22, 2010, at Jan 22, 7: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
