Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

85Error messages
Understanding messages
V-5-1-2353
VxVM vxconfigd ERROR V-5-1-2353 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:
1 Ensure that no vxvol, vxplex, or vxsd processes are running.
Use ps -e to search for such processes, and use kill to kill any that
you find. You may have to run kill twice to make these processes go
away. Killing utilities in this way may make it difficult to make
administrative changes to some volumes until the system is rebooted.
2 Recreate the temporary database files for all imported disk groups
using the following command:
# vxconfigd -x cleartempdir 2> /dev/console
The vxvol, vxplex, and vxsd commands make use of these tempdb
files to communicate locking information. If the file is cleared, then
locking information can be lost. Without this locking information, two
utilities can end up making incompatible changes to the configuration
of a volume.
V-5-1-2524
VxVM vxconfigd ERROR V-5-1:2524 VOL_IO_DAEMON_SET failed: daemon
count must be above
N while cluster
■ Description: The number of Veritas Volume Manager kernel daemons
(vxiod) is less than the minimum number needed to join a cluster.
■ Action: Increase the number of daemons using vxiod.
V-5-1-2630
VxVM vxconfigd WARNING V-5-1-2630 library and vxconfigd disagree on
existence of client number
■ Description: This warning may safely be ignored.
■ Action: None required.