[SOLVED] Issues with corosync.conf Synchronization in Proxmox Cluster After Manual Edits

saygonka

New Member
Sep 22, 2024
3
1
3
Hi!
After manually editing the corosync.conf file, the cluster synchronized the file across the nodes, but any subsequent attempt to modify the file results in the file being overwritten with the original manually modified version after restarting the corosync and pve-cluster services.

I also tried making the same changes to the file on both nodes, but after a system reboot, the file is still overwritten with the old version. Unfortunately, I cannot find any errors in the logs, and pvecm status looks fine as well. Do you have any suggestions on what I should check to fix the corosync.conf synchronization?

Thanks!
 
It looks like you have 2 nodes only. I suppose you have a good /etc/corosync/corosync.conf (mind the path, not /etc/pve one).

In that case, on BOTH nodes:

EDIT: Important - do this over direct SSH connection or locally, not GUI.

Bash:
systemctl stop pve-cluster
killall pmxcfs
systemctl stop corosync

# increase the config_version as well, just to be sure
cp ~/your_corosync_conf_copy /etc/corosync/corosync.conf

systemctl start corosync

# post the output of the below here if still having trouble, from BOTH nodes
corosync-cfgtool -s

systemctl start pve-cluster

If it's not working, post your corosync.conf content here as well.

Good luck!
 
Last edited:
Thank you, I can now edit the file, and after restarting the aforementioned services, the configuration remains as I saved it. However, I have to make changes in both files at the same time, otherwise restarting the corosync service on node number 2 fails. In other words, the main problem has been solved, meaning the configuration is no longer overwritten, but the configuration from node1 is not synchronized with node2.

corosync.conf

Code:
root@pveb01:~# cat /etc/corosync/corosync.conf
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: pveb01
    nodeid: 1
    quorum_votes: 1
    ring0_addr: xx.xx.xx.xx
    ring1_addr: 192.168.65.3
  }
  node {
    name: pveb02
    nodeid: 2
    quorum_votes: 1
    ring0_addr: yy.yy.yy.yy
    ring1_addr: 192.168.65.2
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: clusterexo
  config_version: 5
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

corosync-cfgtool -s

Bash:
root@pveb01:~# corosync-cfgtool -s
Local node ID 1, transport knet
LINK ID 0 udp
    addr    = xx.xx.xx.xx
    status:
        nodeid:          1:    localhost
        nodeid:          2:    connected
LINK ID 1 udp
    addr    = 192.168.65.3
    status:
        nodeid:          1:    localhost
        nodeid:          2:    connected
Bash:
root@pveb02:~# corosync-cfgtool -s
Local node ID 2, transport knet
LINK ID 0 udp
    addr    = yy.yy.yy.yy
    status:
        nodeid:          1:    connected
        nodeid:          2:    localhost
LINK ID 1 udp
    addr    = 192.168.65.2
    status:
        nodeid:          1:    connected
        nodeid:          2:    localhost
 
Last edited:
This is expected. Sorry for not mentioning . :)

Now that you have your quorum back, you actually can edit (copy in) the /etc/pve file (increase config_version once more - you may literally do only that). You do NOT stop any services, just move over the original one. It will get distributed, i.e. you do this only once.

(Under normal circumstances, i.e. when everything works, you want to only edit the /etc/pve file.)
 
  • Like
Reactions: saygonka
This is expected. Sorry for not mentioning . :)

Now that you have your quorum back, you actually can edit (copy in) the /etc/pve file (increase config_version once more - you may literally do only that). You do NOT stop any services, just move over the original one. It will get distributed, i.e. you do this only once.

(Under normal circumstances, i.e. when everything works, you want to only edit the /etc/pve file.)

Thank you for your help! ☺️
 
  • Like
Reactions: esi_y

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!