CentOS 7 Startup issue

[petems]

The failures in PCCI are actually bubbling up a real error:

A few things you could check:

Make sure that Corosync and Pacemaker start at boot (or at least start them both manually) on both nodes:
$ sudo systemctl enable corosync
$ sudo systemctl enable pacemaker

There is a know bug which appears at boot on RHEL 7 or CentOS 7, I reported a workaround in Redhat bugzilla bug #1030583 but it’s no longer public.

The workardound is to let Corosync wait for 10s at boot, so it doesn’t start when the interfaces aren’t completely available (ugly workaround, I know :))

Change /usr/lib/systemd/system/corosync.service to include the ExecStartPre:
…
[Service]
ExecStartPre=/usr/bin/sleep 10
ExecStart=/usr/share/corosync/corosync start
…
Then, reload systemd:
$ sudo systemctl daemon-reload

You can also look in /var/log/pacemaker.log or look for something related in /var/log/messages.

In case these steps won’t help, I will check to redo the tutorial myself and see if I missed or forgot to write something.

Keep me posted :)

http://jensd.be/156/linux/building-a-high-available-failover-cluster-with-pacemaker-corosync-pcs

[petems]

Error from CentOS 7 box:

Dec 12 23:20:35 localhost corosync[5250]: [SERV  ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'

[fatmcgav]

@petems I'm seeing this issue outside of the boot process aswell... So when the machine is running, trying to start corosync service throws the above error...

So I'm not sure it's specific to the boot process...

Thoughts?

[jyaworski]

Could we get more information on this?

[roidelapluie]

I can repoduce that, but I need more info, like the parameters you pass to the corosync class

[roidelapluie]

ping @fatmcgav
@petems

[roidelapluie]

Probably fixed upstream