Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Services Planning and Administration Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Clearing the `Start_failed` Resource State

The `Start_failed` resource state indicates that a `Start` or `Prenet_start` method failed or timed out on a resource, but its resource group came online anyway. The resource group comes online even though the resource has been placed in a faulted state and might not be providing service. This state can occur if the resource's `Failover_mode` property is set to `None` or to another value that prevents the failover of the resource group.

Unlike the `Stop_failed` resource state, the `Start_failed` resource state does not prevent you or the Oracle Solaris Cluster software from performing actions on the resource group. You need only to execute a command that restarts the resource.

Use any one of the following procedures to clear this condition.

## How to Clear a `Start_failed` Resource State by Switching Over a Resource Group

Note - Perform this procedure from any cluster node.

Before You Begin

Ensure that the following conditions are met:

- You have the following information:

  - The name of the resource group that you are switching over

  - The name of the node on which to switch over the resource group

- The nodes where the resource group is to be brought online or to remain online are in the cluster .

1. On a cluster member, assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Switch the resource group to the new node.

       # clresourcegroup switch [-n nodelist] resource-group

   `-n` nodelist

     Specifies a comma-separated, ordered list of nodes that can master this resource group. This resource group is switched offline on all of the other nodes.

     This list is optional. If you omit this list, the resource group is switched on all nodes in the resource group's node list.

   resource-group

     Specifies the name of the resource group to switch.

   Note - If any resource group that you are switching declares a strong affinity for other resource groups, the attempt to switch might fail or be delegated. For more information, see Distributing Online Resource Groups Among Cluster Nodes.

3. Verify that the resource group has been switched to the new node and that the `Start_failed` resource state is cleared.

       # clresourcegroup status

   The output from this command indicates the state of the resource and the resource group that has been switched over.

Example 2-25 Clearing a `Start_failed` Resource State by Switching Over a Resource Group

This example shows how to clear a `Start_failed` resource state that has occurred on the `rscon` resource in the `resource-group-1` resource group. The command clears this condition by switching the resource group to the cluster node `phys-schost-2`.

1. To verify that the resource is in the `Start_failed` resource state on `phys-schost-1`, the following command is run:

       # clresource status

       === Cluster Resources ===

       Resource Name        Node Name           Status          Message
       --------------       ----------          -------         -------
        rscon               phys-schost-1       Faulted         Faulted
                            phys-schost-2       Offline         Offline

        hastor              phys-schost-1       Online          Online
                            phys-schost-2       Offline         Offline

2. To perform the switch, the following command is run:

       # clresourcegroup switch -n phys-schost-2 resource-group-1

3. To verify that the resource group is switched to be online on `phys-schost-2` and that the `Start_failed` resource status is cleared, the following command is run:

       # clresource status

       === Cluster Resources ===

       Resource Name        Node Name           Status          Message
       --------------       ----------          -------         -------
        rscon               phys-schost-1       Offline         Offline
                            phys-schost-2       Online          Online

        hastor              phys-schost-1       Online          Online
                            phys-schost-2       Offline         Offline

See Also

The `clresourcegroup`(1CL) man page.

## How to Clear a `Start_failed` Resource State by Restarting a Resource Group

Note - Perform this procedure from any cluster node.

Before You Begin

Ensure that the following conditions are met:

- You have the following information:

  - The name of the resource group that you are restarting

  - The name of the node on which to restart the resource group

- The nodes where the resource group is to be brought online or to remain online are cluster nodes.

1. On a cluster member, assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Restart the resource group.

       # clresourcegroup restart -n node resource-group

   `-n` node

     Specifies the name of the node on which the resource group is to be restarted. This resource group is switched offline on all of the other nodes.

   resource-group

     Specifies the name of the resource group to restart.

3. Verify that the resource group has been restarted on the new node and that the `Start_failed` resource state is cleared.

       # clresourcegroup status

   The output from this command indicates the state of the resource and the resource group that has been restarted.

Example 2-26 Clearing a `Start_failed` Resource State by Restarting a Resource Group

This example shows how to clear a `Start_failed` resource state that has occurred on the `rscon` resource in the `resource-group-1` resource group. The command clears this condition by restarting the resource group on the cluster node `phys-schost-1`.

1. Verify that the resource is in the `Start_failed` resource state on `phys-schost-1`.

       # clresource status

       === Cluster Resources ===

       Resource Name        Node Name           Status          Message
       --------------       ----------          -------         -------
        rscon               phys-schost-1       Faulted         Faulted
                            phys-schost-2       Offline          Offline

        hastor              phys-schost-1       Online          Online
                            phys-schost-2       Offline         Offline

2. Restart the resource.

       # clresourcegroup restart -n phys-schost-1 –g resource-group-1

3. Verify that the resource group is restarted on `phys-schost-1` and that the `Start_failed` resource status is cleared.

       # clresource status

       === Cluster Resources ===

       Resource Name        Node Name           Status          Message
       --------------       ----------          -------         -------
        rscon               phys-schost-1       Offline         Offline
        rscon               phys-schost-2       Online          Online

        hastor              phys-schost-1       Online          Online
        hastor              phys-schost-2       Offline         Offline

See Also

The `clresourcegroup`(1CL) man page.

## How to Clear a `Start_failed` Resource State by Disabling and Enabling a Resource

Note - Perform this procedure from any cluster node.

Before You Begin

Ensure that you have the name of the resource that you are disabling and enabling.

1. On a cluster member, assume the `root` role that provides `solaris.cluster.modify` RBAC authorization.
2. Disable and then enable the resource.

       # clresource disable resource
       # clresource enable resource

   resource

     Specifies the name of the resource.

3. Verify that the resource has been disabled and enabled and that the `Start_failed` resource state is cleared.

       # clresource status

   The output from this command indicates the state of the resource that has been disabled and re-enabled.

Example 2-27 Clearing a `Start_failed` Resource State by Disabling and Enabling a Resource

This example shows how to clear a `Start_failed` resource state that has occurred on the `rscon` resource by disabling and enabling the resource.

1. Verify that the resource is in the `Start_failed` resource state.

       # clresource status

       === Cluster Resources ===

       Resource Name             Node Name       Status        Message
       --------------            ----------      -------        -------
        rscon               phys-schost-1       Faulted         Faulted
                            phys-schost-2       Offline          Offline

        hastor              phys-schost-1       Online          Online
                            phys-schost-2       Offline         Offline

2. Disable and re-enable the resource.

       # clresource disable rscon
       # clresource enable rscon

3. Verify that the resource is re-enabled and that the `Start_failed` resource status is cleared.

       # clresource status

       === Cluster Resources ===

       Resource Name             Node Name       Status        Message
       --------------            ----------      -------        -------
        rscon               phys-schost-1       Online         Online
                            phys-schost-2       Offline        Offline

        hastor              phys-schost-1       Online          Online
                            phys-schost-2       Offline         Offline

See Also

The `clresource`(1CL) man page.

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |