How to turn on vxconfigd debug logging in Volume Manager (VxVM) at boot for Solaris OS

book

Article ID: 100020983

calendar_today

Updated On:

Resolution

1. Move or remove the existing vxconfigd log file.

  # mv /var/vxvm/vxconfigd.log /var/vxvm/vxconfigd.log.BAK

2. Backup the VxVM startup script before modifying it:

  # cp /lib/svc/method/vxvm-sysboot   /lib/svc/method/vxvm-sysboot.BAK

3. Edit the  file /lib/svc/method/vxvm-sysboot to enable vxconfigd debugging.
 
 
 
Valid debug levels are 0 (off / variable is commented) through 9 (maximum debugging).
---------------------------------------------------------------------------------
section before modification : ( /lib/svc/method/vxvm-sysboot)
---------------------------------------------------------------------------------
opts="$opts -x syslog"                  # use syslog for console messages
#opts="$opts -x log"                    # messages to /var/vxvm/vxconfigd.log
#opts="$opts -x logfile=/foo/bar"       # specify an alternate log file
#opts="$opts -x timestamp"              # timestamp console messages
# to turn on debugging console output, uncomment the following line.
# The debug level can be set higher for more output.  The highest debug
# level is 9.
#debug=1                                # enable debugging console output
[ -n "$debug" ] && {
       opts="$opts -x $debug"          # set debugging to the requested level
}
vxconfigd_opts=$opts


---------------------------------------------------------------------------------
section after modification : ( /lib/svc/method/vxvm-sysboot)
---------------------------------------------------------------------------------
opts="$opts -x syslog"                  # use syslog for console messages
opts="$opts -x log"                     # messages to /var/vxvm/vxconfigd.log
#opts="$opts -x logfile=/foo/bar"       # specify an alternate log file
#opts="$opts -x timestamp"               # timestamp console messages
opts="$opts -x mstimestamp"               # timestamp console messages - in milliseconds
# to turn on debugging console output, uncomment the following line.
# The debug level can be set higher for more output.  The highest debug
# level is 9.
 
debug=9                 # enable debugging console output

[ -n "$debug" ] && {
       opts="$opts -x $debug"          # set debugging to the requested level
}
vxconfigd_opts=$opts
---------------------------------------------------------------------------------

4. Reboot the system.
Upon boot, vxconfigd will start in debug mode.
 
 
To disable vxconfigd debug logging:
===================================

a) Without rebooting :

  # vxdctl stop
  # vxconfigd -k

 Note that the changes in /lib/svc/method/vxvm-sysboot are still present.
The  vxconfigd debug setting will remain and debug level will be active again on next reboot

b) Permanently disable vxconfigd debug logging :
  1. Undo the changes in /lib/svc/method/vxvm-sysboot
  # cp /lib/svc/method/vxvm-sysboot.BAK  /lib/svc/method/vxvm-sysboot

  2.Reboot the system
  Upon boot, vxconfigd debugging is disabled.
 

 

 

 

Issue/Introduction

In some instances it is necessary for Technical Support to gather data which details precisely what occurs at VxVM startup. Enabling debug logging of VxVM at startup may assist in discovery and resolution of VxVM issues. Issues to be resolved by VxVM debugging may include, but are not limited to: - failure to start the vxconfigd daemon successfully - vxconfigd coring - system panic - device discovery failures / inconsistency - patching discovery / utilization issues - OS not continuing to boot up or going to maintenance mode