Search results

  1. F

    Nodes not joining cluster after restart

    nodeid: 1 root@ch1flvps05:~# journalctl -u corosync | tail -20 Aug 22 06:25:16 ch1flvps05 corosync[1444]: [TOTEM ] A new membership (190.215.57.194:880) was formed. Members joined: 2 Aug 22 06:25:16 ch1flvps05 corosync[1444]: [TOTEM ] A new membership (190.215.57.194:884) was formed. Members...
  2. F

    Nodes not joining cluster after restart

    working node (nodeid: 1) logging { debug: off to_syslog: yes } nodelist { node { name: ch1flvps06 nodeid: 2 quorum_votes: 1 ring0_addr: ch1flvps06 } node { name: ch1flvps07 nodeid: 3 quorum_votes: 1 ring0_addr: ch1flvps07 } node { name...
  3. F

    Nodes not joining cluster after restart

    Thanks manu, I have compared corosync.conf across all nodes and the content is the same, in /etc/corosync/corosync.conf and /etc/pve/corosync.conf
  4. F

    Nodes not joining cluster after restart

    Hi, I have a cluster with 3 nodes, after a power outage two nodes restarted and are not joining the cluster, corosync is not running and when trying to restart the service the log shows the following error: "[CMAP ] Received config version (4) is different than my config version (5)! Exiting"...

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!