Differences

This shows you the differences between two versions of the page.

--- virtualization:proxmox:clustercorosynccleanup [2026/04/03 02:09] – old revision restored (2024/12/17 20:33) 114.119.159.86
+++ virtualization:proxmox:clustercorosynccleanup [2026/04/08 17:46] (current) – old revision restored (2025/07/24 20:05) 57.141.20.17
@@ Line 1: / Line 1: @@
 ====== Cleaning up PVE Corosync after removing from cluster ======
- At times it will be needed to remove a server from a cluster or there has been problems connecting a new node to an existing ProxMox cluster. Once the server has been removed from the cluster using "pvecm delnode" there will be leftover cluster configs on the removed node that will prevent rejoining to the ProxMox cluster or cause troubles when connecting to another cluster.
+  At times it will be needed to remove a server from a cluster or there has been problems connecting a new node to an existing ProxMox cluster. At such times it will be necessary to get to a point where pve-cluster/corosync can start fresh. For this to work you will also need to ensure that the server has been completely and cleanly removed from the ProxMox cluster as well. The steps to clean pve-cluster/corosync are as follows:
- When this happens it will be necessary to get to a point where pve-cluster/corosync can start fresh. For this to work you will also need to ensure that the server has been completely and cleanly removed from the ProxMox cluster as well. The steps to clean pve-cluster/corosync are as follows:
-<code>systemctl stop pve-cluster corosync
+  <code>systemctl stop pve-cluster corosync
 pmxcfs -l
 rm /etc/corosync/*