Managing HP Serviceguard for Linux Ninth Edition, April 2009

NO_RESTART.
Dec 14 14:34:45 star04 cmcld[2048]: Examine the file
/usr/local/cmcluster/pkg5/pkg5_run.log for more details.
The following is an example of a successful package starting:
Dec 14 14:39:27 star04 CM-CMD[2096]: cmruncl
Dec 14 14:39:27 star04 cmcld[2098]: Starting cluster management protocols.
Dec 14 14:39:27 star04 cmcld[2098]: Attempting to form a new cluster
Dec 14 14:39:27 star04 cmclconfd[2097]: Command execution message
Dec 14 14:39:33 star04 cmcld[2098]: 3 nodes have formed a new cluster
Dec 14 14:39:33 star04 cmcld[2098]: The new active cluster membership is:
star04(id=1), star05(id=2), star06(id=3)
Dec 14 17:39:33 star04 cmlvmd[2099]: Clvmd initialized successfully.
Dec 14 14:39:34 star04 cmcld[2098]: Executing '/usr/local/cmcluster/conf/pkg4/pkg4_run
start' for package pkg4.
Dec 14 14:39:34 star04 LVM[2107]: vgchange /dev/vg01
Dec 14 14:39:35 star04 CM-pkg4[2124]: cmmodnet -a -i 15.13.168.0 15.13.168.4
Dec 14 14:39:36 star04 CM-pkg4[2127]: cmrunserv Service4 /vg01/MyPing 127.0.0.1
>>/dev/null
Dec 14 14:39:36 star04 cmcld[2098]: Started package pkg4 on node star04.
Reviewing Object Manager Log Files
The Serviceguard Object Manager daemon cmomd logs messages to the file
/usr/local/cmom/cmomd.log on Red Hat and /var/log/cmmomcmomd.log on
SUSE. You can review these messages using the cmreadlog command, for example:
/usr/local/cmom/bin/cmreadlog /usr/local/cmom/log/cmomd.log
Messages from cmomd include information about the processes that request data from
the Object Manager, including type of data, timestamp, etc.
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
For legacy packages, 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 can be found in the package’s
control script log. This log provides the history of the operation of the package, including
all package run and halt activities. The location of the file is determined by the
script_log_file parameter (page 200) in the package configuration file. If you have written
a separate run and halt script for a legacy package, each script will have its own log.
280 Troubleshooting Your Cluster