Error Code details
Severity: n/a 
Component: Cluster Server 
GAB timeout set to %s ms

This message is written to the engine log when the high availability daemon (HAD) is started.


At startup, HAD registers with the Group Membership Services/Atomic Broadcast protocol (GAB) and sets the GAB heartbeat interval. If HAD  does not heartbeat at least once within the interval, GAB assumes a fault and kills the HAD process by sending a SIGABRT signal. The hashadow process restarts the HAD process. Such heartbeat failure can occur when the system is overloaded or is busy processing a system call.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2010-11-01 18:13:24 PDT
Platform: Generic
Release: Generic

This message is informational and requires no action. However, you can change the heartbeat interval. The following command sets the heartbeat interval to 60,000 milliseconds (60 seconds):


# export VCS_GAB_TIMEOUT=60000

# hastart

You must set the heartbeat interval through the environment variable before you start the HAD process. You cannot change the timeout value at runtime.


User solutions
No user solutions yet.


Read and accept Terms of Service