After upgrade to 7.4.2, vxconfigd core dumps after node tries to become CVM slave
Article ID: 100053087
Updated On:
Description
Error Message
Issue reported in file /var/VRTSvcs/log/CVMVxconfigd_A.log
VCS ERROR V-16-20028-1005 CVMVxconfigd:cvm_vxconfigd:monitor:vxconfigd core dumped…
Cause
Issue happens because of an inability of vxtune to successfully run during the node's attempt to become a CVM slave. This becomes apparent when assessing the stack of the core dump:
core '/var/tmp/core.24710' of 955: vxconfigd -x syslog -m boot
------------ lwp# 1 / thread# 1 ---------------
00258b34 vol_print_tunables (1300, 3d6490, ffbfecf0, 0, ffbfeae0, ffbfea60) + 1184
000868ec vol_get_tunableinfo (ffbfeeec, 481178, dc, 3d6490, ffbfeae0, 0) + 170
00086590 send_tunableinfo (4dd5f18, 41a1c58, 2d8800, 481178, 398800, 398970) +134
00132088 req_slave_tunableinfo (4dd5f18, 40ed20, 13200c, 486774, 481178, 2fa800) + 7c
0016d4e4 request_loop (1, 3ec794, 4dd5f18, 0, 40edd8, 1) + c94
00130ec0 main (397000, ffbffb0c, ffffffff, 3ea710, 0, 2f962c) + f28
00053640 _start (0, 0, 0, 0, 0, 0) + 108
It transpired that the upgrade would have some issue, such that when assessing the checksum of /usr/sbin/vxconfigd, it finds it incorrect. This causes the vxconfigd daemon to dump core.
Resolution
To resolve the issue, the VRTSvxvm package needs to be reinstalled, which would then stop the vxconfigd to generate any further core dumps.
Issue/Introduction
