Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Proxmox cluster not ready – How we resolve it!

by | Jan 22, 2020

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:

proxmox cluster not ready

 

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.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

4 Comments

  1. Radu

    Thank you! It greatly helped me

    Reply
  2. Jader

    Thank you

    Reply
  3. Gilmar

    Thank you! You save me.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF