Managing Serviceguard Sixteenth Edition, March 2009

• strings /etc/lvmtab - to ensure that the configuration is correct.
• ioscan -fnC disk - to see physical disks.
• diskinfo -v /dev/rdsk/cxtydz - to display information about a disk.
• lssf /dev/d*/* - to check logical volumes and paths.
• vxdg list - to list Veritas disk groups.
• vxprint- to show Veritas disk group details.
Package Control Script Hangs or Failures
When a RUN_SCRIPT_TIMEOUT or HALT_SCRIPT_TIMEOUT value is set, and the
control script hangs, causing the timeout to be exceeded, Serviceguard kills the script
and marks the package “Halted.” Similarly, when a package control script fails,
Serviceguard kills the script and marks the package “Halted.” In both cases, the
following also take place:
• Control of a failover package will not be transferred.
• The run or halt instructions may not run to completion.
• auto_run (automatic package switching) will be disabled.
• The current node will be disabled from running the package.
Following such a failure, since the control script is terminated, some of the package's
resources may be left activated. Specifically:
• Volume groups may be left active.
• File systems may still be mounted.
• IP addresses may still be installed.
• Services may still be running.
NOTE: Any form of the mount command other than cfsmount or cfsumount should
be used with caution in an HP Serviceguard Storage Management Suite environment
with CFS. Non-cfs commands (such as mount -o cluster, dbed_chkptmount,
or sfrac_chkptmount) could cause conflicts with subsequent command operations
on the file system or Serviceguard packages. These mount commands will not create
an appropriate multi-node package, with the result that the cluster packages are not
aware of the file system changes.
In this kind of situation, Serviceguard will not restart the package without manual
intervention. You must clean up manually before restarting the package. Use the
following steps as guidelines:
1. Perform application-specific cleanup. Any application-specific actions the control
script might have taken should be undone to ensure successfully starting the
378 Troubleshooting Your Cluster