Vxconfigd daemon fails to start and generates a core dump

book

Article ID: 100025678

calendar_today

Updated On:

Description

Error Message

# vxconfigd -k -x syslog
VxVM vxconfigd ERROR V-5-1-0 Segmentation violation - core dumped

Core Stack
# pstack core
core 'core' of 29319:   vxconfigd -k -x syslog
 00117758 dg_creat_tempdb (5978f0, 1597, 30581c, 355e38, 355e50, 355cf0) + 130
 00169878 mode_set (2, ffbffbf0, 0, 0, 0, 0) + dc8
 0015c620 setup_mode (2, 30371c, 3036ec, 0, 6c650000, 6c650000) + 18
 0015c544 startup  (0, ffbffd64, 303354, 2, 403cbc, 3) + 36c
 0015bee4 main     (2, ffbffd64, ffbffd70, 349c00, 0, 0) + 147c
 00045cb0 _start   (0, 0, 0, 0, 0, 0) + b8

Resolution

Start vxconfigd with the reset option to start it successfully.

# vxconfigd -k -r reset -x syslog 

-r reset  Resets all Veritas Volume Manager configuration iinformation stored in the kernel as part of startup processing. Please note the reset fails if any volume devices are in use, or if an imported shared disk group exists.

If the system has encapsulated bootdisk, we need to do a reconfigure reboot using:

# reboot -- -r


Issue/Introduction

Vxconfigd daemon fails to start and generates a core dump. No diskgroups are imported on the system. Restarting vxconfigd with -x cleartempdir also fails and generates core dump.