All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Cluster issue
Hi,
We are created cluster and trying to add server to it. But is leave error and not working.
systemctl status corosync.service
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-06-26 20:23:15 EDT; 18s ago
Process: 2573 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE)
Jun 26 20:22:15 ns507839 corosync[2580]: [QB ] server name: cmap
Jun 26 20:22:15 ns507839 corosync[2580]: [SERV ] Service engine loaded: corosync configuration service [1]
Jun 26 20:22:15 ns507839 corosync[2580]: [QB ] server name: cfg
Jun 26 20:22:15 ns507839 corosync[2580]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
tail -f /var/log/daemon.log
Jun 29 10:21:06 ns507839 pmxcfs[16543]: [dcdb] crit: cpg_initialize failed: 2
Jun 29 10:21:06 ns507839 pmxcfs[16543]: [status] crit: cpg_initialize failed: 2
Jun 29 10:21:12 ns507839 pmxcfs[16543]: [quorum] crit: quorum_initialize failed: 2
Jun 29 10:21:12 ns507839 pmxcfs[16543]: [confdb] crit: cmap_initialize failed: 2
Jun 29 10:21:12 ns507839 pmxcfs[16543]: [dcdb] crit: cpg_initialize failed: 2
Jun 29 10:21:12 ns507839 pmxcfs[16543]: [status] crit: cpg_initialize failed: 2
Jun 29 10:21:18 ns507839 pmxcfs[16543]: [quorum] crit: quorum_initialize failed: 2
Jun 29 10:21:18 ns507839 pmxcfs[16543]: [confdb] crit: cmap_initialize failed: 2
Jun 29 10:21:18 ns507839 pmxcfs[16543]: [dcdb] crit: cpg_initialize failed: 2
Jun 29 10:21:18 ns507839 pmxcfs[16543]: [status] crit: cpg_initialize failed: 2
Any solution for this issue?
Comments
https://forum.proxmox.com/threads/cluster-upgrade-fails-after-proxmox-3-x-upgrade-to-4-0.24278/
similar. You need more debugging and a background story.
Get an enterprise subscription of proxmox and use their support or at least go over their board to ask for your problems...
We already are aware now, that we should not order any of your services after you start offering.