Managing Serviceguard 14th Edition, June 2007

Cluster and Package Maintenance
Reviewing Cluster and Package Status
Chapter 7 321
• fail_wait - The package is waiting to be halted because the
package or a package it depends on has failed, but must wait for a
package that depends on it to halt before it can halt.
• relocate_wait - The package’s halt script has completed or
Serviceguard is still trying to place the package.
• unknown - Serviceguard could not determine the status at the time
cmviewcl was run.
A system multi-node package is up when it is running on all the active
cluster nodes. A multi-node package is up if it is running on any of its
configured nodes.
The state of the package can be one of the following:
• starting - The package is starting. The package master control
script is running.
• start_wait - A cmrunpkg command is in progress for this package.
The package is waiting for packages it depends on (predecessors) to
start before it can start.
• running - Services are active and being monitored.
• halting - A cmhaltpkg command is in progress for this package
and the halt script is running.
• halt_wait - A cmhaltpkg command is in progress for this package.
The package is waiting to be halted, but the halt script cannot start
because the package is waiting for packages that depend on it
(successors) to halt. The parameter description for
successor_halt_timeout (see page 284) provides more
information.
• halted - The package is down and halted.
• failing - The package is halting because it, or a package it
depends on, has failed.
• fail_wait - The package is waiting to be halted because the
package or a package it depends on has failed, but must wait for a
package it depends on to halt before it can halt.
• failed - The package is down and failed.
• relocate_wait - The package’s halt script has completed or
Serviceguard is still trying to place the package.