[quorum] crit: quorum_initialize failed: 2

gavin-way

New Member
Jul 9, 2021
1
0
1
29
Hello everyone, I have encountered a problem for how long. My PVE cluster nodes are always restarted from time to time. The log contains the following information. It's the same with closing pve-ha-lrm and pve-ha-crm.

Here is the output of journalctl -u pve-cluster" :
Jul 09 15:52:38 52-23 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jul 09 15:52:39 52-23 pmxcfs[1244]: [quorum] crit: quorum_initialize failed: 2
Jul 09 15:52:39 52-23 pmxcfs[1244]: [quorum] crit: can't initialize service
Jul 09 15:52:39 52-23 pmxcfs[1244]: [confdb] crit: cmap_initialize failed: 2
Jul 09 15:52:39 52-23 pmxcfs[1244]: [confdb] crit: can't initialize service
Jul 09 15:52:39 52-23 pmxcfs[1244]: [dcdb] crit: cpg_initialize failed: 2
Jul 09 15:52:39 52-23 pmxcfs[1244]: [dcdb] crit: can't initialize service
Jul 09 15:52:39 52-23 pmxcfs[1244]: [status] crit: cpg_initialize failed: 2
Jul 09 15:52:39 52-23 pmxcfs[1244]: [status] crit: can't initialize service
Jul 09 15:52:40 52-23 systemd[1]: Started The Proxmox VE cluster filesystem.
Jul 09 15:52:45 52-23 pmxcfs[1244]: [status] notice: update cluster info (cluster name gsidc-52-x, version = 8)

And here is the output of "cat /etc/pve/corosync.conf" :
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: 52-14
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.52.14
}
node {
name: 52-18
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.52.18
}
node {
name: 52-19
nodeid: 3
quorum_votes: 1
ring0_addr: 192.168.52.19
}
node {
name: 52-21
nodeid: 4
quorum_votes: 1
ring0_addr: 192.168.52.21
}
node {
name: 52-22
nodeid: 5
quorum_votes: 1
ring0_addr: 192.168.52.22
}
node {
name: 52-23
nodeid: 6
quorum_votes: 1
ring0_addr: 192.168.52.23
}
}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: gsidc-52-x
config_version: 8
interface {
linknumber: 0
}
ip_version: ipv4-6
secauth: on
version: 2
}

And here is the output of "pveversion -v" :
proxmox-ve: 6.4-1 (running kernel: 5.4.119-1-pve)
pve-manager: 6.4-9 (running version: 6.4-9/5f5c0e3f)
pve-kernel-5.4: 6.4-3
pve-kernel-helper: 6.4-3
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph: 14.2.20-pve1
ceph-fuse: 14.2.20-pve1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

I look forward to your answers,online
 
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!