Proxmox VE 4.0 - Re-install cluster node Cannot initialize CMAP service

pjkenned

Renowned Member
Dec 16, 2013
26
1
68
I recently had a failed boot SATA DOM and tried re-installing a cluster node. Luckily, there was nothing too important on the node while it was running.

I used these steps exactly: http://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster#Re-installing_a_cluster_node

The files backed up were installed where they are supposed to go. I started the services in the order on the Wiki page and am seeing this:
Code:
root@node05:~# pvecm status
Cannot initialize CMAP service

I am going to try another re-install. I did double-check that it can ping to the other five nodes and it can be pinged from the other five nodes.

I tried doing:
Code:
systemctl status corosync.service

and got:

Code:
Dec 04 16:38:10 node05 corosync[3646]: [MAIN  ] Corosync Cluster Engine ('2.3.5'): started and ready to provide service.
Dec 04 16:38:10 node05 corosync[3646]: [MAIN  ] Corosync built-in features: augeas systemd pie relro bindnow
Dec 04 16:38:10 node05 corosync[3646]: [MAIN  ] Could not open /etc/corosync/authkey: No such file or directory
Dec 04 16:38:10 node05 corosync[3646]: [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1272.
Dec 04 16:38:10 node05 corosync[3641]: Starting Corosync Cluster Engine (corosync): [FAILED]
Dec 04 16:38:10 node05 systemd[1]: corosync.service: control process exited, code=exited status=1
Dec 04 16:38:10 node05: Failed to start Corosync Cluster Engine.
Dec 04 16:38:10 node05 systemd[1]: Unit corosync.service entered failed state.

I did check the the correct /etc/corosync/corosync.conf file is present.

Happy to make a bug report if there is a category this falls in. I do not want to make a bug if it is really a step was missing for re-installation.
 
Seems you also need to copy /etc/corosync/authkey from one of the other cluster nodes.

Hey, I'm a bit new to proxmox and having a blast, but im getting the same problem, but a different log

Code:
Aug 16 11:46:41 pve corosync[1652]: info    [WD    ] no resources configured.
Aug 16 11:46:41 pve corosync[1652]: notice  [SERV  ] Service engine loaded: corosync watchdog service [7]
Aug 16 11:46:41 pve corosync[1652]: notice  [QUORUM] Using quorum provider corosync_votequorum
Aug 16 11:46:41 pve corosync[1652]: crit    [QUORUM] Quorum provider: corosync_votequorum failed to initialize.
Aug 16 11:46:41 pve corosync[1652]: error   [SERV  ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'
Aug 16 11:46:41 pve corosync[1652]: error   [MAIN  ] Corosync Cluster Engine exiting with status 20 at service.c:356.
Aug 16 11:46:41 pve systemd[1]: corosync.service: Main process exited, code=exited, status=20/n/a
Aug 16 11:46:41 pve systemd[1]: Failed to start Corosync Cluster Engine.
Aug 16 11:46:41 pve systemd[1]: corosync.service: Unit entered failed state.
Aug 16 11:46:41 pve systemd[1]: corosync.service: Failed with result 'exit-code'.

I'm using Proxmox 5.2-6 and created the cluster with the gui
 
Last edited:

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!