Node Panic During Initialization of the Multiple-Owner Volume-Manager Framework

If a fatal problem occurs during the initialization of the multiple-owner volume-manager framework, the node panics with an error messages similar to the following error message:

When the node is a global-cluster voting node of the global cluster, the node panic brings down the entire machine.

panic[cpu0]/thread=40037e60: Failfast: Aborting because "vucmmd" died 30 seconds ago

Description:

A component that the multiple-owner volume-manager framework controls returned an error to the multiple-owner volume-manager framework during a reconfiguration.

Cause:

The most common causes of this problem is that the license for Veritas Volume Manager (VxVM) is missing or has expired.

A node might also panic during the initialization of the multiple-owner volume-manager framework because a reconfiguration step has timed out. For more information, see Node Panic Caused by a Timeout.

Solution:

For instructions to correct the problem, see How to Recover From a Failure of the vucmmd Daemon or a Related Component.