After an interrupted yum update, Pacemaker fails to start in my RHEL High Availability environment

Solution Verified - Updated -

Issue

While preforming a yum update, a node was fenced or yum was otherwise prematurely interrupted. Subsequently pacemaker fails to start with systemd errors such as:

Feb  5 20:34:28 node1 systemd: pacemaker.service: main process exited, code=exited, status=127/n/a
Feb  5 20:34:28 node1 systemd: Unit pacemaker.service entered failed state.
Feb  5 20:34:28 node1 systemd: pacemaker.service failed.
Feb  5 20:34:28 node1 systemd: pacemaker.service holdoff time over, scheduling restart.
Feb  5 20:34:28 node1 systemd: start request repeated too quickly for pacemaker.service
Feb  5 20:34:28 node1 systemd: Failed to start Pacemaker High Availability Cluster Manager.
Feb  5 20:34:28 node1 systemd: Unit pacemaker.service entered failed state.
Feb  5 20:34:28 node1 systemd: pacemaker.service failed.

Environment

  • Red Hat Enterprise Linux 6 w/ High Availability
  • Red Hat Enterprise Linux 7 w/ High Availability
  • Pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.