Faruque Ahmed : MCP, MCSA, MCSE, MCTS, MCIT, CCNA, OCA, OCP, GCP

Cluster

Remove node from Proxmox cluster

# systemctl stop pve-cluster.service

# systemctl stop corosync.service

# pmxcfs -l

# rm -rf /etc/pve/corosync.conf

# rm -rf /etc/pve/corosync/*

# killall pmxcfs

# systemctl start pve-cluster.service

root@proxmox2:~# pvecm nodes

Membership information

----------------------

Nodeid Votes Name

1 1 proxmox1 (local)

2 1 proxmox2

3 1 proxmox3

root@proxmox2:~# pvecm expected 1

root@proxmox2:~# pvecm delnode proxmox3

# rm -rf /etc/pve/nodes/proxmox3

# rm -rf /var/lib/corosync/*

set the cluster file system on the node to be isolated to local mode:

# rpmxcfs -l

how to remove the directories. The trick was once again, to remove the whole cluster with

rm -f /etc/pve/cluster.conf /etc/pve/corosync.conf

rm -f /etc/cluster/cluster.conf /etc/corosync/corosync.conf

rm /var/lib/pve-cluster/.pmxcfs.lockfile

Remove existing cluster configuration and rejoin

# Stop corosync and pve-cluster servicessystemctl stop corosyncsystemctl stop pve-cluster
# Remove existing cluster configurationpmtool rm local
# Remove corosync filesrm -f /etc/corosync/authkeyrm -f /etc/corosync/corosync.confrm -rf /var/lib/corosync/*
# Remove cluster databaserm -f /var/lib/pve-cluster/config.dbrm -rf /var/lib/pve-cluster/*
# Start pve-cluster servicesystemctl start pve-cluster
# Now try to join the cluster againpvecm add <existing-cluster-node-ip>

2: If you want to completely reset the node

# Stop all servicessystemctl stop pve-clustersystemctl stop corosyncsystemctl stop pvedaemonsystemctl stop pveproxy
# Remove all cluster filesrm -f /etc/pve/corosync.confrm -f /etc/corosync/*rm -rf /var/lib/corosync/*rm -f /var/lib/pve-cluster/config.db
# Restart servicessystemctl start pve-clustersystemctl start pvedaemonsystemctl start pveproxy
# Now the node should be ready to join a new cluster

3: If this node should remain in the existing cluster

# Check cluster statuspvecm status
# Check nodes in clusterpvecm nodes
# If the cluster is healthy, you might just need to start servicessystemctl start corosyncsystemctl restart pve-cluster

LL

Page updated

Google Sites

Report abuse