What needs to check if vxconfigd cannot starts up during the system boot up with error "VxVM sysboot WARNING V-5-0-0 Error starting vxconfigd"

book

Article ID: 100024184

calendar_today

Updated On:

Description

Error Message

[ ERROR MESSAGES ]
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
VxVM sysboot WARNING V-5-0-0 Error starting vxconfigd

Cause

- During the VxVM upgrading, copying the libraries under /lib to /etc/vx/slib directory was failed due to some reason.

Resolution

 

[ FINDNIGS AND SUGGESTION ]
1. From the console messages, the followings was shown up.
 
[ ERROR MESSAGES ]
VxVM sysboot INFO V-5-2-3409 starting in boot mode...
VxVM sysboot WARNING V-5-0-0 Error starting vxconfigd
 
 
2. According to the /etc/init.d/vxvm-sysboot script ( vxconfigd daemon was able to start up by manual but it failed to start up automatically only during the system boots up )
1) There was something wrong with the following lines due to the missing libraries in /etc/vx/slib such as libc.so.1
 
### /etc/init.d/vxvm-sysboot ###
-------------------------------------------------------------------
$UMIECHO "VxVM sysboot INFO V-5-2-3409 starting in boot mode..."
 
LD_LIBRARY_PATH=/etc/lib:/etc/vx/slib vxconfigd $vxconfigd_opts -m boot > /dev/null 2>&1 ret=$?       <<< This command has problem then the error messages turned out as a result of library missing.
 
if [ $ret = 0 ]; then
      $UMIECHO "VxVM sysboot INFO V-5-2-3390 Starting restore daemon..."
 
      vxdmpadm stop restore > /dev/null 2>&1
      vxdmpadm start restore $restore_daemon_opts > /dev/null 2>&1
      exit 0
else
      $UMIECHO "VxVM sysboot WARNING V-5-0-0 Error starting vxconfigd"
fi
-------------------------------------------------------------------
 
 
2) And the more accurate error messages came out as a result of the command line above
symc-solaris:/ # /slib vxconfigd $vxconfigd_opts -m boot                          <                                
ld.so.1: vxconfigd: fatal: libc.so.1: version `SUNW_1.22' not found (required by file /sbin/vxconfigd)
ld.so.1: vxconfigd: fatal: libc.so.1: open failed: No such file or directory
Killed
 
 
4. So therefore, to fix the problem, the files in /etc/vx/slib directory were re-copied from /lib.
It is because that it seems that there was problem with upgrading installer where calls for /etc/init.d/vxvm-startup2
 
 
### /etc/init.d/vxvm-startup2 ###
-------------------------------------------------------------------
# Need to make sure Veritas private slib stuff is up to date.
# Long term solution is to eliminate these shared
# library dependency altogether.
LD_LIBS=/etc/lib:/usr/lib/lwp:/usr/lib:/usr/platform/`uname -i`/lib;
if [ "$rel" = "5.10" -o "$rel" = "5.11" ]
then
        # For Solaris 10 release, only copy the vxvm
        # libraries (libvx).
        # Stop vxconfigd before copying libraries as to avoid corruption.
        SO_LIBS=`LD_LIBRARY_PATH=$LD_LIBS ldd /sbin/vxconfigd | awk '$NF ~ /libvx/ { print $NF; }'`;
        stop_vold=0;
        for SO_LIB in ${SO_LIBS.EN_US};
        do
                name=`basename ${SO_LIB.EN_US}`
                cmp -s ${SO_LIB.EN_US} /etc/vx/slib/${NAME.EN_US} || {
                [ $stop_vold -eq 0 ] && {
                        stop_vold=1; vxdctl stop;
                }
                cp -f ${SO_LIB.EN_US} /etc/vx/slib;
                }
        done
else
        SO_LIBS=`LD_LIBRARY_PATH=$LD_LIBS ldd /sbin/vxconfigd | awk '$NF ~ /\/usr\// { print $NF; }'`;
        # Copy all library files needed for vxconfigd from /usr/lib to /etc/vx/slib
        # Stop vxconfigd before copying libraries as to avoid corruption.
        stop_vold=0;
        for SO_LIB in ${SO_LIBS.EN_US};
        do
                name=`basename ${SO_LIB.EN_US}`
                cmp -s ${SO_LIB.EN_US} /etc/vx/slib/${NAME.EN_US} || {
                [ $stop_vold -eq 0 ] && {
                        stop_vold=1; vxdctl stop;
                }
                cp -f ${SO_LIB.EN_US} /etc/vx/slib;
                }
        done
-------------------------------------------------------------------
 
5. Afterwards, vxconfigd started up without a fail while the system came up several times.

Applies To

[ VERSION OF OS/PACKAGE ]
Solaris 10
SF5.0MP1

Issue/Introduction

Since SF4.1 got upgraed to 5.0MP1, vxconfigd daemon failed to start up during system booting.