VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Cluster Error Messages
76 VERITAS Volume Manager Troubleshooting Guide
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 clusterjoin is taking too long. If thejoin
fails, the node retries the join automatically.
◆ Action: No action is necessary if the join is slow or a retry eventually succeeds.
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: Rebootthe host machine ifthe cluster must bestarted under a different cluster
manager.
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.
Upgrade operation failed: Error in cluster processing
◆ Description: The cluster protocol upgrade must be done on the master. It cannot be
done from a slave node.
◆ Action: Retry the vxdctl upgrade command on the master node.
Upgrade operation failed: Retry rolling upgrade
◆ Description: No transactions should be in progress when an upgrade is tried.
◆ Action: Retry the upgrade at a later time.