 | ||
| GAB message logging | ||
|---|---|---|
| Prev | VCS message logging | Next |
If GAB encounters some problem, then First Failure Data Capture (FFDC) logs are also generated and dumped.
When you have configured GAB, GAB also starts a GAB logging daemon (/opt/VRTSgab/gablogd). GAB logging daemon is enabled by default. You can change the value of the GAB tunable parameter gab_ibuf_count to disable the GAB logging daemon.
See About GAB load-time or static tunable parameters.
This GAB logging daemon collects the GAB related logs when a critical events such as an iofence or failure of the master of any GAB port occur, and stores the data in a compact binary form. You can use the gabread_ffdc utility as follows to read the GAB binary log files:
/opt/VRTSgab/gabread_ffdc binary_logs_files_location
You can change the values of the following environment variables that control the GAB binary log files:
GAB_FFDC_MAX_INDX: Defines the maximum number of GAB binary log files
The GAB logging daemon collects the defined number of log files each of eight MB size. The default value is 20, and the files are named gablog.1 through gablog.20. At any point in time, the most recent file is the gablog.1 file.
GAB_FFDC_LOGDIR: Defines the log directory location for GAB binary log files
The default location is:
/var/adm/gab_ffdc
Note that the gablog daemon writes its log to the glgd_A.log and glgd_B.log files in the same directory.
You can either define these variables in the following GAB startup file or use the export command. You must restart GAB for the changes to take effect.
/etc/default/gab