Attempt to get lock /sg/cluser1 unsuccessful. Reason: request_timedout

Messages

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.

Solving Problems 339

Page 339
Image 339
HP Serviceguard manual Messages