Hold Reason Codes
The user put the job on hold with condor_hold.
The
PERIODIC_HOLDexpression evaluated toTrue. Or,ON_EXIT_HOLDwas trueUser Provided
The credentials for the job are invalid.
A job policy expression evaluated to
Undefined.The condor_starter failed to start the executable.
Unix errno
The standard output file for the job could not be opened.
Unix errno
The standard input file for the job could not be opened.
Unix errno
The standard output stream for the job could not be opened.
Unix errno
The standard input stream for the job could not be opened.
Unix errno
An internal HTCondor protocol error was encountered when transferring files.
An error occurred while transferring job output files or self-checkpoint files.
See note
An error occurred while transferring job input files.
See note
The initial working directory of the job cannot be accessed.
Unix errno
Verify initialdir exists and is writeable
The user requested the job be submitted on hold.
Input files are being spooled.
Wait for spooling to complete
A standard universe job is not compatible with the condor_shadow version available on the submitting machine.
An internal HTCondor protocol error was encountered when transferring files.
<Keyword>_HOOK_PREPARE_JOB was defined but could not be executed or returned failure.
The job missed its deferred execution time and therefore failed to run.
The job was put on hold because WANT_HOLD in the machine policy was true.
Unable to initialize job event log.
Verify file in log lives in a writeable directory.
Failed to access user account.
No compatible shadow.
Invalid cron settings.
SYSTEM_PERIODIC_HOLD evaluated to true.
The system periodic job policy evaluated to undefined.
The maximum total input file transfer size was exceeded. (See MAX_TRANSFER_INPUT_MB
The maximum total output file transfer size was exceeded. (See MAX_TRANSFER_OUTPUT_MB
Job resource usage exceeded the provisioned limit.
- Exceeded Resource
Memory: 102 Disk: 104
Resubmit with larger resource request i.e. request_memory or request_disk
Specified Docker image was invalid.
Verify docker_image is correct in submit file
Job failed when sent the checkpoint signal it requested.
User error in the EC2 universe:
Public key file not defined.
1
Private key file not defined.
2
Grid resource string missing EC2 service URL.
4
Failed to authenticate.
9
Can’t use existing SSH keypair with the given server’s type.
10
You, or somebody like you, cancelled this request.
20
Internal error in the EC2 universe:
Grid resource type not EC2.
3
Grid resource type not set.
5
Grid job ID is not for EC2.
7
Unexpected remote job status.
21
Administrator error in the EC2 universe:
EC2_GAHP not defined.
6
Connection problem in the EC2 universe
…while creating an SSH keypair.
11
…while starting an on-demand instance.
12
…while requesting a spot instance.
17
Server error in the EC2 universe:
Abnormal instance termination reason.
13
Unrecognized instance termination reason.
14
Resource was down for too long.
22
Instance potentially lost due to an error in the EC2 universe:
Connection error while terminating an instance.
15
Failed to terminate instance too many times.
16
Connection error while terminating a spot request.
17
Failed to terminated a spot request too many times.
18
Spot instance request purged before instance ID acquired.
19
Pre script failed.
Post script failed.
Test of singularity runtime failed before launching a job
The job’s allowed duration was exceeded.
The job’s allowed execution time was exceeded.
Prepare job shadow hook failed when it was executed; status code indicated job should be held.
Note
For hold codes 12 [TransferOutputError] and 13 [TransferInputError]: file transfer may invoke file-transfer plug-ins. If it does, the hold subcodes may additionally be 62 (ETIME), if the file-transfer plug-in timed out; or the exit code of the plug-in shifted left by eight bits, otherwise.