VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

vxconfigd Error Messages
50 VERITAS Volume Manager Troubleshooting Guide
◆ Action: Manual use of the vxdg recover command may be required to clean the
disk group to be imported. See “Recovering from Incomplete Disk Group Moves” on
page 15 for more information.
vxvm:vxconfigd: ERROR: Differing version of vxconfigd installed
◆ Description: A vxconfigd daemon was started after stopping an earlier vxconfigd
with a non-matching version number. This can happen, for example, if you upgrade
VxVM and then run vxconfigd without first rebooting.
◆ Action: To fix, reboot the system.
vxvm:vxconfigd: ERROR: Disk disk, group group, device device: not updated
with new host ID
Error: reason
◆ Description: This can result from using vxdctl hostid to change the VERITAS
Volume Manager host ID for the system. The error indicates that one of the disks in a
disk group could not be updated with the new host ID. Most likely, this indicates that
the given disk has become inaccessible or has failed in some other way.
◆ Action: Try running the following command to determine whether the disk is still
operational:
# vxdisk check device
If the disk is no longer operational, vxdisk should print a message such as:
device: Error: Disk write failure
This will result in the disk being taken out of active use in its disk group, if it has not
already been taken out of use. If the disk is still operational, which should not be the
case, vxdisk prints:
device: Okay
If the disk is listed as “Okay,” try running vxdctl hostid again. If it still results in
an error, contact Customer Support.
vxvm:vxconfigd: ERROR: Disk group group: Cannot recover temp database:
reason
Consider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].
◆ Description: This can happen if you kill and restart vxconfigd, or if you disable and
enable it with vxdctl disable and vxdctl enable. This error indicates a failure
related to reading the file /var/vxvm/tempdb/group. This is a temporary file
used to store information that is used when recovering the state of an earlier
vxconfigd. The file is recreated on a reboot, so this error should never survive a
reboot.
◆ Action: If you can reboot, do so. If you do not want to reboot, then do the following: