gabconfig -cx fails to seed the GAB membership
Article ID: 100033464
Updated On:
Description
Workaround
Before the required patch is installed, run gabconfig -x to seed the GAB membership when GAB is already configured before.
# gabconfig -x <<< don't specify the "-c" option # gabconfig -a
GAB Port Memberships
===============================================================
Port a gen 15b501 membership 0 <<< GAB is now seeded with the "gabconfig -x" command
Cause
When the gabconfig -c and gabconfig– -cx commands are executed simultaneously, a race condition might occur, inside GAB. This causes a packet to get queued for sending. GAB fails to start.
Resolution
A fix for this issue is included in VCS 6.0.500. Veritas patches can be downloaded from here:
https://downloads.infoscale.com/
Issue/Introduction
The gabconfig -cx command fails to seed the GAB (Global Atomic Broadcast) membership. When gabconfig is run with the -cx argument, it returns the following message. But the GAB membership is not seeded.
# gabconfig -cx
GAB driver already configured. Honored other options.
The GAB membership is not seeded:
# gabconfig -a
GAB Port Memberships
===============================================================
This is not an error message and is not related to the issue. In VCS (Veritas Cluster Server) 6.0, the above message is added to the gabconfig program to indicate that the GAB driver is already configured when the -c (configure) argument is specified. The other arguments that are specified, such as -x, will still be performed (honored).
The problem is specific to VCS 6.0 versions and is resolved in VCS 6.0.500.
Additional Information
ETrack: 3140359
