Error Unknown symbol gab_imc_deport is seen when vxfen module attempts to load on boot up.

Article: 100009171
Last Published: 2013-04-12
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

VxFEN is starting before GAB when cluster node is rebooted.

Error Message

# /etc/init.d/vxfen start
Starting vxfen..
GAB /sbin/gabconfig ERROR V-15-2-25022 unknown error
ERROR: No appropriate modules found.
Error in loading module "vxfen". See documentation.
VxFEN:Error: cannot find compatible module binary
VxFEN:ERROR: module load failed
...Exiting

/var/log/messages
Apr 11 13:58:57 rhel64-02 kernel: vxfen: Unknown symbol gab_imc_deport
Apr 11 13:58:57 rhel64-02 kernel: vxfen: Unknown symbol gab_imc_import

Cause

The default runlevel on RHEL6 is runlevel 3.

# cat /etc/inittab |grep id:
id:3:initdefault:

# Default runlevel. The runlevels used are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
 

If startup scripts are disabled using chkconfig command and not turned back on the result will be that SYMANTEC SFHA modules will not load in the required order.

example,
chkconfig --level 3 gab off

The above command will unlink the gab startup script that gets initiated at runlevel 3. In which case other startup scripts like LLT and VxFEN will start, because VxFEN requires GAB to be loaded at boot time. You will see the error message "Unknown symbol gab_imc_deport".

 

Solution

If runlevels are turned off for Veritas startup scripts ensure that you reenable them.

Make a backup the current runlevels prior to turning them off.

chkconfig --list > /tmp/chkconfig.lst

If you have disabled the startup script reenable it. Example,
chkconfig --level 3 gab on

Reenabling the startup script above will correctly link the /etc/rc.d/rc3.d/S67gab script to /etc/init.d/gab.

# ls -al  /etc/rc.d/rc3.d/S*gab
lrwxrwxrwx 1 root root 13 Feb 20 20:22 /etc/rc.d/rc3.d/S67gab -> ../init.d/gab
 

Note: If Storage Foundation High Availability components are not starting up on reboot of a node. Check the runlevel scripts that are on vs the scripts that are located in /etc/rc.d. Another location to check is /etc/sysconfig. We have files located in /etc/sysconfig for vxfen, llt, gab, vcs, and vcsmm. If startup variables in the files are set to 0. The startup scripts will be skipped. If the startup variable is set to 1 the startup script will be initiated.


Applies To

Storage Foundation (SF) High Availability (HA) Solutions 6.x and later

Linux distributions supported by Storage Foundation High Availability 6.x

Was this content helpful?