How to Recover From a Failure of the vucmmd Daemon or a Related Component

Perform this task to correct the problems that are described in the following sections:

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

• Failure of the vucmmd Daemon to Start

This procedure provides the long forms of the Sun Cluster maintenance commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

1. To determine the cause of the problem, examine the log files for multiple-owner volume-manager framework reconfigurations and the system messages file.

   For the location of the log files for multiple-owner volume-manager framework reconfigurations, see Sources of Diagnostic Information.

   When you examine these files, start at the most recent message and work backward until you identify the cause of the problem.

   For more information about error messages that might indicate the cause of reconfiguration errors, see Sun Cluster Error Messages Guide for Solaris OS.

2. Correct the problem that caused the component to return an error to the multiple-owner volume-manager framework .

   For example:

   • If the license for VxVM is missing or has expired, ensure that VxVM is correctly installed and licensed.

     1. Verify that you have correctly installed your volume manager packages.

     2. If you are using VxVM, check that you have installed the software and check that the license for the VxVM cluster feature is valid.

     ---

     Note –

     A zone cluster does not support VxVM.

     ---

   • If a reconfiguration step has timed out, increase the value of the extension property that specifies the timeout for the step.

     For more information, see Node Panic Caused by a Timeout.

3. If the solution to the problem requires a reboot, reboot the node where the problem occurred.

   The solution to only certain problems requires a reboot. For example, increasing the amount of shared memory requires a reboot. However, increasing the value of a step timeout does not require a reboot.

   For more information about how to reboot a node, see Shutting Down and Booting a Single Node in a Cluster in Sun Cluster System Administration Guide for Solaris OS.

4. On the node where the problem occurred, take offline and bring online the multiple-owner volume-manager framework resource group.

   This step refreshes the resource group with the configuration changes you made.

   1. Become superuser or assume a role that provides solaris.cluster.admin RBAC authorization.

   2. Type the command to take offline the multiple-owner volume-manager framework resource group and its resources.

      # clresourcegroup offline -n node vucmm-fmwk-rg

      -n node

      Specifies the node name or node identifier (ID) of the node where the problem occurred.

      vucmm-fmwk-rg

      Specifies the name of the resource group that is to be taken offline.

   3. Type the command to bring online and in a managed state the multiple-owner volume-manager framework resource group and its resources.

      # clresourcegroup online -emM -n node vucmm-fmwk-rg