Perform this procedure from any cluster node.
Ensure that you have the following information.
The name of the node or zone where the resource is STOP_FAILED
The name of the resource and resource group that are in STOP_FAILED state
On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
Identify which resources have gone into the STOP_FAILED state and on which nodes or zones.
# clresource status
Manually stop the resources and their monitors on the nodes or zones on which they are in STOP_FAILED state.
This step might require that you kill processes or run commands that are specific to resource types or other commands.
Clear the STOP_FAILED error flag on the resources.
# clresource clear -f STOP_FAILED -n nodelist resource
Specifies the flag name.
Specifies a comma-separated list of the names of the nodes where the resource is in the STOP_FAILED state. The list may contain one node name or more than one node name.
Specifies the name of the resource.
Check the resource group state on the nodes or zones where you cleared the STOP_FAILED flag in Step 4.
# clresourcegroup status
The resource group state should now be OFFLINE or ONLINE.
The resource group remains in the ERROR_STOP_FAILED state in the following combination of circumstances:
The resource group was being switched offline when the STOP method failure occurred.
The resource that failed to stop had a dependency on other resources in the resource group.
If the resource group remains in the ERROR_STOP_FAILED state, correct the error as follows.
The following man pages: