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

Troubleshooting Your Cluster
Solving Problems
Chapter 8344
• ioscan -fnC disk - to see physical disks.
• diskinfo -v /dev/rdsk/cxtydz - to display information about a
disk.
• lssf /dev/dsk/*d0 - to check LV 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 the package will not be transferred.
• The run or halt instructions may not run to completion.
• Global 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.
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 package on an alternate node. This might
include such things as shutting down application processes,
removing lock files, and removing temporary files.