Cannot initialize CMAP service on fresh install of pve-manager/4.1

[Mn1sh]

Hi,
I see the following error before trying to setup 3node promoxVE cluster


root@srv1:~# pvecm status
Cannot initialize CMAP service
root@srv1:~#

root@srv1:~# pveversion
pve-manager/4.1-1/2f9650d4 (running kernel: 4.2.6-1-pve)
root@srv1:~#

root@srv1:~# corosync-cmapctl -g totem.interface.0.mcastaddr
Failed to initialize the cmap API. Error CS_ERR_LIBRARY
root@srv1:~#



Please advise.

 

[Mn1sh]

Ok i got it working somewhat , please check below/advice what could be wrong?
#########################################################################

root@srv1:~# pvecm status
Quorum information
------------------
Date: Wed Mar 9 07:45:58 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 4
Quorate: Yes

Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.0.1 (local) ### ip for representation only here
root@srv1:~# corosync-cmapctl -g totem.interface.0.mcastaddr
totem.interface.0.mcastaddr (str) = 239.192.153.205


root@srv1:~# omping srv1 srv2 srv3
srv2 : waiting for response msg
srv3 : waiting for response msg
srv2 : waiting for response msg
srv3 : waiting for response msg
srv2 : waiting for response msg
srv3 : waiting for response msg
^C
srv2 : response message never received
srv3 : response message never received
^Croot@srv1:~#




However there is no response from srv2 an srv3 using omping.

Tried following , eternally stuck
###################################################
root@srv2:~# pvecm add srv1
root@srv1's password:
copy corosync auth key
stopping pve-cluster service
backup old database
Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.
waiting for quorum...corosync-cmapctl -g totem.interface.0.mcastaddr



On other node ( trying to add to cluster )
#######################################################
Note: In this case, i went to the proxmoxVE GUI for srv3 and started corosync from services ( which was showing dead earlier )
root@srv3:~# pvecm add srv1
The authenticity of host '[srv1]:30962 ([192.168.0.1]:30962)' can't be established.
ECDSA key fingerprint is aa:2e:83:b1:f9:01:30:48:66:28:1c:ba:38:1c:ac:f1.
Are you sure you want to continue connecting (yes/no)? yes
root@srv1's password:
unable to copy ssh ID
root@srv3:~#
root@srv3:~# pvecm status
Cannot initialize CMAP service
root@srv3:~# /etc/init.d/cma^C
root@srv3:~# /etc/init.d/cman status
-bash: /etc/init.d/cman: No such file or directory
root@srv3:~#
root@srv3:~# corosync-cmapctl -g totem.interface.0.mcastaddr
Failed to initialize the cmap API. Error CS_ERR_LIBRARY
root@srv3:~#


root@srv3:~# pveversion -v
proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)
pve-kernel-4.2.6-1-pve: 4.2.6-26
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-41
pve-firmware: 1.1-7
libpve-common-perl: 4.0-41
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-17
pve-container: 1.0-32
pve-firewall: 2.0-14
pve-ha-manager: 1.0-14
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie
root@srv3:~#

 

[athompso]

Would you please share what you did to get past the CMAP initialization problem?

 

[Mn1sh]

i could get past the error in main node, when I created a cluster name using:

pvecm create ClusterName

 

[fabian]

The error message "Cannot initialize CMAP service" is normal on standalone nodes (i.e., if you haven't created or joined a cluster on that node).

 

[laowolf]

make sure two things.
first, make sure all of your node's /etc/hosts file has been properly edited so you can ping any node from any node with hostname.
second, make sure your cluster network support multicast, and when you run omping from all of your node simultaneously, you can get proper response.