Managing HP Serviceguard A.11.20.10 for Linux, December 2012

Unable to set client version at quorum server 192.6.7.2: reply timed
out
Probe of quorum server 192.6.7.2 timed out
These messages could be an indication of an intermittent network problem; or the default quorum
server timeout may not be sufficient. You can set the QS_TIMEOUT_EXTENSION to increase the
timeout, or you can increase the MEMBER_TIMEOUT value. See “Cluster Configuration Parameters
” (page 86)for more information about these parameters.
A message such as the following in a Serviceguard node’s syslog file indicates that the node
did not receive a reply to its lock request on time. This could be because of delay in communication
between the node and the Quorum Server or between the Quorum Server and other nodes in the
cluster:
Attempt to get lock /sg/cluser1 unsuccessful. Reason:
request_timedout
8.8.8.3 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. The request will be retried a few seconds later and will succeed.
The following message is logged:
Oct 008 16:10:06:0: Request for lock /sg/lockTest1
succeeded. New lock owners: 1,2.
8.8.9 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.
8.9 Troubleshooting serviceguard-xdc package
For information about how to troubleshoot issues related to serviceguard-xdc package, see HP
Serviceguard Extended Distance Cluster for Linux A.11.20.10 Deployment Guide at http://
www.hp.com/go/linux-serviceguard-docs.
254 Troubleshooting Your Cluster