"GAB: Driver information displayed in data field below" is reported by GAB in the Windows event viewer

Problem

Windows System event viewer indicates messages from GAB with the description "GAB: Driver information displayed in data field below."   These messages can appear in batches of 2-3 messages or can appear with several messges, which are followed by a restart of the High Availability Daemon (HAD).

Error Message

GAB Event ID 18: "GAB: Driver information displayed in data field below."

When Event ID 18 is reported by GAB, the message looks like:

0000: 00 00 3c 00 01 00 88 00 ..<...ˆ.
0008: 00 00 00 00 12 00 07 40 .......@
0010: 04 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 47 41 42 20 57 41 52 4e GAB WARN
0030: 49 4e 47 20 56 2d 31 35 ING V-15
0038: 2d 31 2d 32 30 30 35 37 -1-20057
0040: 20 50 6f 72 74 20 68 20 Port h
0048: 70 72 6f 63 65 73 73 20 process
0050: 31 20 69 6e 61 63 74 69 1 inacti
0058: 76 65 20 37 20 73 65 63 ve 7 sec
0060: 0a 00 00 00 ....

Notice the message "GAB WARNING V-15-1-20057 Port h process 1 inactive 7 sec."

Other common messages in this sequence can include any or all of the following:

GAB WARNING V-15-1-20057 Port h process 1 inactive 8 sec
...
GAB WARNING V-15-1-20057 Port h process 1 inactive 15 sec
GAB WARNING V-15-1-20058 Port h process 1: heart beat failed, killing process....
GAB INFO V-15-1-20059 Port h heartbeat interval 15000 msec. Statistics:.
GAB INFO V-15-1-20129 Port h: heartbeats in 0 ~ 3000 mse c: 9584.
GAB INFO V-15-1-20129 Port h: heartbeats in 3000 ~ 6000 msec: 0.
GAB INFO V-15-1-20129 Port h: heartbeats in 6000 ~ 9000 msec: 0.
GAB INFO V-15-1-20129 Port h: heartbeats in 9000 ~ 12000 msec: 0
GAB INFO V-15-1-20129 Port h: heartbeats in 12000 ~ 15000 msec: 0.
GAB INFO V-15-1-20041 Port h: client process failure: killing process...
GAB INFO V-15-1-20032 Port h closed.

Cause

GAB has not received heartbeat from the HAD process.

Solution

Messages from GAB are usually the result of heartbeat timeouts. By default, a 15 second threshold is allowed before a timeout occurs and had.exe is restarted.  Note in the above error field the tiemout counts every second up to 15 seconds, however if as mentioned below the timeout is changed the GAB will count up to the timeout value.
 
GAB is a kernel process that monitores the user mode process HAD.EXE.  In situations where the server is under heavy load, or is low on resources, HAD may be unable to send or acknowledge heartbeats in a timely manner.  The GAB process will always be able to run and maintain cluster membership.  If it feels that HAD not responding is a potential problem then it will close port h which effectively terminates the HAD process.  This message for the High Availability Daemon will follow the full sequence of error messages above.
 
Under normal circumstances HAD will restart and cluster operations resume as normal.  Applications online on the node will not be affected in this case.


Recommendations

1. Review the Windows event viewer to determine if any activity is taking place at the time of the GAB events that may cause the server to become busy. In particular, check for Event IDs 2019, 2020, 2021 and 2022. These events occur when system resources are running low.

2. Use the Windows Performance Monitor to track processes, processor and memory for the affected server.

3. As a workaround, the GAB timeout threshold can be increased. Further information about this can be found here:  http://www.symantec.com/business/support/index?page=content&id=TECH82933
keywords: had restart, cluster restart
 
 

Applies To

Veritas Storage Foundation HA for Windows

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)