Managing Serviceguard 13th Edition, February 2007

Understanding Serviceguard Software Components
How Package Control Scripts Work
Chapter 398
This log has the same name as the halt script and the extension.log.
Normal starts are recorded in the log, together with error messages or
warnings related to halting the package.
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.
• 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. The package script may not have been able to clean up some
of its resources such as LVM volume groups, VxVM disk groups or
package mount points, so before attempting to start up the package
on any node, be sure to check whether any resources for the package
need to be cleaned up
Package Control Script Error and Exit Conditions
Table 3-4 shows the possible combinations of error condition, failfast
setting and package movement for failover packages.
Table 3-4 Error Conditions and Package Movement for Failover Packages
Package Error Condition Results
Error or
Exit Code
Node
Failfast
Enabled
Service
Failfast
Enabled
HP-UX
Status
on
Primary
after
Error
Halt
script
runs
after
Error
or Exit
Package
Allowed to
Run on
Primary
Node after
Error
Package
Allowed
to Run on
Alternate
Node
Service
Failure
YES YES TOC No N/A (TOC) Yes