Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Reviewing Serviceguard Manager Log Files
From the System Management Homepage (SMH), click Tools, then select Serviceguard
Manager, select the cluster you are interested and then choose View -> Operation Log.
Reviewing the System Multi-node Package Files
If you are running Veritas Cluster Volume Manager and you have problems starting the cluster,
check the log file for the system multi-node package. For CVM 4.1 and later, the file is
SG-CFS-pkg.log.
Reviewing Configuration Files
Review the following ASCII configuration files:
• Cluster configuration file.
• Package configuration files.
Ensure that the files are complete and correct according to your configuration planning worksheets.
Reviewing the Package Control Script
Ensure that the package control script is found on all nodes where the package can run and that
the file is identical on all nodes. Ensure that the script is executable on all nodes. Ensure that the
name of the control 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. By default, it is
found at /etc/cmcluster/<package_name>/control_script.log; but another location
may have been specified in the package configuration file’s script_log_file parameter. This
log documents all package run and halt activities. If you have written a separate run and halt script
for a legacy 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.
318 Troubleshooting Your Cluster