Cluster not quorate log

P

prodav

New Member
Feb 4, 2024
2
0
1
Hi !

I have only one proxmox server.

And it seems very slow since some weeks.
Today I'm trying to resolve the issue...

And in the Proxmox UI > Node machine > System > Syslog
I can see these line which appers continuously....

Code: 
Feb 04 18:00:24 proxmox6 pveproxy[19136]: Cluster not quorate - extending auth key lifetime!
Feb 04 18:00:24 proxmox6 pvedaemon[1041]: Cluster not quorate - extending auth key lifetime!

How can I stop this logging ?
I think the server checks something continuously and it's why he's slow...

Maybe I'm wrong, but I'm would like to fix this.

Thanks for your help.
 
Hi,
please share the output of the following:
Code: 
pveversion -v
pvecm status
cat /etc/pve/corosync.conf
 
Hi,

The outputs :

pveversion -v
Code: 
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-5 (running version: 6.1-5/9bf06119)
pve-kernel-5.3: 6.1-1
pve-kernel-helper: 6.1-1
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-15
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
pve-zsync: 2.0-1
qemu-server: 6.1-4
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

pvecm status
Code: 
Cluster information
-------------------
Name:             MYPROXMOX
Config Version:   1
Transport:        knet
Secure auth:      on

Cannot initialize CMAP service

cat /etc/pve/corosync.conf
Code: 
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: proxmox6
    nodeid: 1
    quorum_votes: 1
    ring0_addr: xx.xx.xx.xx
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: MYPROXMOX
  config_version: 1
  interface {
    linknumber: 0
  }
  ip_version: ipv4-6
  secauth: on
  version: 2
}
 
prodav said:
pveversion -v
Code: 
proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
Click to expand...
That is a very old version and has been unsupported for a long time. Please upgrade to the latest version of 7.4 or 8:
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

prodav said:
pvecm status
Code: 
Cluster information
-------------------
Name:             MYPROXMOX
Config Version:   1
Transport:        knet
Secure auth:      on

Cannot initialize CMAP service
Click to expand...
Sounds like corosync has issues, despite it being only one node. What is the output of journalctl -b -u corosync.service -u pve-cluster.service?

Since you have only one node, you could also try to remove the cluster configuration: https://forum.proxmox.com/threads/delete-all-cluster-config-from-proxmox.108478/post-466078
 
Hi fiona,

I have similar issue, kindly help on this

root@pve2:~# journalctl -b -u corosync.service -u pve-cluster.service
Feb 07 19:24:52 pve2 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Feb 07 19:24:52 pve2 pmxcfs[1934]: [main] notice: resolved node name 'pve2' to 'x.x.x.x' for default node IP address
Feb 07 19:24:52 pve2 pmxcfs[1934]: [main] notice: resolved node name 'pve2' to 'x.x.x.x' for default node IP address
Feb 07 19:24:52 pve2 pmxcfs[1946]: [quorum] crit: quorum_initialize failed: 2
Feb 07 19:24:52 pve2 pmxcfs[1946]: [quorum] crit: can't initialize service
Feb 07 19:24:52 pve2 pmxcfs[1946]: [confdb] crit: cmap_initialize failed: 2
Feb 07 19:24:52 pve2 pmxcfs[1946]: [confdb] crit: can't initialize service
Feb 07 19:24:52 pve2 pmxcfs[1946]: [dcdb] crit: cpg_initialize failed: 2
Feb 07 19:24:52 pve2 pmxcfs[1946]: [dcdb] crit: can't initialize service
Feb 07 19:24:52 pve2 pmxcfs[1946]: [status] crit: cpg_initialize failed: 2
Feb 07 19:24:52 pve2 pmxcfs[1946]: [status] crit: can't initialize service
Feb 07 19:24:53 pve2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Feb 07 19:24:53 pve2 systemd[1]: Starting corosync.service - Corosync Cluster Engine...
Feb 07 19:24:53 pve2 corosync[2071]: [MAIN ] Corosync Cluster Engine starting up
Feb 07 19:24:53 pve2 corosync[2071]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vqsim nozzle snmp pie relro bindnow
Feb 07 19:24:53 pve2 corosync[2071]: [TOTEM ] Initializing transport (Kronosnet).
Feb 07 19:24:54 pve2 corosync[2071]: [TOTEM ] totemknet initialized
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] pmtud: MTU manually set to: 0
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync configuration map access [0]
Feb 07 19:24:54 pve2 corosync[2071]: [QB ] server name: cmap
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync configuration service [1]
Feb 07 19:24:54 pve2 corosync[2071]: [QB ] server name: cfg
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Feb 07 19:24:54 pve2 corosync[2071]: [QB ] server name: cpg
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync profile loading service [4]
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
Feb 07 19:24:54 pve2 corosync[2071]: [WD ] Watchdog not enabled by configuration
Feb 07 19:24:54 pve2 corosync[2071]: [WD ] resource load_15min missing a recovery key.
Feb 07 19:24:54 pve2 corosync[2071]: [WD ] resource memory_used missing a recovery key.
Feb 07 19:24:54 pve2 corosync[2071]: [WD ] no resources configured.
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync watchdog service [7]
Feb 07 19:24:54 pve2 corosync[2071]: [QUORUM] Using quorum provider corosync_votequorum
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Feb 07 19:24:54 pve2 corosync[2071]: [QB ] server name: votequorum
Feb 07 19:24:54 pve2 corosync[2071]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Feb 07 19:24:54 pve2 corosync[2071]: [QB ] server name: quorum
Feb 07 19:24:54 pve2 corosync[2071]: [TOTEM ] Configuring link 0
Feb 07 19:24:54 pve2 corosync[2071]: [TOTEM ] Configured link number 0: local addr: x.x.x.x, port=5405
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 0)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 1 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] link: Resetting MTU for link 0 because host 2 joined
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 3 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 4 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 4 has no active links
Feb 07 19:24:54 pve2 corosync[2071]: [KNET ] host: host: 4 (passive) best link: 0 (pri: 1)
lines 1-57

​

 
Please share and check your corosync configuration and the output of pveversion -v. Are you running any other traffic on the same network, can you ping the hosts from each other on the corosync network without issues? See also the requirements in: https://pve.proxmox.com/pve-docs/chapter-pvecm.html
 
You must log in or register to reply here.
Top Bottom