"pengine: error: native_create_actions: Resource <name> (<class>:<provider>:<type>) is active on 2 nodes attempting recovery" seen when a node rejoins a RHEL 6 or 7 High Availability cluster

Solution Verified - Updated -

Issue

  • My resources restarted unexpectedly after a node rejoined, even though I have location constraints and resource-stickiness set to prefer the node it was already running on, and I saw "is active on 2 nodes" errors
Dec 10 07:33:56 [11743] node1    pengine:    error: native_create_actions:    Resource myScript (lsb::ha_script) is active on 2 nodes attempting recovery
Dec 10 07:33:56 [11743] node1    pengine:  warning: native_create_actions:    See http://clusterlabs.org/wiki/FAQ#Resource_is_Too_Active for more information.
Dec 10 07:33:56 [11743] node1    pengine:   notice: LogActions:       Restart myScript    (Started node1)
  • A node rejoined after fencing and the resource moved to it, even though its configured to stick where it is

Environment

  • Red Hat Enterprise Linux (RHEL) 6, 7, 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