HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook Rev 13.00 Page 80 (of 108)
Chapter 15 Serviceguard
October 29, 2013
daemon, /usr/lbin/cmcld [####], died upon receiving signal number 11.
The kernel parameter maxssiz was set too low. Change maxssiz back to its previous setting.
cmcld: WARNING: Cluster lock on disk /dev/dsk/cXtYdZ is missing.
Until is fixed, a single failure could cause all nodes in the cluster to
crash.
This event has been known to be caused by the following:
a. During the most recent cluster configuration, the cluster lock VG was active in vgchange -a y
on one of the adoptive nodes in the cluster.
b. The cluster lock disk was replaced or moved to a different disk.
Insure the cluster lock VG is listed in /etc/lvmtab and that the cluster binary file uses the correct
device special file (cmapplyconf).
Problems with SAP-Package-Start
For DEBUGGING purposes, the following steps can be used to start
Serviceguard in Debug mode:
1. If the package is running, run "cmhaltpkg -v <pkgname>".
2. Run the following unix command on the ServiceGuard nodes:
touch /etc/cmcluster/<SID>/debug
3. Next, enter:
cmrunpkg -n <failover_node> -v <pkgname>
At this point, the package should start without starting the DataBase or SAP.
4. Now, just specify the SAP startup script and observe. This method avoids executing
Serviceguard SAP script.
Intermittent Cluster Reformations
• Problem: Intermittent cluster reformations with possible node TOC
If a node does not receive a heartbeat from a remote node within the NODE_TIMEOUT interval,
then that node will be timed out. At that time all cluster nodes enter the cluster reformation
process. If the heartbeat interval is one second, and the node timeout interval is two seconds, it
takes two consecutive missed heartbeats to cause the node to time out, and a cluster reformation
to start. Cluster reformation involves informing all nodes of the reformation (including the node