Storage Foundation 5.1SP1RP2P2: vxconfigd crashed & dumped core in volboot_match_hostid() when it called strncmp().

Article:TECH183360  |  Created: 2012-03-08  |  Updated: 2012-03-08  |  Article URL http://www.symantec.com/docs/TECH183360
Article Type
Technical Solution

Product(s)

Environment

Issue



Storage Founadtion 5.1SP1RP2P2: vxconfigd crashed & dumped core in volboot_match_hostid() when it called strncmp().


Error



Stack:
core '/core' of 5997:   vxconfigd -k
 ff102d60 strncmp  () + 2c 

 0014a6a8 volboot_match_hostid () + 14
 000ca470 dg_auto_import_all () + 4dc
 0010b790 mode_set () + aec
 001006bc setup_mode () + 24
 0010060c startup  () + 2d4
 000ffe04 main     () + fb8
 00040ad8 _start   (0, 0, 0, 0, 0, 0) + 108

 


Cause




## That the VM license has expired, could be causing this problem.

Mar  8 08:21:42 hstst724 vxvm:vxconfigd: [ID 702911 daemon.error] V-5-1-1589 enable failed: License has expired or is not available for operation
Mar  8 08:21:42 hstst724 vxvm:vxconfigd: [ID 702911 daemon.error]       transactions are disabled.
 


Solution




On Solaris 10, I was able to get it to work by not installing the temporary Veritas license. vxconfigd would dump coe after installing the temporary license. Without a temporary license, vxconfigd works just fine. Please refer vxkeyless utility and check # /opt/VRTSvlic/bin/vxkeyless displayall
 

vxconfigd starts without Storage Foundation (SF) 5.1 temporary key, and does not crash showing the above stack.

It's recommended to use SF's PERMANENT key instead of temporary key.

 




Article URL http://www.symantec.com/docs/TECH183360


Terms of use for this information are found in Legal Notices