When the Failover_mode resource property is set to NONE or SOFT, a failure of the resource's STOP method causes the following effects:
The individual resource goes into the STOP_FAILED state.
The resource group that contains the resource goes into the ERROR_STOP_FAILED state.
In this situation, you cannot perform the following operations:
Bringing online the resource group on any node
Adding resources to the resource group
Removing resources from the resource group
Changing the properties of the resource group
Changing the properties of resources in the resource group
Perform this procedure from any cluster node.
Before You Begin
Ensure that you have the following information.
The name of the node where the resource is STOP_FAILED
The name of the resource and resource group that are in STOP_FAILED state
# clresource status
This step might require that you kill processes or run commands that are specific to resource types or other commands.
# 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.
# 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.
# clresourcegroup offline resource-group
Specifies the name of the resource group to switch offline.