Next: Job Submission Errors
Up: Job Submission
Previous: Customized Configuration Files
The user is able to recollect the output of the job only when the job status is
done. In case the job hangs in some other status, the job is lost and
the user must re-submit it. Examples are:
When problems executing a job arise because of some job error, the user must
debug the job locally before trying to run it on the grid. Examples of such
cases are segmentation faults, floating point exceptions, job hanging in
some loop or waiting for resources.
- wait, no recovery
a job may hang in waiting status when some problem arises at RB level
- cancel, stopped but output lost
the job was cancelled by the user. In this case the OutputSandbox is cleared
and the user is not able to retrieve any job information.