A cluster node was fenced after a `stop` action for a stonith device timed out

Solution In Progress - Updated -

Issue

  • A cluster node was fenced after a stop action for a stonith device timed out

    Sep 28 22:53:51 node42 pacemaker-controld[1628]: error: Node node41 did not send stop result (via controller) within 80000ms (action timeout plus cluster-delay)
    Sep 28 22:53:51 node42 pacemaker-controld[1628]: error: [Action    2]: In-flight resource op vmfence_stop_0             on node41 (priority: 0, waiting: (null))
    Sep 28 22:53:51 node42 pacemaker-controld[1628]: notice: Transition 26 aborted: Action lost
    Sep 28 22:53:51 node42 pacemaker-controld[1628]: warning: rsc_op 2: vmfence_stop_0 on node41 timed out
    [.....]
    Sep 28 22:53:52 node42 pacemaker-schedulerd[1627]: warning: Cluster node node41 will be fenced: vmfence failed there
    Sep 28 22:53:52 node42 pacemaker-schedulerd[1627]: warning: Scheduling Node node41 for STONITH
    Sep 28 22:53:52 node42 pacemaker-schedulerd[1627]: notice: Stop of failed resource vmfence is implicit because node41 is fenced
    [.....]
    Sep 28 22:53:52 node42 pacemaker-controld[1628]: notice: Requesting fencing (reboot) of node node41
    

Environment

  • Red Hat Enterprise Linux Server 8 (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