VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages

Cluster Error Messages

Join not allowed now

◆ Description: A slave attempted to join a cluster when the master was not ready. The

slave will retry automatically. If the retry succeeds, the following message appears:

vxclust: slave join complete

◆ Action: No action is necessary if the join eventually completes. Otherwise, investigate

the cluster monitor on the master.

Master sent no data

◆ 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

conﬂicting mode on another node in a cluster.

◆ Action: Retry later, or deactivate the disk group on conﬂicting 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 appearduring a plexdetach operation onthe masterin

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 appearduring a plexdetach operation onthe masterin

a cluster.

◆ Action: None required.