GAB fails to start with ERROR V-15-2-25015 LLT not configured
Article ID: 100034300
Updated On:
Description
Error Message
Error returned when GAB tries to start:/etc/init.d/gab start
Starting GAB:
Loaded 2.6.32-71.el6.x86_64 on kernel 2.6.32-220.el6.x86_64
WARNING: No modules found for 2.6.32-220.el6.x86_64, using compatible modules for 2.6.32-71.el6.x86_64.
GAB /sbin/gabconfig ERROR V-15-2-25015 LLT not configured
Starting GAB:
Loaded 2.6.32-71.el6.x86_64 on kernel 2.6.32-220.el6.x86_64
WARNING: No modules found for 2.6.32-220.el6.x86_64, using compatible modules for 2.6.32-71.el6.x86_64.
GAB /sbin/gabconfig ERROR V-15-2-25015 LLT not configured
Permission errors on the following LLT (Low Latency Transport) and GAB files confirm the issue:
cat /proc/vximc/gab
cat: /proc/vximc/gab: Permission denied
cat /proc/vximc/llt
cat: /proc/vximc/llt: Permission denied
cat: /proc/vximc/gab: Permission denied
cat /proc/vximc/llt
cat: /proc/vximc/llt: Permission denied
Workaround
1. Remount the /proc file system without any options.
mount -o remount /proc
2. Start GAB.
# /sbin/gabconfig -c -n2
A permanent solution would be to upgrade to 6.0.1, or above, Beginning with this version, Veritas uses files in /proc/vximc and not character devices, as in 6.0.
Cause
GAB is not able to communicate with LLT.
/proc/vximc is the intercommunication protocol used by GAB to communicate with LLT. This directory will have the LLT, GAB or VxFEN (Fencing) related files when the corresponding modules are loaded. The /proc file system was mounted with “nosuid,noexec,nodev “ options.
On RHEL (Red Hat Enterprise Linux) 6.2 and RHEL 6.3, /proc is mounted using the following syntax:
init:mount -t proc -o nosuid,noexec,nodev proc /proc >/dev/null 2>&1
On RHEL 6.5, the following syntax is used:
This appears to only effect VCS (Veritas Cluster Server) 6.0.
/proc/vximc is the intercommunication protocol used by GAB to communicate with LLT. This directory will have the LLT, GAB or VxFEN (Fencing) related files when the corresponding modules are loaded. The /proc file system was mounted with “nosuid,noexec,nodev “ options.
On RHEL (Red Hat Enterprise Linux) 6.2 and RHEL 6.3, /proc is mounted using the following syntax:
init:mount -t proc -o nosuid,noexec,nodev proc /proc >/dev/null 2>&1
On RHEL 6.5, the following syntax is used:
init:mount -t proc proc /proc >/dev/null 2>&1
This appears to only effect VCS (Veritas Cluster Server) 6.0.
Issue/Introduction
After a node reboot, GAB (Global Atomic Broadcast) will fail to start. Reconfiguring GAB generates the same error.
Additional Information
UMI: V-15-2-25015
Was this article helpful?
Yes
No
Powered by
