Managing HP Serviceguard A.12.00.00 for Linux, June 2014

7. Exits with an exit code of zero (0).
8. Executes any external_pre_script. For more information, see “external_pre_script”
(page 200).
Figure 21 Modular Package Time Line for Halt Script Execution
At any step along the way, an error will result in the script exiting abnormally (with an exit code
of 1). If the halt script execution is not complete before the time specified in the
halt_script_timeout (page 187) , the package manager will kill the script. During halt script
execution, messages are written to a log file. For modular packages, the pathname is determined
by the script_log_file parameter in the package configuration file (page 188). Normal starts
are recorded in the log, together with error messages or warnings related to halting the package.
3.4.10 Normal and Abnormal Exits from the Halt Script
The package’s ability to move to other nodes is affected by the exit conditions on leaving the halt
script. The following are the possible exit codes:
• 0—normal exit. The package halted normally, so all services are down on this node.
• 1—abnormal exit, also known as no_restart exit. The package did not halt normally.
Services are killed, and the package is disabled globally. It is not disabled on the current
node, however.
• 2 — abnormal exit, also known as restart exit. The package did not halt normally. Services
are killed, and the package is disabled globally. It is not disabled on the current node, however.
The package is allowed to run on an alternate node.
• 3—abnormal exit. The package did not halt normally and will be placed in the halt_aborted
state (page 212). The package switching is disabled and it will not failover to other nodes.
• Timeout—Another type of exit occurs when the halt_script_timeout is exceeded. In this
scenario, the package is killed and disabled globally. It is not disabled on the current node,
however.
58 Understanding Serviceguard Software Components