[SOLVED] Enable second corosync ring

L

lDemoNl

Member
Proxmox Subscriber
Oct 23, 2020
83
3
13
31
Hi guys! I stucked and need help. I have cluster (8 nodes) and tried add vLAN for corosync. When I modified corosync.conf file on non-master node, new file not modified on another nodes, but when I modified corosync.conf on master node, and restarted corosync service system rewrite file (delete newly added ringX)
pve-manager/7.2-7/d0dd0e85
I have another cluster (3 nodes), there when I modified corosync.conf on master node, this file was updated on all hosts.
pve-manager/6.4-13/9f411e79
So, what am I doing wrong?
 
fiona said:
Hi,
there is no master node for Corosync, each node gets (by default) one vote. Please see the documentation for how to best edit the file. Did you increment the config_version? Were there any errors (check with journalctl -b -u corosync.service)?
Click to expand...
I edited .conf file without copying to temp and then replacing original file. Then I tried to edit config_version in original file, and have no result.
 
Does diff /etc/corosync/corosync.conf /etc/pve/corosync.conf find a mismatch on any of your nodes?
Please share the log from journalctl -b -u corosync.service or /var/log/syslog from around the time you edit the file, once from the node where you edit the file and once from a different node.
 
fiona said:
Does diff /etc/corosync/corosync.conf /etc/pve/corosync.conf find a mismatch on any of your nodes?
Please share the log from journalctl -b -u corosync.service or /var/log/syslog from around the time you edit the file, once from the node where you edit the file and once from a different node.
Click to expand...
Thank you. It was my mistake bcause I forgot to change version. I reset all my changes and then tried to change step-by-step by documentation and everything works fine
 
@fiona my previous success was on second test cluster. But I tried to repeat steps on my production, and there I got a trouble.
I edited corosync.conf file, but changes didn't applied on nodes.
There is output when I already changed corosync.conf on node 1
Code: 
Sep 01 11:14:07 ala220pve01 systemd[1]: Stopping Corosync Cluster Engine...
Sep 01 11:14:07 ala220pve01 corosync-cfgtool[3672000]: Shutting down corosync
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [MAIN  ] Node was shut down by a signal
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Unloading all Corosync service engines.
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [QB    ] withdrawing server sockets
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync vote quorum service v1.0
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [CFG   ] Node 3 was shut down by sysadmin
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [QB    ] withdrawing server sockets
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync configuration map access
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [QB    ] withdrawing server sockets
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync configuration service
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [QB    ] withdrawing server sockets
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync cluster closed process group service v1.01
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [QB    ] withdrawing server sockets
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync cluster quorum service v0.1
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync profile loading service
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync resource monitoring service
Sep 01 11:14:07 ala220pve01 corosync[343541]:   [SERV  ] Service engine unloaded: corosync watchdog service
Sep 01 11:14:08 ala220pve01 corosync[343541]:   [MAIN  ] Corosync Cluster Engine exiting normally
Sep 01 11:14:08 ala220pve01 systemd[1]: corosync.service: Succeeded.
Sep 01 11:14:08 ala220pve01 systemd[1]: Stopped Corosync Cluster Engine.
Sep 01 11:14:08 ala220pve01 systemd[1]: corosync.service: Consumed 1d 8h 20min 8.547s CPU time.
Sep 01 11:14:08 ala220pve01 systemd[1]: Starting Corosync Cluster Engine...
Sep 01 11:14:08 ala220pve01 corosync[3672007]:   [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Sep 01 11:14:08 ala220pve01 corosync[3672007]:   [MAIN  ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf vqsim nozzle snmp pie relro bindnow
Sep 01 11:14:08 ala220pve01 corosync[3672007]:   [TOTEM ] Initializing transport (Kronosnet).
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] totemknet initialized
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync configuration map access [0]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QB    ] server name: cmap
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync configuration service [1]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QB    ] server name: cfg
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QB    ] server name: cpg
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync profile loading service [4]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [WD    ] Watchdog not enabled by configuration
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [WD    ] resource load_15min missing a recovery key.
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [WD    ] resource memory_used missing a recovery key.
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [WD    ] no resources configured.
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync watchdog service [7]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QUORUM] Using quorum provider corosync_votequorum
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QB    ] server name: votequorum
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QB    ] server name: quorum
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] Configuring link 0
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] Configured link number 0: local addr: 172.16.133.136, port=5405
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] Configuring link 1
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] Configured link number 1: local addr: 10.222.145.6, port=5406
Sep 01 11:14:09 ala220pve01 systemd[1]: Started Corosync Cluster Engine.
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QUORUM] Sync members[1]: 3
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QUORUM] Sync joined[1]: 3
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [TOTEM ] A new membership (3.b4a) was formed. Members joined: 3
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [QUORUM] Members[1]: 3
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [MAIN  ] Completed service synchronization, ready to provide service.
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:09 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 has no active links
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 9 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 8 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 7 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 5 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 2 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 9 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 7 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 6 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 1 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] rx: host: 4 link: 0 is up
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 5 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 6 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] host: host: 4 (passive) best link: 0 (pri: 1)
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 9 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 8 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 7 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 6 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 5 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 2 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 1 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: PMTUD link change for host: 4 link: 0 from 469 to 1397
Sep 01 11:14:13 ala220pve01 corosync[3672007]:   [KNET  ] pmtud: Global data MTU changed to: 1397
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [QUORUM] Sync members[9]: 1 2 3 4 5 6 7 8 9
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [QUORUM] Sync joined[8]: 1 2 4 5 6 7 8 9
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [TOTEM ] A new membership (1.b4e) was formed. Members joined: 1 2 4 5 6 7 8 9
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [QUORUM] This node is within the primary component and will provide service.
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Sep 01 11:14:14 ala220pve01 corosync[3672007]:   [MAIN  ] Completed service synchronization, ready to provide service.
 
