program terminated with signal sigalrm alarm clock

I am surprised by this, as I am pretty sure that there was plenty of memory for it.

Under what conditions does linux (busybox) send a SIGTERM to a process.

What can you tell us about what the program is doing and how its started How did you find out about the programs exit status Can you reproduce the problem Do you have logs you can check.

I have wrapped the execution on a bash script and therefore I know the exit code.

Is it possible someone else was able to kill your server program.

An exiting program can choose any integer between 0 and 255 as its exit status.

Values 126 and above are used by the shell to report special conditions, so its best to avoid them.

There are a few signals that are sent automatically like SIGHUP when a terminal goes away, SIGSEGVSIGBUSSIGILL when a process does things it shouldnt be doing, SIGPIPE when it writes to a broken pipesocket, etc.

And there are a few signals that are sent due to a key press in a terminal, mainly SIGINT for Ctrl C, SIGQUIT for Ctrl and SIGTSTP for Ctrl Z, but SIGTERM is not one of those.

If a process receives SIGTERM, some other process sent that signal.

Well, one of the questions in the body given that it was based on a misunderstanding, it is a bit messy.

Something on your system is explicitly calling kill(, SIGTERM).

Youd have to look at the clusters documentation or ask the administrators.

If on Linux, you could use auditd auditctl to log invocations of kill tkill tgkill system calls.

I am for sure (me) not doing any killing, it must be something either in python or the cluster would be my guess.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged linux process busybox signals or ask your own question.

Program Terminated With Signal Sigalrm Alarm Clock