System is Terminating Due to Hang Up Signal (SIGHUP)

[ravicapg]

One of the batch Job failed and restarted again and got error like ERROR: System is Terminating Due to Hang Up Signal (SIGHUP)).

Can any one please help.

Thanks

[nhvdwalt]

Someone / something probably issued a kill -15 (or 9) against the UNIX
process that ran your batch job. Does your UNIX environment have any usage
limitations that could maybe trigger the OS to kill your job ?

[ravicapg]

Thanks for quick reply. No one killed job. Could you please explain below variable values and uses. 

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 1032768
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 350000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 100000
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

[Kurt_Bremser]

Actually, SIGHUP is signal 1. It is usually issued when a terminal connection breaks.

If your scheduler runs from a remote server, it connects to the SAS server via ssh and then issues commands. If the ssh connection drops, the SAS job will receive a SIGHUP (because the connection was "hung up" like a telephone) and terminate gracefully (writing the reason to the log). The scheduler will probably handle this as an internal error and restart the batch job.

If you started the batch job via console login, and either killed the telnet/PuTTY client while the job was running, or had a network outage, or ran into some timeout (eg your PC went into standby), then the result is more or less the same.

To prevent such termination, use the nohup wrapper and put the process into the background:

nohup sasbatch program.sas&

Mind that a broken connection will still be registered as an error condition by a scheduler, so don't use nohup there.

[ravicapg]

Thanks for reply Kurt,

How to know if the specific job hangs up from long time? the job not restarted after receive a SIGHUP message. do we want to restart the job again when see like  SIGHUP  ERROR.

Thanks

Ravi Inturi

[Kurt_Bremser]

In your first post you said "and restarted again". How was the job restarted?

---

@ravicapg wrote:

Thanks for reply Kurt,

How to know if the specific job hangs up from long time? the job not restarted after receive a SIGHUP message. do we want to restart the job again when see like  SIGHUP  ERROR.

Thanks

Ravi Inturi

---

[nhvdwalt]

Thanks @Kurt_Bremser, this is a good explanation.