Re: [gt-user] globus-job-status: UNKNOWN JOB STATE 0

2010-01-25 Thread Joseph Bester

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


Re: [gt-user] globus-job-status: UNKNOWN JOB STATE 0

2010-01-25 Thread Joseph Bester

On Jan 23, 2010, at 4:53 PM, Stuart Martin wrote:

Joe,

Can you help debug what might be wrong when Nikolay starts the seg:


[root]$ globus-job-manager-event-generator -scheduler pbs -background
-pidfile $GLOBUS_LOCATION/var/globus-job-manager-seg-pbs.pid
Error: pbs not configured


-Stu


Run gpt-postinstall -force to get the setup package to be rerun so  
that it will know about the PBS setup. There is currently an  
unexpressed order dependency between the PBS SEG and job manager SEG  
setup packages, so depending on install order they may get run in the  
wrong order.


Joe



Re: [gt-user] globus-job-status: UNKNOWN JOB STATE 0

2010-01-25 Thread Nikolay Kutovskiy
Thanks. Joseph! That helped!

Nikolay.

Joseph Bester wrote on 25/01/10 20:54:
 On Jan 23, 2010, at 4:53 PM, Stuart Martin wrote:
 Joe,

 Can you help debug what might be wrong when Nikolay starts the seg:

 [root]$ globus-job-manager-event-generator -scheduler pbs -background
 -pidfile $GLOBUS_LOCATION/var/globus-job-manager-seg-pbs.pid
 Error: pbs not configured

 -Stu
 
 Run gpt-postinstall -force to get the setup package to be rerun so that
 it will know about the PBS setup. There is currently an unexpressed
 order dependency between the PBS SEG and job manager SEG setup packages,
 so depending on install order they may get run in the wrong order.
 
 Joe
 


Re: [gt-user] globus-job-status: UNKNOWN JOB STATE 0

2010-01-22 Thread Stuart Martin
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