Are you stuck with Proxmox cluster not ready? We can help you fix it.
If we remove a node from the cluster in Proxmox and try to add or delete a VM then this error will occur.
Here at Bobcares, we often receive requests to fix Proxmox errors as a part of our Server Management Services.
Today, let’s see how our Support Engineers fix Proxmox cluster not ready.
Causes for Proxmox cluster not ready
This error occurs when we remove a node from the cluster.
If the cluster has 2 nodes and the two nodes are mentioned to access the quorum.
After removing a node from the cluster only a single node is active. Thus the quorum permission becomes a read-only state.
To resolve the error we change the node from 2 to 1 in the default configuration.
The sample error looks like:
How to fix Proxmox cluster not ready
Recently one of our customers contacted us with the error ‘cluster not ready’ when trying to delete the virtual machine. Let’s now discuss how our Support Engineers resolve this error for our customers.
Cluster not ready – no quorum? (500)
First we login to the Proxmox server.
Then we check the state of the cluster using the command
pvecm status
From the result, we find that the Quorum activity is blocked.
Thus we execute the below command to change the votes from 2 to 1.
pvecm expected 1
After executing the command we will be able to delete the VM.
If the VM gets locked during the process, we unlock the VM using the command
qm unlock
Then we delete the Virtual Machine.
Cluster not ready due to corosync
Another reason for the error is when the corosync is incorrect. Our Support Engineers analyze the corosync configuration file.
The configuration file is present at the location
/etc/pve/corosync.conf
We stop the corosync service first by running the command.
systemctl stop corosync.service
Then we make the required changes in the file.
After making the changes we start the service back.
systemctl start corosync.service
[Need any further assistance with Proxmox errors? – We’ll help you]
Conclusion
In short, we’ve discussed the causes of the error. Also, we’ve discussed how our Support Engineers resolve the error for our customers.
thank you very much for your help
Thank you! It greatly helped me
Thank you
Thank you! You save me.