Cluster lock disk is missing

[LUIS F. GARCIA JARA]

Hi there !

I have a problem on two MC/SG Clusters running HP-UX 10.20 and MC/SG 10.06 with PHNE_7495 and PHSS_20577.

In fixed time periods, cmcld sends a message to syslog.log reading:
"WARNING: Cluster lock on disk /dev/dsk/cXtXdX is missing!
Until it is fixed, a single failure could cause all nodes in the cluster to crash"

We never have had any problem regarding package switching on the nodes, but are concerned about the message.

Anybody knows if there is a patch missing, or workarounds to this message ?

Thanx in advance !

[James R. Ferguson · Accepted solution]

Hi:

For a description and a resolution, see document #W3618850. In part, this reads:

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.

The following fix will help regardless of the reason for the disk lock problem:

1. Halt the packages and cluster.

2. A. De-activate the cluster lock VG:

vgchange -a n

Note: You must de-activate the volume group on all nodes in the cluster, and then activate the volume group on the node from which you will run cmapplyconf.

B. If necessary, execute the following command on the VG:

vgchange -c n

3. Update the cluster binary configuration file:

cmcheckconf

4. Re-distribute the cluster binary configuration file:

cmapplyconf

You get the message once every hour because that is the frequency at which MC/ServiceGuard checks the connectivity with the cluster lock disk. This helps prevent a surprise node failure.

...JRF...

[sung-hoon chang]

Hi

If you replaced or moved to a different disk the cluster lock disk,

At first, execute cmdeleteconf and then try to cmcheckconf and cmapplyconf.

[melvyn burnard]

The message you are seeing indicates that cmcld is unable to poll the disk that the SG binary has marked as the CL disk.
This iwll have NOTHING to do with switching packages, but what WILL happen is if you lose one node, the othere will try to get the cluster lock disc and fail. As a result it will TOC, so you lose that node as well.
You must fix this asap.
do:
cmhaltcl
vgchange -c n
vgchange -a y
cd /etc/cmcluster
cmapplyconf -v -C -P and repeat the -P for every package
vgchange -a n
cmruncl


I would also advise you to consider moving to a newer version of MC/SG, such as 10.12

[Manuales]

What is the function of the following command?

and how can i know the file as ascci and pkg_conf_file what is that file?

cmapplyconf -v -C
-P and repeat the -P for every package

vgchange -a n
cmruncl

I'm new worker on this one ..

Thanks ...