Managing Serviceguard Eighteenth Edition, September 2010

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