VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages
Cluster Error Messages
77
Upgrade operation failed: Version out of range for at least one node
Description:Beforetrying toupgrade acluster byrunning vxdctl upgrade, all nodes
should beable to support the new protocolversion. An upgrade canfail if atleast one
of them does not support the new protocol version.
Action: Make sure that the VERITAS Volume Manager package that supports the new
protocol version is installed on all nodes and retry the upgrade.
Version out of range for at least one node
Description: One or more nodes in the cluster do not support the protocol version that
would result from a protocol upgrade.
Action: Make sure that the latest version of VxVM is installed on all nodes in the
cluster.
Vol recovery in progress
Description: A node that crashed attempted to rejoin the cluster before its DRL map
was merged into the recovery map.
Action: Retry the join when the merge operation has completed.
vxconfigd not ready
node number: vxconfigd is not communicating properly
Description: The vxconfigd daemon is not responding properly.
Action: Stop and restart the vxconfigd daemon.
vxclust not there
Description: An error during an attempt to join the cluster caused vxclust to fail.
This may be caused by the failure of another node during a join or by the failure of
vxclust.
Action: Retry the join. An error message on the other node may clarify the problem.
vxiod count must be above number to join cluster
Description: The number of VERITAS Volume Manager kernel daemons (vxiod) is
less than the minimum number needed to join the cluster.
Action: Increase the number of daemons using vxiod.
vxvm:vxconfigd: group group exists
Description: A slave tried to join a cluster, but ashared disk group already existsin the
cluster with the same name as one of its private disk groups.
Action: Use the vxdg newname operation to rename either the shared disk group on
the master, or the private disk group on the slave.