Pacemaker cluster fails to initialize at boot time in RHEL 7 High Availability Cluster with Pacemaker

Solution In Progress - Updated -

Issue

  • A pacemaker cluster fails to initialize at boot time with the corosync errors below:
Jul 25 12:54:44 node1 corosync[2195]:  [MAIN  ] parse error in config: Not all bind address belong to the same IP family
Jul 25 12:54:44 node1 corosync[2195]:  [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1278.
Jul 25 12:54:44 node1 corosync[2103]: Starting Corosync Cluster Engine (corosync): [FAILED]
Jul 25 12:54:44 node1 systemd[1]: corosync.service: control process exited, code=exited status=1
Jul 25 12:54:44 node1 systemd[1]: Failed to start Corosync Cluster Engine.
Jul 25 12:54:44 node1 systemd[1]: Dependency failed for Pacemaker High Availability Cluster Manager.
Jul 25 12:54:44 node1 systemd[1]: Job pacemaker.service/start failed with result 'dependency'.
Jul 25 12:54:44 node1 systemd[1]: Unit corosync.service entered failed state.
Jul 25 12:54:44 node1 systemd[1]: corosync.service failed.
  • If we then attempt to start the cluster again, pacemaker initialization succeeds.

Environment

  • Red Hat Enterprise Linux 7 with the High Availability Add-On
  • corosync
  • 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