Failed to start 'corosync.service' in pacemaker cluster
Issue
-
Failed to start cluster services, while it is configured to start during boot.
Nov 23 20:28:05 node1 corosync[600]: [MAIN ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service. Nov 23 20:28:05 node1 corosync[600]: [MAIN ] Corosync built-in features: dbus systemd xmlconf snmp pie relro bindnow Nov 23 20:28:05 node1 corosync[600]: [MAIN ] parse error in config: No interfaces defined Nov 23 20:28:05 node1 corosync[600]: [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1220.
Mar 11 08:49:21 node1 systemd[1]: Starting Corosync Cluster Engine... Mar 11 08:49:21 node1 corosync[2336]: [MAIN ] Corosync Cluster Engine ('2.3.4'): started and ready to provide service. Mar 11 08:49:21 node1 corosync[2336]: [MAIN ] Corosync built-in features: dbus systemd xmlconf snmp pie relro bindnow Mar 11 08:49:51 node1 corosync[2336]: [MAIN ] parse error in config: No interfaces defined Mar 11 08:49:51 node1 corosync[2336]: [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1278. Mar 11 08:49:51 node1 corosync[2319]: Starting Corosync Cluster Engine (corosync): [FAILED] Mar 11 08:49:51 node1 systemd[1]: corosync.service: control process exited, code=exited status=1 Mar 11 08:49:51 node1 systemd[1]: Failed to start Corosync Cluster Engine. Mar 11 08:49:51 node1 systemd[1]: Unit corosync.service entered failed state. Mar 11 08:49:51 node1 systemd[1]: corosync.service failed.
Environment
- Red Hat Enterprise Linux 7 (High Availability add-on)
- Corosync
- Red Hat OpenStack Platform 6 (Juno) (using above)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.