Difference between revisions of "Tools/Manuals/TS71"
< Tools
Jump to navigation
Jump to search
m |
m |
||
Line 33: | Line 33: | ||
<li> or it is not defined at all, | <li> or it is not defined at all, | ||
<li> or there is a firewall blocking the specified range. | <li> or there is a firewall blocking the specified range. | ||
</ul | </ul> | ||
NOTE: a direct <font face="Courier New,Courier">globus-job-run</font> '''may''' work for the CE | NOTE: a direct <font face="Courier New,Courier">globus-job-run</font> '''may''' work for the CE | ||
because it does not use the two-phase commit feature of GRAM, | because it does not use the two-phase commit feature of GRAM, |
Revision as of 09:33, 26 May 2011
Back to Troubleshooting Guide
Globus error 79: connecting to the job manager failed.
Full message
$ glite-wms-job-logging-info -v 2 https://wms221.cern.ch:9000/cFtw9svc7vBkj3GnvCHwOE [...] Event: Done [...] - Exit code = 1 [...] - Reason = Got a job held event, reason: Globus error 79: connecting to the job manager failed. Possible reasons: job terminated, invalid job contact, network problems, ... - Source = LogMonitor [...] - Status code = FAILED [...]
Diagnosis
This problem can happen at least for these reasons:
- The CE to which the job was sent does not allow the WMS to connect to a port within the GLOBUS_TCP_PORT_RANGE defined on the CE:
- Either the GLOBUS_TCP_PORT_RANGE on the CE has an incorrect value,
- or it is not defined at all,
- or there is a firewall blocking the specified range.
NOTE: a direct globus-job-run may work for the CE because it does not use the two-phase commit feature of GRAM, while the WMS (Condor-G) depends on it.
- The job could not be submitted to the batch system. See Unspecified gridmanager error for details and suggestions.