Managing HP Serviceguard A.11.20.10 for Linux, December 2012

6.1.4.8 node_fail_fast_enabled
Can be set to yes or no. The default is no.
yes means the node on which the package is running will be halted (reboot) if the package fails;
no means Serviceguard will not halt the system.
If this parameter is set to yes and one of the following events occurs, Serviceguard will halt the
system (reboot) on the node where the control script fails:
• A package subnet fails and no backup network is available
• A generic resource fails
• Serviceguard is unable to execute the halt function
• The start or halt function times out
NOTE: If the package halt function fails with “exit 1”, Serviceguard does not halt the node,
but sets no_restart for the package, which disables package switching, setting auto_run
(page 170) to no and thereby preventing the package from starting on any adoptive node.
Setting node_fail_fast_enabled to yes prevents Serviceguard from repeatedly trying (and
failing) to start the package on the same node.
Setting node_fail_fast_enabled to yes ensures that the package can fail over to another
node even if the package cannot halt successfully. Be careful when using
node_fail_fast_enabled, as it will cause all packages on the node to halt abruptly. For more
information, see “Responses to Failures ” (page 72) and “Responses to Package and Service
Failures ” (page 73).
For system multi-node packages, node_fail_fast_enabled must be set to yes.
6.1.4.9 run_script_timeout
The amount of time, in seconds, allowed for the package to start; or no_timeout. The default is
no_timeout. The maximum is 4294.
If the package does not complete its startup in the time specified by run_script_timeout,
Serviceguard will terminate it and prevent it from switching to another node. In this case, if
node_fail_fast_enabled is set to yes, the node will be halted (rebooted).
If no timeout is specified (no_timeout), Serviceguard will wait indefinitely for the package to
start.
If a timeout occurs:
• Switching will be disabled.
• The current node will be disabled from running the package.
NOTE: If no_timeout is specified, and the script hangs, or takes a very long time to complete,
during the validation step (cmcheckconf (1m)), cmcheckconf will wait 20 minutes to allow
the validation to complete before giving up.
6.1.4.10 halt_script_timeout
The amount of time, in seconds, allowed for the package to halt; or no_timeout. The default is
no_timeout. The maximum is 4294.
If the package’s halt process does not complete in the time specified by halt_script_timeout,
Serviceguard will terminate the package and prevent it from switching to another node. In this
case, if node_fail_fast_enabled (page 171) is set to yes, the node will be halted (reboot).
If a halt_script_timeout is specified, it should be greater than the sum of all the values set
for service_halt_timeout (page 178) for this package.
6.1 Choosing Package Modules 171