Error Message

VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
 

The VxVM drivers reside under /etc/vx/kernel, but links to these files should also exist under /lib/modules. If the links are missing, then vxconfigd will not start properly.
 

For example on a RHEL 7.9 (3.10.0-1160.59.1.el7.x86_64 kernel) system:
 

# ls -l /etc/vx/kernel | egrep '(vxio|vxdmp|vxspec)'
-rw-r--r--. 1 root root  912704 Apr  1 00:48 vxdmp.ko.3.10.0-1062.el7.x86_64
-rw-r--r--. 1 root root  912704 Apr  1 00:48 vxdmp.ko.3.10.0-1127.el7.x86_64
-rw-r--r--. 1 root root  910904 Apr  1 00:48 vxdmp.ko.3.10.0-862.el7.x86_64
-rw-r--r--. 1 root root  912704 Apr  1 00:48 vxdmp.ko.3.10.0-957.el7.x86_64
-rw-r--r--. 1 root root 7690408 Apr  1 00:48 vxio.ko.3.10.0-1062.el7.x86_64
-rw-r--r--. 1 root root 7690408 Apr  1 00:48 vxio.ko.3.10.0-1127.el7.x86_64
-rw-r--r--. 1 root root 7688088 Apr  1 00:48 vxio.ko.3.10.0-862.el7.x86_64
-rw-r--r--. 1 root root 7690408 Apr  1 00:48 vxio.ko.3.10.0-957.el7.x86_64
-rw-r--r--. 1 root root   13216 Apr  1 00:48 vxspec.ko.3.10.0-1062.el7.x86_64
-rw-r--r--. 1 root root   13216 Apr  1 00:48 vxspec.ko.3.10.0-1127.el7.x86_64
-rw-r--r--. 1 root root   13208 Apr  1 00:48 vxspec.ko.3.10.0-862.el7.x86_64
-rw-r--r--. 1 root root   13216 Apr  1 00:48 vxspec.ko.3.10.0-957.el7.x86_64

# ls -l /lib/modules/*/veritas/vxvm
/lib/modules/3.10.0-1160.21.1.el7.x86_64/veritas/vxvm:
total 0

/lib/modules/3.10.0-1160.45.1.el7.x86_64/veritas/vxvm:
total 0

/lib/modules/3.10.0-1160.59.1.el7.x86_64/veritas/vxvm:
total 0
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 dmpaaa.ko -> /etc/vx/kernel/dmpaaa.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 46 Apr  1 10:38 dmpaa.ko -> /etc/vx/kernel/dmpaa.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 48 Apr  1 10:38 dmpalua.ko -> /etc/vx/kernel/dmpalua.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 dmpapf.ko -> /etc/vx/kernel/dmpapf.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 dmpapg.ko -> /etc/vx/kernel/dmpapg.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 46 Apr  1 10:38 dmpap.ko -> /etc/vx/kernel/dmpap.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 52 Apr  1 10:38 dmpCLARiiON.ko -> /etc/vx/kernel/dmpCLARiiON.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 51 Apr  1 10:38 dmpEngenio.ko -> /etc/vx/kernel/dmpEngenio.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 50 Apr  1 10:38 dmphuawei.ko -> /etc/vx/kernel/dmphuawei.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 dmpinv.ko -> /etc/vx/kernel/dmpinv.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 48 Apr  1 10:38 dmpjbod.ko -> /etc/vx/kernel/dmpjbod.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 48 Apr  1 10:38 dmpkove.ko -> /etc/vx/kernel/dmpkove.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 49 Apr  1 10:38 dmpnalsi.ko -> /etc/vx/kernel/dmpnalsi.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 55 Apr  1 10:38 dmpsun7x10alua.ko -> /etc/vx/kernel/dmpsun7x10alua.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 dmpsvc.ko -> /etc/vx/kernel/dmpsvc.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 48 Apr  1 10:38 dmpvmax.ko -> /etc/vx/kernel/dmpvmax.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 46 Apr  1 10:38 vxdmp.ko -> /etc/vx/kernel/vxdmp.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 45 Apr  1 10:38 vxio.ko -> /etc/vx/kernel/vxio.ko.3.10.0-1127.el7.x86_64
lrwxrwxrwx. 1 root root 47 Apr  1 10:38 vxspec.ko -> /etc/vx/kernel/vxspec.ko.3.10.0-1127.el7.x86_64
 

Prior to performing the below steps, ensure the VRTSveki package (rpm) has also been updated and vxinstall has been executed.


Steps
 

If the links are missing and/or vxconfigd is not starting up properly, then the following steps can be performed to resolve the issue:

1.] Create the "install-upgrade" file

# touch /etc/vx/reconfig.d/state.d/install-upgrade   

2.] Start the "vxvm-boot" service

# systemctl start vxvm-boot.service 

3.] Check the Veritas driver files

# ls -l /lib/modules/*/veritas/vxvm

Links to the drivers show be displayed.

4.] Check the status of the "vxvm-boot" service 

# systemctl status vxvm-boot.service

   Loaded: loaded (/usr/lib/systemd/system/vxvm-boot.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2022-12-16 03:30:05 PST; 2h 10min ago
  Process: 3386 ExecStart=/etc/vx/vxvm-boot start (code=exited, status=0/SUCCESS)
 Main PID: 3936 (vxconfigd)
    Tasks: 4 (limit: 48852)
   Memory: 54.3M
   CGroup: /system.slice/vxvm-boot.service
           3936 vxconfigd -x syslog

5.] Check to see if vxconfigd is running and VxVM commands are working

# vxdctl mode

# vxdisk list
 

6.] If vxconfigd is still not running, then run 'vxinstall' and answer 'y' to re-install and 'n' to the subsequent questions

# vxinstall
 

7.] Check to see if vxconfigd is now running and VxVM commands are working

# vxdctl mode

# vxdisk list
 

8.] If vxconfigd is still not running, then collect the following outputs and contact Veritas Technical Support for assistance:

    a) # ls -lai /etc/vx/reconfig.d/state.d/ 

    b) # systemctl status vxvm-boot.service

    c) File: /var/log/messages

    d) # ls -l /lib/modules/*/veritas/vxvm