Veritas Volume Manager 5.0 Troubleshooting Guide Guide (September 2006)

89Error messages
Understanding messages
V-5-1-3034
VxVM vxconfigd ERROR V-5-1-3034 Join not currently allowed
■ Description: A slave attempted to join a cluster when the master was not ready. The
slave will retry automatically.
■ Action: No action is necessary if the join eventually completes. Otherwise,
investigate the cluster monitor on the master.
V-5-1-3042
VxVM vxconfigd ERROR V-5-1-3042 Clustering license restricts
operation
■ Description: An operation requiring a full clustering license was attempted, and such
a license is not available.
■ Action: If the error occurs when a disk group is being activated, dissociate all but one
plex from mirrored volumes before activating the disk group. If the error occurs
during a transaction, deactivate the disk group on all nodes except the master.
V-5-1-3046
VxVM vxconfigd ERROR V-5-1-3046 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.
V-5-1-3049
VxVM vxconfigd ERROR V-5-1-3049 Retry rolling upgrade
■ Description: An attempt was made to upgrade a cluster to a higher protocol version
when a transaction was in progress.
■ Action: Retry the upgrade at a later time.
V-5-1-3050
VxVM vxconfigd ERROR V-5-1-3050 Version out of range for at least
one node
■ Description: Before trying to upgrade a cluster by running vxdctl upgrade, all
nodes should be able to support the new protocol version. An upgrade can fail if at
least one of them does not support the new protocol version.
■ Action: Make sure that the Veritas Volume Manager 5.0 package that supports the
new protocol version is installed on all nodes and retry the upgrade.