Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Understanding Serviceguard Software Components
How Packages Run
Chapter 364
legacy package; for more information about configuring services in
modular packages, see the discussion starting on page 209, and the
comments in the package configuration template file.
SERVICE_RESTART[0]=" " ; do not restart
SERVICE_RESTART[0]="-r <n>" ; restart as many as <n> times
SERVICE_RESTART[0]="-R" ; restart indefinitely
NOTE If you set <n> restarts and also set service_fail_fast_enabled to yes,
the failfast will take place after <n> restart attempts have failed. It does
not make sense to set service_restart to “-R” for a service and also set
service_fail_fast_enabled to yes.
While Services are Running
During the normal operation of cluster services, the package manager
continuously monitors the following:
• Process IDs of the services
• Subnets configured for monitoring in the package configuration file
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.
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, or Subnet Fails, or a Dependency is
Not Met
What happens when something goes wrong? If a service fails and there
are no more restarts, or if a configured dependency on another package is
not met, then a failover package will halt on its current node and,
depending on the setting of the package switching flags, may be
restarted on another node. If a multi-node or system multi-node package
fails, all of the packages that have configured a dependency on it will also
fail.