VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages
Cluster Error Messages
Chapter 3
87
Description: During the slave join protocol, a message without data was received
from the master. This message is only likely to be seen in the case of a programming
error.
Action: Contact Customer Support.
Missing vxconfigd
Description: The vxconfigd daemon is not running.
Action: Restart the vxconfigd daemon.
Node activation conflict
Description: The disk group could not be activated because it is activated in a
conflicting mode on another node in a cluster.
Action: Retry later, or deactivate the disk group on conflicting nodes.
Not in cluster
Description: Checking for the current protocol version (using vxdctl protocol version)
makes sense only if the node is in the cluster.
Action: Bring the node in the cluster and retry.
NOTICE: commit: NOTE: Reason found for abort: code=2
Description: This message may appear during a plex detach operation on the master
in a cluster.
Action: None required.
NOTICE: commit: NOTE: Reason found for abort: code=6
Description: This message may appear during a plex detach operation on a slave in a
cluster.
Action: None required.
NOTICE: ktcvm_check: sent to slave node: node=1 mid=196
Description: This message may appear during a plex detach operation on the master
in a cluster.
Action: None required.
NOTICE: vol_kmsg_send_wait_callback: got error 22
Description: This message may appear during a plex detach operation on a slave in a
cluster.
Action: None required.
Retry rolling upgrade
Description: An attempt was made to upgrade the cluster to a higher protocol version
when a transaction was in progress.
Action: Retry at a later time.
Return from cluster_establish is Configuration daemon error 242
Description: A node failed to join a cluster, or a cluster join is taking too long. If the
join fails, the node retries the join automatically.
Action: No action is necessary if the join is slow or a retry eventually succeeds.