Then I tried restart corosync on my node 2 and node is down. There's output
Code: 
root@ala924bf02pve12:~# journalctl -u corosync | tail -25
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 4 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 8 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 3 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] host: host: 5 (passive) best link: 0 (pri: 1)
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 8 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 7 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 6 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 5 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 2 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 1 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 4 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: PMTUD link change for host: 3 link: 0 from 469 to 1397
Sep 01 11:28:25 ala924bf02pve12 corosync[4130184]:   [KNET  ] pmtud: Global data MTU changed to: 1397
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QUORUM] Sync members[9]: 1 2 3 4 5 6 7 8 9
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QUORUM] Sync joined[8]: 1 2 3 4 5 6 7 8
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [TOTEM ] A new membership (1.b60) was formed. Members joined: 1 2 3 4 5 6 7 8
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [CMAP  ] Received config version (10) is different than my config version (9)! Exiting
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Unloading all Corosync service engines.
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QB    ] withdrawing server sockets
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync vote quorum service v1.0
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QB    ] withdrawing server sockets
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync configuration map access
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QB    ] withdrawing server sockets
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync configuration service
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QB    ] withdrawing server sockets
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync cluster closed process group service v1.01
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [QB    ] withdrawing server sockets
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync cluster quorum service v0.1
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync profile loading service
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync resource monitoring service
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [SERV  ] Service engine unloaded: corosync watchdog service
Sep 01 11:28:27 ala924bf02pve12 corosync[4130184]:   [MAIN  ] Corosync Cluster Engine exiting normally
Sep 01 11:28:28 ala924bf02pve12 systemd[1]: corosync.service: Control process exited, code=exited, status=1/FAILURE
Sep 01 11:28:28 ala924bf02pve12 systemd[1]: corosync.service: Failed with result 'exit-code'.

Node can't start corosync.service because version is different on nodes.
But /etc/corosync/corosync.conf and /etc/pve/corosync.conf identical

Could I replace corosync.conf from corosync.conf.bak file without problems? Because version is lower than ?
 
Last edited:
I've replaced /etc/corosync/corosync.conf.bak to /etc/corosync/corosync.conf on node 1, but without result.
Then I've tried reboot failed node and nothing changed. Via web I can access to node but I can't migrate VM's from this node, telling me that cluster is not quorate
 
What about the other nodes? They probably got the new config already (please check to make sure) which would be good. Can you try to copy the new config from another node to the node where the service fails?
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back