I'm newbie please help
Rebooting the vm 101 of the node pve resulted in a 500 error
I searched on google and tried everything, but it didn't work-----------------------------------------------------------
https://forum.proxmox.com/threads/another-cluster-not-ready-no-quorum-500-case.56104/
systemctl stop pve-cluster
systemctl stop corosync
pmxcfs -l
rm /etc/pve/corosync.conf
rm /etc/corosync/*
killall pmxcfs
systemctl start pve-cluster
systemctl start pve-cluster
systemctl start corosync
systemctl status pve-cluster
pvecm status
pvecm expected ected 1
pvecm status
pvecm expected ected 1
qm unlock
--------------------------------------------------------------------------------------------------------------------------------------------------------------
root@pve03:/etc/corosync# pvecm status
Cluster information
-------------------
Name: Datacenter
Config Version: 6
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Mon May 22 13:47:14 2023
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 0x00000004
Ring ID: 2.31f
Quorate: No
Votequorum information
----------------------
Expected votes: 6
Highest expected: 6
Total votes: 3
Quorum: 4 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000002 1 103.82.118.250
0x00000004 1 103.82.118.24 (local)
0x00000006 1 103.82.118.28
root@pve03:/etc/corosync# systemctl status pve-cluster corosync
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-19 14:52:36 PST; 2 days ago
Main PID: 996 (pmxcfs)
Tasks: 6 (limit: 38395)
Memory: 62.0M
CPU: 3min 3.303s
CGroup: /system.slice/pve-cluster.service
└─996 /usr/bin/pmxcfs
May 22 12:04:18 pve03 pmxcfs[996]: [dcdb] notice: data verification successful
May 22 12:05:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:21:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:37:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:53:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:04:18 pve03 pmxcfs[996]: [dcdb] notice: data verification successful
May 22 13:09:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:24:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:40:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:56:14 pve03 pmxcfs[996]: [status] notice: received log
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-19 14:52:36 PST; 2 days ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Main PID: 1121 (corosync)
Tasks: 9 (limit: 38395)
Memory: 147.8M
CPU: 46min 20.792s
CGroup: /system.slice/corosync.service
└─1121 /usr/sbin/corosync -f
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Sync members[3]: 2 4 6
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Sync joined[1]: 2
May 22 11:04:23 pve03 corosync[1121]: [TOTEM ] A new membership (2.31f) was formed. Members j>
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Members[3]: 2 4 6
May 22 11:04:23 pve03 corosync[1121]: [MAIN ] Completed service synchronization, ready to pr>
May 22 12:33:42 pve03 corosync[1121]: [KNET ] link: host: 6 link: 0 is down
May 22 12:33:42 pve03 corosync[1121]: [KNET ] host: host: 6 (passive) best link: 0 (pri: 1)
May 22 12:33:42 pve03 corosync[1121]: [KNET ] host: host: 6 has no active links
May 22 12:33:45 pve03 corosync[1121]: [KNET ] rx: host: 6 link: 0 is up
May 22 12:33:45 pve03 corosync[1121]: [KNET ] host: host: 6 (passive) best link: 0 (pri: 1)
--------------------------------------------------------------------------------------------------------------------------------------------------------------
root@pve03:/etc/pve# cat corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: pve01
nodeid: 6
quorum_votes: 1
ring0_addr: 103.82.118.28
}
node {
name: pve02
nodeid: 2
quorum_votes: 1
ring0_addr: 103.82.118.250
}
node {
name: pve03
nodeid: 4
quorum_votes: 1
ring0_addr: 103.82.118.24
}
node {
name: pve04
nodeid: 1
quorum_votes: 1
ring0_addr: 103.82.118.252
}
node {
name: pve05
nodeid: 3
quorum_votes: 1
ring0_addr: 103.82.118.251
}
node {
name: pve06
nodeid: 5
quorum_votes: 1
ring0_addr: 103.82.118.22
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: Datacenter
config_version: 6
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
root@pve03:/etc/pve#
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Rebooting the vm 101 of the node pve resulted in a 500 error
I searched on google and tried everything, but it didn't work-----------------------------------------------------------
https://forum.proxmox.com/threads/another-cluster-not-ready-no-quorum-500-case.56104/
systemctl stop pve-cluster
systemctl stop corosync
pmxcfs -l
rm /etc/pve/corosync.conf
rm /etc/corosync/*
killall pmxcfs
systemctl start pve-cluster
systemctl start pve-cluster
systemctl start corosync
systemctl status pve-cluster
pvecm status
pvecm expected ected 1
pvecm status
pvecm expected ected 1
qm unlock
--------------------------------------------------------------------------------------------------------------------------------------------------------------
root@pve03:/etc/corosync# pvecm status
Cluster information
-------------------
Name: Datacenter
Config Version: 6
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Mon May 22 13:47:14 2023
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 0x00000004
Ring ID: 2.31f
Quorate: No
Votequorum information
----------------------
Expected votes: 6
Highest expected: 6
Total votes: 3
Quorum: 4 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000002 1 103.82.118.250
0x00000004 1 103.82.118.24 (local)
0x00000006 1 103.82.118.28
root@pve03:/etc/corosync# systemctl status pve-cluster corosync
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-19 14:52:36 PST; 2 days ago
Main PID: 996 (pmxcfs)
Tasks: 6 (limit: 38395)
Memory: 62.0M
CPU: 3min 3.303s
CGroup: /system.slice/pve-cluster.service
└─996 /usr/bin/pmxcfs
May 22 12:04:18 pve03 pmxcfs[996]: [dcdb] notice: data verification successful
May 22 12:05:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:21:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:37:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 12:53:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:04:18 pve03 pmxcfs[996]: [dcdb] notice: data verification successful
May 22 13:09:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:24:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:40:14 pve03 pmxcfs[996]: [status] notice: received log
May 22 13:56:14 pve03 pmxcfs[996]: [status] notice: received log
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-19 14:52:36 PST; 2 days ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview
Main PID: 1121 (corosync)
Tasks: 9 (limit: 38395)
Memory: 147.8M
CPU: 46min 20.792s
CGroup: /system.slice/corosync.service
└─1121 /usr/sbin/corosync -f
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Sync members[3]: 2 4 6
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Sync joined[1]: 2
May 22 11:04:23 pve03 corosync[1121]: [TOTEM ] A new membership (2.31f) was formed. Members j>
May 22 11:04:23 pve03 corosync[1121]: [QUORUM] Members[3]: 2 4 6
May 22 11:04:23 pve03 corosync[1121]: [MAIN ] Completed service synchronization, ready to pr>
May 22 12:33:42 pve03 corosync[1121]: [KNET ] link: host: 6 link: 0 is down
May 22 12:33:42 pve03 corosync[1121]: [KNET ] host: host: 6 (passive) best link: 0 (pri: 1)
May 22 12:33:42 pve03 corosync[1121]: [KNET ] host: host: 6 has no active links
May 22 12:33:45 pve03 corosync[1121]: [KNET ] rx: host: 6 link: 0 is up
May 22 12:33:45 pve03 corosync[1121]: [KNET ] host: host: 6 (passive) best link: 0 (pri: 1)
--------------------------------------------------------------------------------------------------------------------------------------------------------------
root@pve03:/etc/pve# cat corosync.conf
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: pve01
nodeid: 6
quorum_votes: 1
ring0_addr: 103.82.118.28
}
node {
name: pve02
nodeid: 2
quorum_votes: 1
ring0_addr: 103.82.118.250
}
node {
name: pve03
nodeid: 4
quorum_votes: 1
ring0_addr: 103.82.118.24
}
node {
name: pve04
nodeid: 1
quorum_votes: 1
ring0_addr: 103.82.118.252
}
node {
name: pve05
nodeid: 3
quorum_votes: 1
ring0_addr: 103.82.118.251
}
node {
name: pve06
nodeid: 5
quorum_votes: 1
ring0_addr: 103.82.118.22
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: Datacenter
config_version: 6
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
root@pve03:/etc/pve#
--------------------------------------------------------------------------------------------------------------------------------------------------------------
