|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|Documentation menu:||Home •||Manuals •||Procedures •||Training •||Other •||Contact ►||For:||VO managers •||Administrators|
Back to Troubleshooting Guide
Globus error 155: the job manager could not stage out a file
$ glite-wms-job-logging-info -v 2 https://wms221.cern.ch:9000/aFtw9svc7vBkj3GnvCHwOC [...] Event: Done [...] - Exit code = 1 [...] - Reason = Got a job held event, reason: Globus error 155: the job manager could not stage out a file - Source = LogMonitor [...] - Status code = FAILED [...]
This problem typically occurs if the submitting WMS cannot be called back by the CE. This either means that the WMS has its GLOBUS_TCP_PORT_RANGE ill- or undefined (at least for the Condor processes), or that some (campus/department/node) firewall is blocking outside access to the port range. (Or the CE might mistakenly restrict outgoing connections.)
Note: if the problem is intermittent between the same endpoints, refer to gridftp works only once within a minute or so.