Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Troubleshooting Your Cluster
Solving Problems
Chapter 8284
Quorum Server Messages
The coordinator node in Serviceguard sometimes sends a request to the
quorum server to set the lock state. (This is different from a request to
obtain the lock in tie-breaking.) If the quorum server’s connection to one
of the cluster nodes has not completed, the request to set may fail with a
two-line message like the following in the quorum server’s log file:
Oct 008 16:10:05:0: There is no connection to the applicant
2 for lock /sg/lockTest1
Oct 08 16:10:05:0:Request for lock /sg/lockTest1 from
applicant 1 failed: not connected to all applicants.
This condition can be ignored. When the failure happens, the QS client
within cmcld on the coordinator node does not log anything, but tries the
request again within a few seconds. This request succeeds because the
connections to all nodes have completed. The following message is
logged:
Oct 008 16:10:06:0: Request for lock /sg/lockTest1
succeeded. New lock owners: 1,2.
Lock LUN Messages
If the lock LUN device fails, the following message will be entered in the
syslog file:
Oct 008 16:10:05:0: WARNING: Cluster lock lun /dev/sdc1 has
failed.