[torqueusers] Interpreting Exit_status in server accounting files
garrick at usc.edu
Tue Jan 10 16:41:06 MST 2006
On Wed, Jan 11, 2006 at 10:06:32AM +1100, Jeroen van den Muyzenberg alleged:
> Erm... I'll take that back. Have had a brief look and it seems that
> exit_status could be assigned to one of the JOB_EXIT_* definitions in
> However I can't see the correlation with those definitions and the final
> reported value.
Negative exit values are "special." They are generated by MOM to
indicate an error outside of the job. The specific meaning of each is
the JOB_EXEC_* defines in job.h.
Positive exit values are from the user's job. It is just whatever the
job returned and can't be reliably interpreted without looking at the
> On Tue, 10 Jan 2006, Jeroen van den Muyzenberg wrote:
> >The exit status should be (haven't checked) the return from the exec'd
> >job. We've had a look at them recently and they do seem to conform to;
> > Exit_status >> 8 # Actual exit value
> > Exit_status & 127 # Signal number if thus killed
> > Exit_status & 128 # True if a core dump happened
> >On Tue, 10 Jan 2006, Ole Holm Nielsen wrote:
> >> I'm working on the "pbsacct" accounting package for Torque/PBS
> >> and would like to understand the meaning of the "Exit_status"
> >> numbers in the server accounting files. Unfortunately, I
> >> haven't been able to find a list of exit status values in the
> >> Torque source tree. Going through some of our accounting files,
> >> I find a number of jobs with non-zero "Exit_status" values
> >> such as: 1, 126, 127, 139, 143, 265, 271.
> >> Question: How do I assign a meaning to these "Exit_status" values
> >> so that I can decide whether or not to flag a job termination as OK
> >> (or just sort of OK) or as "failed" in the accounting output ?
> >> It would also be nice to know if a job exited because of wall or
> >> cpu time exceeded.
> >> Thanks,
> >> Ole
> >> --
> >> Ole Holm Nielsen
> >> Department of Physics, Technical University of Denmark
> >> _______________________________________________
> >> torqueusers mailing list
> >> torqueusers at supercluster.org
> >> http://www.supercluster.org/mailman/listinfo/torqueusers
> torqueusers mailing list
> torqueusers at supercluster.org
Garrick Staples, Linux/HPCC Administrator
University of Southern California
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20060110/776c3893/attachment.bin
More information about the torqueusers