Setting up cluster, corosync.service failed, configuration error: nodelist

brucexx

Renowned Member
Mar 19, 2015
216
7
83
I just tried to get a new cluster to work. To my surprise I got this:

Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.

Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.
command 'systemctl restart corosync' failed: exit code 1

..and this:

root@pve01:~# systemctl status corosync.service -l
...
Mar 14 13:33:27 pve01 corosync[1875]: [QUORUM] Quorum provider: corosync_votequorum failed to initialize.
Mar 14 13:33:27 pve01 corosync[1875]: [SERV ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'
...
root@pve01:~#

...and this:
root@pve01:~# pvecm status
Cannot initialize CMAP service

I am just posting it for others to spare them some time. I had a clean installation of the Proxmox 4.1 (or so I thought) but the ip address of the node was changed right after the installation before joining a cluster. If you decide to change your ip (again before joining a cluster) you need to change it also in the host file as it is being used by the corosync.conf file and the ips don't mach.

Thank you
 
I wish I had found this post 3 hours ago!! Thank you for sharing, it works like a charm now.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!