abstract:darwin:runjobs:job_status

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
abstract:darwin:runjobs:job_status [2024-05-23 12:15] – [sacct or ssacct] anitaabstract:darwin:runjobs:job_status [2024-07-17 15:42] (current) – [sacct or ssacct] anita
Line 208: Line 208:
 Here is another example showing a job exited because enough memory was not specified for the job (may be indicated in Slurm output as ''oom-kill event(s)'' which means __o__ut __o__f __m__emory), and in ''sacct'' shows ''OUT_OF_ME+'' which also means OUT OF MEMORY. Here is another example showing a job exited because enough memory was not specified for the job (may be indicated in Slurm output as ''oom-kill event(s)'' which means __o__ut __o__f __m__emory), and in ''sacct'' shows ''OUT_OF_ME+'' which also means OUT OF MEMORY.
  
 +<code>
 [traine@login00 ~]$ sacct -j 9176640 [traine@login00 ~]$ sacct -j 9176640
        JobID    JobName  Partition    Account  AllocCPUS      State ExitCode        JobID    JobName  Partition    Account  AllocCPUS      State ExitCode
  • abstract/darwin/runjobs/job_status.1716480933.txt.gz
  • Last modified: 2024-05-23 12:15
  • by anita