Managing HP Serviceguard A.11.20.20 for Linux, March 2014

1. Halts all package services.
2. Executes any customer-defined halt commands (legacy packages only) or external_scripts
(modular packages only; see “external_script” (page 190)).
3. Removes package IP addresses from the LAN card on the node.
4. Unmounts file systems.
5. Deactivates volume groups.
6. Revokes Persistent registrations and reservations, if any
7. Exits with an exit code of zero (0).
8. Executes any external_pre_scripts (modular packages only; see
“external_pre_script” (page 190)).
Figure 21 Legacy 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 177) , the package manager will kill the script. During halt script
execution, messages are written to a log file. For legacy packages, this is in the same directory
as the run script and has the same name as the run script and the extension.log. For modular
packages, the pathname is determined by the script_log_file parameter in the package
configuration file (page 178). Normal starts are recorded in the log, together with error messages
or warnings related to halting the package.
NOTE: This diagram applies specifically to legacy packages. Differences for modular scripts are
called out above.
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:
60 Understanding Serviceguard Software Components