Created by Thomas Hartmann on Jan 16, 2018 12:26
Summary of Condor status codes taken from here
Job Status Codes
| 0 | Unexpanded | U |
| 1 | Idle | I |
| 2 | Running | R |
| 3 | Removed | X |
| 4 | Completed | C |
| 5 | Held | H |
| 6 | Submission_err | E |
Shadow exit status
| Value | Name | Description |
|---|
| 4 | JOB_EXCEPTION | The job exited with an exception |
| 44 | DPRINTF_ERROR | There is a fatal error with dprintf() |
| 100 | JOB_EXITED | The job exited (not killed) |
| 101 | JOB_CKPTED | The job was checkpointed |
| 102 | JOB_KILLED | The job was killed |
| 103 | JOB_COREDUMPED | The job was killed and a core file produced |
| 105 | JOB_NO_MEM | Not enough memory to start the shadow |
| 106 | JOB_SHADOW_USAGE | incorrect arguments to condor_shadow |
| 107 | JOB_NOT_CKPTED | The job was kicked off without a checkpoint |
| 107 | JOB_SHOULD_REQUEUE | (!) We define this to the same number, since we want the same behavior. However, "JOB_NOT_CKPTED" doesn't mean much if we're not a standard universe job. The effect of this exit code is that we want the job to be put back in the job queue and run again. |
| 108 | JOB_NOT_STARTED | Can't connect to startd or request refused |
| 109 | JOB_BAD_STATUS | Job status != RUNNING on startup |
| 110 | JOB_EXEC_FAILED | Exec failed for some reason other than ENOMEM |
| 111 | JOB_NO_CKPT_FILE | There is no checkpoint file (lost) |
| 112 | JOB_SHOULD_HOLD | The job should be put on hold |
| 113 | JOB_SHOULD_REMOVE | The job should be removed |
Log event codes
| Submit | 0 |
| Execute | 1 |
| Executable error | 2 |
| Checkpointed | 3 |
| Job evicted | 4 |
| Job terminated | 5 |
| Image size | 6 |
| Shadow exception | 7 |
| Generic | 8 |
| Job aborted | 9 |
| Job suspended | 10 |
| Job unsuspended | 11 |
| Job held | 12 |
| Job released | 13 |
| Node execute | 14 |
| Node terminated | 15 |
| Post script terminated | 16 |
| Globus submit | 17 |
| Globus submit failed | 18 |
| Globus resource up | 19 |
| Globus resource down | 20 |
| Remote error | 21 |