Difference between revisions of "Tools/Manuals/TS56"
(Created page with '{{TOC_right}} Category:FAQ ------ Back to Troubleshooting Guide ------ = Jobs sent to some CE stay in Ready state forever = == Full m…') |
m |
||
Line 9: | Line 9: | ||
== Full message == | == Full message == | ||
$ glite-wms-job-status https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A | $ glite-wms-job-status <nowiki>https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A</nowiki> | ||
************************************************************* | ************************************************************* | ||
BOOKKEEPING INFORMATION: | BOOKKEEPING INFORMATION: | ||
Status info for the Job : https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A | Status info for the Job : <nowiki>https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A</nowiki> | ||
Current Status: Ready | Current Status: Ready | ||
Status Reason: unavailable | Status Reason: unavailable |
Revision as of 14:08, 25 May 2011
Back to Troubleshooting Guide
Jobs sent to some CE stay in Ready state forever
Full message
$ glite-wms-job-status https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A ************************************************************* BOOKKEEPING INFORMATION: Status info for the Job : https://lxbra2303.cern.ch:9000/nZWbflGp1gJVwC-pXN_d8A Current Status: Ready Status Reason: unavailable Destination: some-CE.some-domain:2119/jobmanager-pbs-ops Submitted: Fri Mar 27 20:29:24 2009 CET *************************************************************
Diagnosis
A gLite WMS job enters the Ready state when the Workload Manager (WM) daemon has matched it to a particular CE. For an LCG-CE or an ARC-CE (NorduGrid) the job is handed to Condor-G, for a CREAM-CE the job is handed to ICE. In either case the job should quickly reach the Scheduled state indicating that the job has actually been submitted to the CE. The Ready state will persist when there are network or configuration problems affecting the CE or possibly the WMS itself. For example, an LCG-CE and the WMS each need the GLOBUS_TCP_PORT_RANGE environment variable correctly defined and firewalls need to allow each service to receive incoming connections in its port range. Otherwise the job may eventually fail with an error that may be explained in the Troubleshooting Guide.