Cluster Error Messages

This section presents error messages that may occur with the Volume Manager in a cluster environment. Each message is accompanied by an explanation and a suggested user action.




	NOTE: Some of these messages may appear on the console; others are returned by `vxclust`.

Attempt to start the restore daemon that is already running

		vxvm:vxdmpadm: ERROR:The VxVM restore daemon is already
		running. To change any of its parameters, stop and restart the
		restore daemon with the new set of arguments.

Description
vxdmpadm utility returns this error message when the vxdmpadm start restore command is executed while the restore daemon is running.
Action
Stop the restore daemon. Restart the restore daemon with the required set of parameters.

Error in cluster processing

Description
This may be due to an operation inconsistent with the current state of the cluster (such as an attempt to import or deport a shared disk group from the slave). It may also be caused by an unexpected sequence of commands from vxclust.
Action
Make sure that the operation can be performed in the current environment.

Cannot find disk on slave node

Description
A slave node cannot find a shared disk. This is accompanied by the syslog message:
vxvm:vxconfigd cannot find disk disk
Action
Make sure that the same set of shared disks is online on both nodes.
Examine the disks on both the master and the slave with the command vxdisk list and make sure that the same set of disks with the shared flag is visible on both nodes. If not, check connections to the disks.

Disk in use by another cluster

Description
An attempt was made to import a disk group whose disks are stamped with the ID of another cluster.
Action
If the disk group is not imported by another cluster, retry the import using the -C (clear import) flag.

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.

Unable to add portal for cluster

Description
vxconfigd was not able to create a portal for communication with the vxconfigd on the other node. This may happen in a degraded system that is experiencing shortages of system resources (such as memory or file descriptors).
Action
If the system does not appear to be degraded, stop and restart vxconfigd and try again.

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 again later (when the merge operation has completed).

Cannot assign minor #

Description
The slave attempted to join, but an existing volume on the slave has the same minor number as a shared volume on the master.
This message should be accompanied by the following console message:
WARNING vxvm:vxconfigd minor number ### disk group group in use
Action
Before retrying the join, use vxdg reminor diskgroup ### (see the vxdg(1M) manual page) to choose a new minor number range either for the disk group on the master or for the conflicting disk group on the slave. If there are open volumes in the disk group, the reminor operation will not take effect until the disk group is deported and updated either explicitly or through system restart.

Master sent no data

Description
During the slave join protocol, a message without data was received. This message is only likely to be seen in the case of a programming error.
Action
Contact Customer Support for more information.

Join in progress

Description
An attempt was made to import or deport a shared disk group during a cluster reconfiguration.
Action
Retry later.

Join not allowed now

Description
A slave attempted to join the cluster when the master was not ready. The slave will retry automatically. If the retry succeeds, the following message should appear:
vxclust: slave join complete
Action
No action is necessary if the join eventually completes. Otherwise, investigate the cluster monitor on the master.

Disk reserved by other host

Description
An attempt to online a disk whose controller has been reserved by another host will fail with this error.
Action
No action is necessary. The cluster manager will free the disk and the Volume Manager will online it when the node joins the cluster.

Group exists

vxvm:vxconfigd: group group exists

Description
The slave tried to join the cluster, but there is already a shared disk group in 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.

Plex detached from volume

		WARNING: vxvm:vxio: Plex plex detached from volume volume
		NOTICE: vol_kmsg_send_wait_callback: got error 22
		NOTICE: commit: NOTE: Reason found for abort: code=6

Description
These messages may appear during a plex detach operation on a slave.
Action
These messages provide information and require no user action.

Read error on Plex of shared volume; Plex detached from volume

		WARNING: vxvm:vxio: read error on Plex plex of shared volume
		volume offset 10 length 1
		WARNING: vxvm:vxio: Plex plex detached from volume volume
		NOTICE: commit: NOTE: Reason found for abort: code=2
		NOTICE: ktcvm_check: sent to slave node: node=1 mid=196

Description
These messages may appear during a plex detach operation on the master.
Action
These messages provide information and require no user action.

Return from cluster_establish is Configuration daemon error 242

Description
This error may occur when a node fails to join the cluster or when a cluster join takes a long time. If the join fails, the node should retry the join automatically.
Action
No action is necessary if the join is slow or a retry eventually succeeds.

Missing vxconfigd

Description
The vxconfigd daemon is not running.
Action
Restart the vxconfigd daemon.

vxconfigd not ready

node #: vxconfigd is not communicating properly

Description
The vxconfigd daemon is not responding properly.
Action
Stop and restart the vxconfigd daemon.

vxiod count must be above # to join cluster

ERROR: vxiod count must be above 5 to join cluster

Description
The number of Volume Manager kernel daemons (vxiod) is less than the minimum number needed to join the cluster.
Action
Increase the number of daemons using vxiod.

Insufficient DRL log size: logging is disabled.

Description
A volume with an insufficient DRL log size was started. The volume gets started successfully, but DRL logging is disabled and a full recovery is performed.
Action
Create a new DRL of sufficient size.

This node was running different CM. Please Reboot.

Description
VxVM supports clustering under the control of various cluster managers. However, once a node joins the cluster under a particular cluster manager, it cannot be restarted under a different cluster manager until it is rebooted.
Action
Reboot the host machine if the cluster must be started under a different cluster manager.

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.

Node activation conflict

Description
The disk group could not be activated because it is activated in a conflicting mode on another node in the cluster.
Action
Retry later, or deactivate the disk group on conflicting nodes.

Incorrect protocol version num in volboot file

Description
This message may appear when a node attempts to join the cluster if VxVM software was incorrectly upgraded or the volboot file is corrupted.
Action
Verify the supported cluster protocol versions using vxdctl protocolversion, and reinstall the Volume Manager if necessary.

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 later.

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.

Upgrade operation failed: Version out of range for at least one node

Description
Before trying to upgrade a cluster by running vxdctl upgrade, all the nodes should be able to support the new protocol version. If at least one of them doesn't support the the new protocol version, an upgrade can fail.
Action
Make sure that the VxVM package that supports the new protocol version is installed on all nodes and retry the upgrade.

Upgrade operation failed: Error in cluster processing

Description
The cluster protocol upgrade must be done on the master and cannot be done from a slave node.
Action
Retry the vxdctl upgrade command on the master node.

CVM protocol version out of range

Description
When a node joins the cluster, it tries to join at a protocol version that is stored in its volboot file. If the cluster is running at a different protocol version, the master rejects the join and sends the current protocol version to the slave. The slave re-tries with the current version (if that version is supported on the joining node), or the join fails.
Action
Make sure that the joining node has a VxVM release installed that supports the current protocol version of the cluster.

ERROR: upgrade operation failed: Already at highest version

Description
The message conveys that the upgrade operation has failed because the cluster is already running at the highest protocol version that the master supports.
Action
No further action is necessary as the master is already running at the highest protocol version it can support.

Not in cluster

Description
Checking for the current protocol version (vxdctl protocolversion) makes sense only if the node is in the cluster.
Action
Bring the node in the cluster and retry.

Incorrect protocol version (15) in volboot file.

Description
The volboot file contains an incorrect protocol version. It has either been corrupted or edited manually. The volboot file should always have a supported protocol version in it before trying to bring the node into the cluster.
Action
Run vxdctl init. This writes a valid protocol version in the volboot file. Restart vxconfigd and retry the join.

Upgrade operation failed: Retry rolling upgrade

Description
No transactions should be in progress when an upgrade is tried.
Action
Retry the upgrade later.

Cluster Error Messages

Technical documentation

» Table of Contents

» Index