Hello there,
last week I updated my PVE two node Cluster, but after rebooting since a while i ran into some problems:
Both nodes currently are online, but keep complaning that there is no quorum.
In the webui this looks like this :
Anyway from the webui of both nodes i get the actual informations about the other node, even uptime and resources stats are shown in the summary menu.
Following some research results this must have to do with the corosync.service.
So here you see the corosync.service which is identical on both nodes:
anyway the service must have failed by any reason:
An here is where the things get spooky in my eyes:
so if i get this right from the corosync.service the node ganymed has the nodeid 1, anyway it's connected to himself as nodeid 2 as well?
In case that's true the corosync service seems to have failed by the shown mismatch, right?
Does anybody know how to debug this further or how to resolve this?
Thanks a lot for any kind of Ideas
Maphisto
last week I updated my PVE two node Cluster, but after rebooting since a while i ran into some problems:
Both nodes currently are online, but keep complaning that there is no quorum.
In the webui this looks like this :
Anyway from the webui of both nodes i get the actual informations about the other node, even uptime and resources stats are shown in the summary menu.
Following some research results this must have to do with the corosync.service.
So here you see the corosync.service which is identical on both nodes:
Code:
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: CALLISTO
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.2.3
}
node {
name: GANYMED
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.2.10
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: JUPITER
config_version: 3
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 3
}anyway the service must have failed by any reason:
Code:
root@GANYMED:~# corosync-cfgtool -s
Local node ID 1, transport knet
LINK ID 0
addr = 192.168.2.10
status:
nodeid: 1: connected
nodeid: 2: localhost
root@CALLISTO:~# corosync-cfgtool -s
Could not initialize corosync configuration API error 2An here is where the things get spooky in my eyes:
so if i get this right from the corosync.service the node ganymed has the nodeid 1, anyway it's connected to himself as nodeid 2 as well?
In case that's true the corosync service seems to have failed by the shown mismatch, right?
Does anybody know how to debug this further or how to resolve this?
Thanks a lot for any kind of Ideas
Maphisto
