On a Unix remote host, jobs may fail with error 129 when performing sudo

sudo ./AppManage -stop -app BOLService_pl -domain prod_domain -user prod -pw *****
Initializing ...
+ expr 0 + 129
+ RC=129

Legacy ID:KA389222

The exit code from a batch job is a standard UNIX termination status, which is the same sort of number you get in a shell script when checking the "$?" or "$status" variable after executing a command.

Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling exit() with a non-zero value to terminate itself and indicate an error
Exit codes in the range 129-255 represent jobs terminated by Unix "signals".
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 (such as for SEGV, see below) or when sent to the process by the Operating System.

In this scenario - the job exits with 129 - which means 128 + 1

Signal 1 means SIGHUP and we can see that it happens 5 minutes after the job started.

As a general note, whenever the Control-M/Agent communicates with a remote host it opens an SSH session to this machine, and another SFTP connection (in order to transfer the wrapper temp files and then, to clean these logs and to pull out the SYSOUT file from the remote-host back to the Agent).
After some period of time, the Control-M/Agent drops the SSH connection and only reconnects when the job ends (the SFTP session remains open).

By default the connection closes after 300 seconds / 5 minutes.

In order to prevent this error and allow you to initiate a connection to a remote host over SSH with the parameter "ssh -t" for a pseudo tty, we need to increase the timeout value.

To do this, please, open the ctm/data/OS.dat file on the Control-M/Agent that communicates with this remote host and add the following parameter: RJX_SSH_CLOSE_TOUT

Please set the value to the maximum expected time-frame that the job should execute.
If for example, the job should execute normally for 10 minutes, then please set this value to 900 seconds / 15 minutes to allow it some extra time to complete.

For example:
RJX_SSH_CLOSE_TOUT 900

Stop and restart the Control-M/Agent to make the change effective, and test the job again.

1. Control-M/Agent for UNIX and Microsoft Windows