[SOLVED] Proxmox ve 5 Cluster installation

juniper

Renowned Member
Oct 21, 2013
84
0
71
Proxmox VE 5 installed on Debian Stretch (diskless iscsi boot)

Debian Stretch installation is fine

Proxmox VE 5 installation is fine on 3 node but when i try to create a cluster i have this error:

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


root@********:/etc/corosync# systemctl restart pve-cluster
root@********:/etc/corosync# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-07-05 13:19:43 CEST; 5s ago
Process: 6247 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 6243 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Main PID: 6245 (pmxcfs)
Tasks: 5 (limit: 6144)
CGroup: /system.slice/pve-cluster.service
└─6245 /usr/bin/pmxcfs

Jul 05 13:19:42 timlabsrv1 pmxcfs[6245]: [confdb] crit: can't initialize service
Jul 05 13:19:42 timlabsrv1 pmxcfs[6245]: [dcdb] crit: cpg_initialize failed: 2
Jul 05 13:19:42 timlabsrv1 pmxcfs[6245]: [dcdb] crit: can't initialize service
Jul 05 13:19:42 timlabsrv1 pmxcfs[6245]: [status] crit: cpg_initialize failed: 2
Jul 05 13:19:42 timlabsrv1 pmxcfs[6245]: [status] crit: can't initialize service
Jul 05 13:19:43 timlabsrv1 systemd[1]: Started The Proxmox VE cluster filesystem.
Jul 05 13:19:48 timlabsrv1 pmxcfs[6245]: [quorum] crit: quorum_initialize failed: 2
Jul 05 13:19:48 timlabsrv1 pmxcfs[6245]: [confdb] crit: cmap_initialize failed: 2
Jul 05 13:19:48 timlabsrv1 pmxcfs[6245]: [dcdb] crit: cpg_initialize failed: 2
Jul 05 13:19:48 timlabsrv1 pmxcfs[6245]: [status] crit: cpg_initialize failed: 2


 
root@******:/var/log# systemctl status corosync.service
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2017-07-05 13:19:43 CEST; 10min ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Process: 6258 ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS (code=exited, status=20)
Main PID: 6258 (code=exited, status=20)

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