Managing Serviceguard Eighteenth Edition, September 2010

logical volumes, as specified by the LV[] array variables in the package control
script, appear under the “Filesystem” column, use umount to unmount them:
fuser -ku <logical-volume>
umount <logical-volume>
Next, deactivate the package volume groups. These are specified by the VG[]
array entries in the package control script.
vgchange -a n <volume-group>
4. Finally, re-enable the package for switching.
cmmodpkg -e <package-name>
If after cleaning up the node on which the timeout occurred it is desirable to have
that node as an alternate for running the package, remember to re-enable the
package to run on the node:
cmmodpkg -e -n <node-name> <package-name>
The default Serviceguard control scripts are designed to take the straightforward steps
needed to get an application running or stopped. If the package administrator specifies
a time limit within which these steps need to occur and that limit is subsequently
exceeded for any reason, Serviceguard takes the conservative approach that the control
script logic must either be hung or defective in some way. At that point the control
script cannot be trusted to perform cleanup actions correctly, thus the script is terminated
and the package administrator is given the opportunity to assess what cleanup steps
must be taken.
If you want the package to switch automatically in the event of a control script timeout,
set the node_fail_fast_enabled parameter (page 301) to yes. In this case, Serviceguard will
cause the node where the control script timed out to halt (system reset). This effectively
cleans up any side effects of the package's run or halt attempt (but remember that the
system reset will cause all the packages running on that node to halt abruptly). In this
case the package will be automatically restarted on any available alternate node for
which it is configured. For more information, see “Responses to Package and Service
Failures ” (page 119).
Problems with Cluster File System (CFS)
NOTE: Check the Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility
and Feature Matrix and the latest Release Notes for your version of Serviceguard for
up-to-date information about support for CFS (www.hp.com/go/
hpux-serviceguard-docs).
If you have a system multi-node package for Veritas CFS, you may not be able to start
the cluster until SG-CFS-pkg starts. Check SG-CFS-pkg.log for errors.
You will have trouble running the cluster if there is a discrepancy between the CFS
cluster and the Serviceguard cluster. To check, use gabconfig -a.
418 Troubleshooting Your Cluster