[SOLVED] Another "cluster not ready - no quorum? (500)" case

PeterZ

New Member
Jul 18, 2019
20
0
1
51
Hi all, new Proxmox user since a few months for a home server.
I have some basic experience with vmware & virtualbox but recently got a refurbished mini pc which I geared up with Proxmox and a few containers and vm's; initially this was a test but because I liked it, I continued this path.

Everything was fine, I installed a second node and thought of moving containers and vm's to this machine so that I could reinstall the main system with a recently repurposed SSD - now all is on 1 HD.
So I created a cluster, tried through migration in the web interface but got stuck on the systems not being reachable.
Moved them back to first node and everything was OK.

Yesterday I got the 'no valid subscription message and after making some changes to the sources files, I got some updates, which I installed.
Now my containers and vm's don't boot anymore with this "cluster not ready - no quorum? (500)" message.

The second node is still showing but not manageable anymore from the first and if I click on it, I get "hostname lookup 'pve2' failed - failed to get address info for: pve2: No address associated with hostname (500)" although it's running and I can manage it from it's own web interface.

I don't need this second node right anymore, so no matter what happens with it but I have some data in a vm on the first node that I would like to get my hands on.
If possible, recovering the first node with the systems, would be a bonus.

Is this possible and if so, how?
TIA!
Peter
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
804
66
33
You can temporarily set 'pvecm expected 1' which sets the expected votes to 1. Make sure the other node has no access to any of the VMs or storages the first node uses.

Please post your corosync config (/etc/pve/corosync.conf), your /etc/hosts file and your /etc/network/interfaces file. If there are any public IP addresses in there you might want to mask them.
 
  • Like
Reactions: PeterZ

PeterZ

New Member
Jul 18, 2019
20
0
1
51
Hi mira, thanks for picking this up!
It's not clear to me if changing that setting was the only thing to solve this since you're asking for these files, but the node is back up and running.

Thanks a LOT!
Peter
 

Syrrys

New Member
Nov 8, 2020
1
0
1
41
Hey,

Just wanted to add a note for anyone else who comes across this thread looking to setup a small homelab with 2 nodes.

according to man corosync.conf and man votequorum explain that adding two_node: 1
to the quorum{} section of /etc/corosync/corosync.conf will create a special case where the usual (nodes/2)+1 quorum rule doesn't apply.

I'm not sure yet what other changes might be needed to get or keep this setup stable but for me, this is letting me get on with spinning up new VMs etc.
 

ieronymous

Member
Apr 1, 2019
106
5
23
41
Hey,

Just wanted to add a note for anyone else who comes across this thread looking to setup a small homelab with 2 nodes.

according to man corosync.conf and man votequorum explain that adding two_node: 1
to the quorum{} section of /etc/corosync/corosync.conf will create a special case where the usual (nodes/2)+1 quorum rule doesn't apply.

I'm not sure yet what other changes might be needed to get or keep this setup stable but for me, this is letting me get on with spinning up new VMs etc.
By that you mean the line two_node: 1 to be inserted on both nodes?
Like

quorum {
provider: corosync_votequorum
two_node: 1
}
...... because didnt seem to work for me? Did you have to update any service afterwards even though I rebooted the server
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!