Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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.
Package Control Script Error and Exit Conditions
Table 4 shows the possible combinations of error condition, failfast setting and package
movement for failover packages.
Table 4 Error Conditions and Package Movement for Failover Packages
ResultsPackage Error Condition
Package
Allowed to
Package Allowed
to Run on Primary
Node after Error
Halt script
runs after
Error or
Exit
Linux Status
on Primary
after Error
Service
Failfast
Enabled
Node
Failfast
Enabled
Error or Exit
Code
Run on
Alternate
Node
YesN/A (system
reset)
Nosystem resetYESEither
Setting
Service Failure
YesNoYesRunningNOEither
Setting
Service Failure
NoNot changedNoRunningEither
Setting
Either
Setting
Run Script Exit
1
YesN/A (system
reset)
Nosystem resetEither
Setting
YESRun Script Exit
2
YesNoNoRunningEither
Setting
NORun Script Exit
2
YesN/A (system
reset)
Nosystem resetEither
Setting
YESRun Script
Timeout
NoNot changedNoRunningEither
Setting
NORun Script
Timeout
NoYesN/ARunningEither
Setting
YESHalt Script Exit
1
NoYesN/ARunningEither
Setting
NOHalt Script Exit
1
How Packages Run 67