crm_resource --restart fails to restart a clone instance with a "resource not running on node" error in a Pacemaker cluster

Solution Verified - Updated -


  • The crm_resource --restart --resource <rsc> --node <node> command successfully restarts an instance of a clone resource on one node. But for the other nodes, the command fails with the error shown below.
# crm_resource --restart --resource stateful --node node2
stateful is not running on node2 and so cannot be restarted


  • Red Hat Enterprise Linux 7, 8, 9 (with the High Availability 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