Post a reply
Note:If not registered, provide any username. For more comfort, register here.
Message body:
Enter your message here, it may contain no more than 60000 characters. 

:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:
Font size:
Font colour
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Disable BBCode
Disable smilies
Do not automatically parse URLs
Confirmation of post
To prevent automated posts the board requires you to enter a confirmation code. The code is displayed in the image you should see below. If you are visually impaired or cannot otherwise read this code please contact the %sBoard Administrator%s.
Confirmation code:
Enter the code exactly as it appears. All letters are case insensitive, there is no zero.

Topic review - Exit codes
Author Message
  Post subject:  Re: Exit codes  Reply with quote
Why successfully completed ??

or see for C Exit Codes e.g.
Typically, exit code 0 (zero) means successful completion. Codes 1-127
are typically generated by your job itself calling
with a non-zero value to terminate itself and indicate an error.
In BaBar we don't make very much use of this. The most common such value you might
see is 64, which is the value used by Framework to say that its event loop is
being stopped before all the requested data have been read, typically because time
ran out.
In recent BaBar releases you might also see 125, which we use as a code for a generic
"severe error"; the job log should contain a message stating what the error was.

Exit codes in the range 129-255 represent jobs terminated by Unix
Each type of signal has a number, and what's reported as the job exit code is the
signal number plus 128.
Signals can arise from within the process itself (as for SEGV, see below)
or be sent to the process by some external agent (such as the batch control system,
or your using the "bkill" command).

By way of example, then, exit code 64 means that the job deliberately terminated its
execution by calling "exit(64)",
exit code 137 means that the job received a signal 9,
and exit code 140 represents signal 12.

SIGHUP 1 Term Hangup detected on controlling terminal
or death of controlling process
SIGINT 2 Term Interrupt from keyboard
SIGQUIT 3 Core Quit from keyboard
SIGILL 4 Core Illegal Instruction
SIGABRT 6 Core Abort signal from abort(3)
SIGFPE 8 Core Floating point exception
SIGKILL 9 Term Kill signal
SIGSEGV 11 Core Invalid memory reference
SIGPIPE 13 Term Broken pipe: write to pipe with no readers
SIGALRM 14 Term Timer signal from alarm(2)
SIGTERM 15 Term Termination signal
Post Posted: Wed Dec 27, 2017 4:04 pm
  Post subject:  Exit codes  Reply with quote
I have had a variety of exit codes that on slurm say that the job has been successfully completed, but the output file that ought to have been there, isn't. Here are some exit codes.

Program is finished with exit code 137 at: Tue Dec 26 18:13:52 EST 2017
Post Posted: Wed Dec 27, 2017 2:15 am

It is currently Fri Jan 19, 2018 3:51 pm
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group