Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Understanding Serviceguard Software Components
How Package Control Scripts Work
Chapter 390
card. If a service fails but the RESTART parameter for that service is set
to a value greater than 0, the service will restart, up to the configured
number of restarts, without halting the package.
If there is a configured EMS resource dependency and there is a trigger
that causes an event, the package will be halted.
During normal operation, while all services are running, you can see the
status of the services in the “Script Parameters” section of the output of
the cmviewcl command.
When a Service, Subnet, or Monitored Resource Fails
What happens when something goes wrong? If a service fails and there
are no more restarts, if a subnet fails and there are no standbys, or if a
configured resource fails, then the package will halt on its current node
and, depending on the setting of the package switching flags, may be
restarted on another node.
Package halting normally means that the package halt script executes
(see the next section). However, if SERVICE_FAILFAST_ENABLED is set to
yes for the service that fails, then the node will halt as soon as the failure
is detected. If this flag is not set, the loss of a service will result in
halting the package gracefully by running the halt script.
If AUTO_RUN is set to YES, the package will start up on another eligible
node, if it meets all the requirements for startup. If AUTO_RUN is set to NO,
then the package simply halts without starting up anywhere else.
NOTE If a package is dependent on a subnet, and the subnet on the primary
node fails, then the package will start to shut down. If the subnet
recovers immediately (before the package is restarted on an adoptive
node), then the package could be restarted on the primary node.
Therefore the package does not switch to another node in the cluster in
this case.