|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
8 the user cancelled the job
$ glite-wms-job-logging-info -v 2 https://lb009.cnaf.infn.it:9000/hWcl6dGVN7Z3JgXHbUKTkg [...] --- Event: Transfer - Arrived = Wed Sep 16 10:47:08 2009 CEST - Dest host = unavailable - Dest instance = /var/glite/logmonitor/CondorG.log/CondorG.1229530674.log - Dest jobid = unavailable - Destination = LRMS - Host = gridit-cert-rb.cnaf.infn.it - Reason = 8 the user cancelled the job - Result = FAIL - Source = LogMonitor - Src instance = unique - Timestamp = Wed Sep 16 10:47:08 2009 CEST - User = /...../CN=proxy/CN=proxy --- Event: Done - Arrived = Wed Sep 16 10:47:21 2009 CEST - Exit code = 1 - Host = gridit-cert-rb.cnaf.infn.it - Reason = Job got an error while in the CondorG queue. - Source = LogMonitor - Src instance = unique - Status code = FAILED - Timestamp = Wed Sep 16 10:47:21 2009 CEST - User = /...../CN=proxy/CN=proxy --- [...]
In this case the "user" denotes the local account that submitted the job to Condor-G on the gLite WMS, i.e. "glite". A Condor-G job should only be canceled by the WMS itself when the job proxy is about to expire and could not be renewed or, in this case, when the submission to the CE has suffered persistent problems, usually network timeouts, that may be due to configuration errors on the CE or the WMS itself. See data transfer to the server failed and various other Globus errors explained in the Troubleshooting Guide.