How to tell if a Shareplex process exited normally or abnormally? (4301103)

This document provides examples of normal and abnormal termination of shareplex processes to aid the user in monitoring Shareplex. 

n/a

A Shareplex program module can end in a normal manner or can terminate abnormally. The Shareplex event_log located in $SP_SYS_VARDIR/log directory contains the log of various Shareplex processes. The log has an exit code 0 or 1 associated with a process that ends gracefully or abnormally respectively. Thus the user (or monitoring script) can search for the string exit(0) for normal termination and exit(1) for abnormal termination as the following entries show:

a. Normal termination:

In the following event log entries the Capture process exits normally which indicates that there is no error condition:

10/30/08 07:18 Notice: shutting down by request [sp_ocap/7540812]
10/30/08 07:18 Process exited sp_ocap  (for o.SID) [pid = 7540812] - exit(0)

b. Abnormal termination:

In programming jargon, an exception is raised or to put it another way an error condition has occurred:

10/23/08 19:45 Process launched: sp_xport (to <IP address> queue queuename) [pid = 26221]
10/23/08 19:45 Connected to host <IP address>
10/23/08 19:46 Cannot connect to import on <IP address>  - timeout waiting for ack
10/23/08 19:46 Process exited sp_xport  (to <IP address> queue queuename) [pid = 26221] - exit(1)

The exit codes can be used within a program or a shell script to change the flow of execution depending on the success or failure of commands executed. In general, Success is represented with exit 0 and failure is indicated with a non-zero exit-code.