Managing Serviceguard 14th Edition, June 2007

Troubleshooting Your Cluster
Solving Problems
Chapter 8 409
Solving Problems
Problems with Serviceguard may be of several types. The following is a
list of common categories of problem:
• Serviceguard Command Hangs.
• Cluster Re-formations.
• System Administration Errors.
• Package Control Script Hangs.
• Problems with VxVM Disk Groups.
• Package Movement Errors.
• Node and Network Failures.
• Quorum Server Problems.
The first two categories of problems occur with the incorrect
configuration of Serviceguard. The last category contains “normal”
failures to which Serviceguard is designed to react and ensure the
availability of your applications.
Serviceguard Command Hangs
If you are having trouble starting Serviceguard, it is possible that
someone has accidentally deleted, modified, or placed files in, the
directory that is reserved for Serviceguard use only:
/etc/cmcluster/rc (HP-UX) or
${SGCONF}/rc (Linux)
Many Serviceguard commands, including cmviewcl, depend on name
resolution services to look up the addresses of cluster nodes. When name
services are not available (for example, if a name server is down),
Serviceguard commands may hang, or may return a network-related
error message. If this happens, use the nslookup command on each
cluster node to see whether name resolution is correct. For example:
nslookup ftsys9
Name Server: server1.cup.hp.com
Address: 15.13.168.63