Result of stop operation for a resource: Timed Out

Solution Verified - Updated -

Issue

  • A cluster node gets fenced after a stop operation fails with a timeout
  • Unexpected reboot in a cluster node due to operation failure.
lrmd: warning: <resource_name>_stop_0 process (PID 12885) timed out
lrmd: warning: <resource_name>_stop_0:12885 - timed out after 600000ms
.
.
pengine: warning: Cluster node <node-name> will be fenced: <resource-name> failed there
pengine: warning: Scheduling Node <node-name> for STONITH
pengine:  notice: Stop of failed resource <resource-name> is implicit after <node-name> is fenced
pengine:  notice:  * Fence (reboot) <node-name> <resource-name> failed there'

Environment

  • Red Hat Enterprise Linux (RHEL) 7, 8 or 9 with the High Availability Or Resilient Storage Add On

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content