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

Troubleshooting Your Cluster
Troubleshooting Approaches
Chapter 8 339
script appears in the package configuration file, and ensure that all
services named in the package configuration file also appear in the
package control script.
Information about the starting and halting of each package is found in
the package’s control script log. This log provides the history of the
operation of the package control script. It is found at
/etc/cmcluster/package_name/control_script.log. This log
documents all package run and halt activities. If you have written a
separate run and halt script for a package, each script will have its own
log.
Using the cmcheckconf Command
In addition, cmcheckconf can be used to troubleshoot your cluster just as
it was used to verify the configuration.
The following example shows the commands used to verify the existing
cluster configuration on ftsys9 and ftsys10:
# cmquerycl -v -C /etc/cmcluster/verify.ascii -n ftsys9 -n
ftsys10
# cmcheckconf -v -C /etc/cmcluster/verify.ascii
The cmcheckconf command checks:
• The network addresses and connections.
• The cluster lock disk connectivity.
• The validity of configuration parameters of the cluster and packages
for:
— The uniqueness of names.
— The existence and permission of scripts.
It doesn’t check:
• The correct setup of the power circuits.
• The correctness of the package configuration script.
Using the cmscancl Command
The command cmscancl displays information about all the nodes in a
cluster in a structured report that allows you to compare such items as
IP addresses or subnets, physical volume names for disks, and other