Managing HP Serviceguard A.11.20.00 for Linux, June 2012

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 160) to YES. In this case, Serviceguard will cause
a reboot on the node where the control script timed out. This effectively cleans up any side effects
of the package’s run or halt attempt. In this case the package will be automatically restarted on
any available alternate node for which it is configured.
Package Movement Errors (Legacy Packages)
These errors are similar to the system administration errors except they are caused specifically by
errors in the package control script. The best way to prevent these errors is to test your package
control script before putting your high availability application on line.
Adding a set -x statement in the second line of your control script will give you details on where
your script may be failing.
Package startup failure due to uncleaned LVM2 hosttags
When LVM2 hosttags feature is used in Volumegroup, Serviceguard ensures that the hosttags are
cleaned up on every package halt process. However, in case of Node power failure or crash
initiated by SERVICE_FAIL_FAST / NODE_FAIL_FAST feature, hosttags will not be cleaned up. In
such cases, hosttags have to be manually cleaned up before starting the package on other node.
Following messages can be seen in the package log where package failed to startup on other
node and it also provides procedure to clean up the hosttags.
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: ERROR: Function activation_check:
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: Error vg01 may still be activated on xyz.hp.com
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: To correct this situation, logon to "xyz.hp.com " and
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: execute the following commands:
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: vgchange -a n vg01
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: vgchange --deltag xyz.hp.com vg01
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: Once "vg01" has been deactivated from “xyz.hp.com",
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: this package may be restarted via either cmmodpkg (1M)
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: or cmrunpkg(1M).
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: In the event that "xyz.hp.com" is either powered off
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: or unable to boot, then "vg01" must be forced
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: to be activated on this node.
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: ******************* WARNING ***************************
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: Forcing activation can lead to data corruption if
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: "xyz.hp.com" is still running and has "vg01"
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: active. It is imperative to positively determine that
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: "xyz.hp.com" is not running prior to performing
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: this operation.
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: *******************************************************
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: To force activate "vg01", execute the following
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: command on the local system:
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: vgchange --deltag xyz.hp.com vg01
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: The package may then be restarted via either
Feb 11 17:18:36 [e-mail] volume_group.sh[1871]: cmmodpkg (1M) or cmrunpkg (1M) commands.
236 Troubleshooting Your Cluster