Bobcares

Proxmox remove node from cluster – How we safely remove it?

by | Dec 29, 2019

Are you looking for how to remove a node from the cluster in Proxmox? We can help you remove it

Removing a node from the cluster can be done with a few simple steps.

At Bobcares, we often get requests on Proxmox management, as a part of our Infrastructure Management Services.

Today, we will discuss how our Support Engineers remove a node from cluster in Proxmox.

A quick look at Proxmox, cluster, and node

Proxmox VE is a popular open-source server virtualization platform. By using Proxmox we can manage two virtualization technologies – KVM for VMs and LXC for containers. The advantage is, we can manage both using a single web-based interface.

A cluster is a group of physical servers and other resources connected together. It enables high availability and parallel processing as per setup. In Proxmox we can create the cluster using Proxmox VE cluster manager or pvecm. Whereas a single physical system is known as a node in virtualization.

So now let us see how our Support Engineers remove a node from the cluster.

 

How to remove a node from the Proxmox cluster?

Removing a node from a cluster is something we must do with care. Because this should not affect the already running nodes. So there are the steps our Support Engineers follow to remove the node.

1. Initially, we move all VMs to another active node. We do live or offline migration by looking at the storage type.

2. Next we login to another active node to list the nodes in the cluster. This is to get the node ID of the node we remove.

3. Then we shut down the node we want to remove.

4. Finally, we execute the command to remove the node. And the command appears as,

Proxmox command to remove node from cluster.

 

5. Then we verify it using the below command. The list should display without the deleted node.

pvecm nodes

6. Later we remove the node from Proxmox GUI. For this, we login to any active node. Then we check /etc/pve/nodes folder. And we check for the folder name of the removed node and remove it. Otherwise, the GUI displays the removed node in it.

 

[Still, having trouble in removing a node from the Proxmox cluster? – We can help you.]

 

Conclusion

So far, we saw the steps to remove a node from the Proxmox cluster. We also how our Support Engineers do this will all precautions to avoid errors afterward.

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";

3 Comments

  1. Wolfgang Sprick

    Followed your description. status shows just the single node left. Directory in /etc/pve/nodes/ deleted, deleted node without power, remaining node rebooted … but deleted node still shows up in the GUI of the remaining node.

    Remaining node is an outdated VE 6.4

    Any hint?

    Reply
    • Hiba Razak

      Hi,
      Please contact our support team via live chat(click on the icon at right-bottom).

      Reply
    • Dan Mandle

      Try editing the /etc/pve/corosync.conf file

      Reply

Submit a Comment

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

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

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

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

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