corosync

Recently, I've added multiple qdevices to several clusters running older versions of PVE without any issues, using command: pvecm qdevice setup 192.168.1.xxx -f and corosync-qdevice. Issue regarding certificate authentication. However, my latest 2-node cluster is running VE 8.2.2, where the...

Hello, From what I see, the corosync uses max number of cluster nodes+1 as a quorum for the cluster. So in 11 node cluster, 6 is the quorum. This is logically ok, but in real life scenarios, I need to have part or cluster to shutdown, and if shut down part is 5, then one more node and cluster...

... and nobody heard it, did it make a sound? How often (per month, year?) do you get the [KNET ] link: host: X link: 0 is down on otherwise healthy network in production dedicated redundant setups without losing quorum? Does anyone check? How many nodes are there in your cluster? Is that...

Hi, thank you for accepting me into this community. I have set up a new cluster for production (my first non vSPhere cluster) and I am running into a little problem. Given that we have a 4 node cluster I wanted to add additional quorum following the Instructions from the manual...

PVE 8.2 I have configured a 4 node cluster, and am wondering if it is possible to just copy corosync.conf to /etc/pve/corosync.conf and /etc/corosync/corosync.conf to my nodes if i were to start from scratch (fresh install of pve) on all nodes. Would this create and "join" the nodes to the...

Hi everyone, I'm experiencing an issue where NODE1 in my Proxmox VE cluster is restarting when both NODE2 and NODE3 are powered off, even after I've made several adjustments to the corosync.conf configuration. Below is a summary of the setup and the steps I've taken: Configuration Overview...

When i look at pvecm status i see that 3 of my nodes have NR status , that mean not reachebol, sould not all nodes have de status a,v,nmw? root@proxmox4-int:~# pvecm status Cluster information ------------------- Name: HCC-hobbynet Config Version: 27 Transport: knet...

I am relatively new to Proxmox and have a cluster running with 3 nodes, everything is currently working fine, cluster is up HA is running fine. The issue I face currently is that in case the cluster link goes down for let's say more than 10s, watchdog kicks in and reboots the server, this causes...

Hello together, I'd like to build a PVE HA Cluster out of 2 PVE Nodes and 1 QDev to get quorum. In order to get a nice and stable Corosync Link, I've a dedicated 1G NIC via Crossover LAN between the 2 PVE nodes. The QDev VM is a external hosted system and can't be connected via LAN. The Plan...

Hi everyone, I'm currently facing a problem when adding a QDevice to a 2-node cluster. Current cluster: 2x Proxmox VE 8.2.2 QDevice: 1x Proxmox Backup-Server 3.2-2 - I can remote from both nodes into PBS as root - corosync-qdevice is installed on both nodes - corosync-qnetd and...

Good morning, since setting up a cluster with 3 nodes (all running PVE 8.2.2), we've been experiencing an issue where they no longer communicate with each other after a maximum of 24 hours. The hosts are directly connected to each other via a switch. There is no load on the ports in the switch...

I especially want to know what protection mechanism the PVE cluster has to allow the host to automatically restart. Environment: There are 13 hosts in the cluster: node1-13 Version: pve-manager/6.4-4/337d6701 (running kernel: 5.4.106-1-pve) Web environment: There are two switches A and B...

Hi, i am using Proxmox with ZFS replication and HA, i have set the /etc/pve/corsync.conf: quorum_votes: 1 two_nodes: yes but everytime the pve1 crashes the pve2 stays on "waiting for quorum", when pve1 is online again the option is back to default, how to solve this?

Hallo zusammen, ich habe ein Cluster konfiguriert, wo nicht alle Nodes die gleiche Anzahl an Votes haben soll. Grund dafür ist deren Standort. Soweit so gut. Allerdings werden nach aktueller Konfiguration 17 Votes benötigt um Quorum zu erreichen. Aufgrund der Konstellation reichen allerdings...

Hi all, I would like to cluster some VMs within my Proxmox Homer Lab, using Pacemaker and Corosync. i world then like to create a couple of Shared Storage Devices between the nodes, all sharing the same respective "physical" storage devices underneath. The idea is to create two, one being a...

So, as the title says, I am deploying all new Proxmox servers to replace our aging fleet of 2U Dells. Currently, I have a 10G trunk for all of my normal VLANs and a separate 10G connection specific to only Corosync VLAN traffic. My new servers have 4 x 10G NICs and 2 x 100G NICs each. I was...

I'm having issues getting corosync to start up, causing my node to be unable to connect to the other. Diagnostics so far I've tested the basics like pinging one node from the other and it works fine.\ Results from journalctl -xeu pve-cluster.service Jan 15 18:15:49 pve847 pmxcfs[122430]...

There's a great deal of misleading piece of argument to be found in currently official PVE docs on QDevices [1] and then some conscious effort to take it even further. Under "Supported setups" [1] the following is advised (emphasis mine): It continues to provide an absurd piece of reasoning...

I have a small cluster of just 2 devices, I will be adding a 3rd in the not too distant future. One of the nodes has 10gb uplink to external, the other only has 1gb. This means that synching between the two is limited to 1GB of course. I've added a 10gb network card to the node with 1GB...

It's nowhere in the PVE official docs, but corosync does support last_man_standing and when used with HA it is suggested to also set wait_for_all. I found some previous threads, but not in relation to HA. Now I understand the official PVE endorsed way would be to just use a qdevice, but this...