[SOLVED] Remove or reset cluster configuration.
- Thread starter taurolyon
- Start date
systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster
Was the way in Proxmox VE 6
https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node
Here it is again
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster
Was the way in Proxmox VE 6
https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node
Here it is again
Thank you! This still appears to be the way to clear it! EDIT: Not quite there (see next post).
When I attempted this earlier, I must have missed the pmxcfs -l line to force local mode.
When I attempted this earlier, I must have missed the pmxcfs -l line to force local mode.
Code:
.://:` `://:. root@pve
`hMMMMMMd/ /dMMMMMMh` --------
`sMMMMMMMd: :mMMMMMMMs` OS: Proxmox VE 7.2-7 x86_64
`-/+oo+/:`.yMMMMMMMh- -hMMMMMMMy.`:/+oo+/-` Host: PowerEdge R710
`:oooooooo/`-hMMMMMMMyyMMMMMMMh-`/oooooooo:` Kernel: 5.15.39-4-pve
`/oooooooo:`:mMMMMMMMMMMMMm:`:oooooooo/` Uptime: 4 mins
./ooooooo+- +NMMMMMMMMN+ -+ooooooo/. Packages: 746 (dpkg)
.+ooooooo+-`oNMMMMNo`-+ooooooo+. Shell: bash 5.1.4
-+ooooooo/.`sMMs`./ooooooo+- Terminal: /dev/pts/0
:oooooooo/`..`/oooooooo: CPU: Intel Xeon X5670 (24) @ 2.927GHz [36.0°on]
:oooooooo/`..`/oooooooo: GPU: NVIDIA Quadro P620
-+ooooooo/.`sMMs`./ooooooo+- Memory: 19.96GiB / 141.32GiB (14%)
.+ooooooo+-`oNMMMMNo`-+ooooooo+.
./ooooooo+- +NMMMMMMMMN+ -+ooooooo/.
`/oooooooo:`:mMMMMMMMMMMMMm:`:oooooooo/`
`:oooooooo/`-hMMMMMMMyyMMMMMMMh-`/oooooooo:`
`-/+oo+/:`.yMMMMMMMh- -hMMMMMMMy.`:/+oo+/-`
`sMMMMMMMm: :dMMMMMMMs`
`hMMMMMMd/ /dMMMMMMh`
`://:` `://:`
root@pve:~# systemctl stop pve-cluster corosync
root@pve:~# pmxcfs -l
[main] notice: forcing local mode (although corosync.conf exists)
root@pve:~# tar -zcvf etc_corosync.tar.gz /etc/corosync/*
tar: Removing leading `/' from member names
/etc/corosync/authkey
tar: Removing leading `/' from hard link targets
/etc/corosync/corosync.conf
root@pve:~# rm /etc/corosync/*
root@pve:~# tar -zcvf corosync_conf.tar.gz /etc/pve/corosync.conf
tar: Removing leading `/' from member names
/etc/pve/corosync.conf
root@pve:~# rm /etc/pve/corosync.conf
root@pve:~# killall pmxcfs
root@pve:~# systemctl start pve-cluster
root@pve:~# pvecm status
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
root@pve:~#
Last edited:
Spoke too soon. While the cluster information is removed; when attempting to join the cluster, I get the following:
I attempted the following:
I'm stumped.
Code:
detected the following error(s):
* this host already contains virtual guests
TASK ERROR: Check if node may join a cluster failed!I attempted the following:
Code:
root@pve:~# pvecm nodes
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
root@pve:~# pvecm delnode pve
Cannot delete myself from cluster!I'm stumped.
Created acct just to reply here. I'm not OP but I had this work for me on 2 nodes that wouldn't communicate. Only thing is for the second node I needed to remove the folder /etc/pve/nodes/<NODE NAME> for it to remove from the Web UI, otherwise it looks good. I believe this has also worked for me in the past with these same 2 nodes.
**cough** what If someone deleted the /etc/pve/nodes/YYYY folder?
I did this and it took the proxmox server, effectively offline. The GUI will not load, cannot reach it via SSH (it is on the network). Looking at another unrelated server, the only files of importance appears to be the pve-ssk.key & PEM file.
I rebooted the box, no change. Will this constitute a reload of the OS? and a firm kick in the rear for myself?
I did this and it took the proxmox server, effectively offline. The GUI will not load, cannot reach it via SSH (it is on the network). Looking at another unrelated server, the only files of importance appears to be the pve-ssk.key & PEM file.
I rebooted the box, no change. Will this constitute a reload of the OS? and a firm kick in the rear for myself?
You probably need to restart the services you stopped during your attempt to delete the node info.
systemctl start pve-cluster.service
systemctl start pvestatd.service
systemctl start pvedaemon.service
I got that from here: https://forum.proxmox.com/threads/removing-deleting-a-created-cluster.18887/post-154254
Tested a matter of minutes ago. I caused the problem by killing those services through the web GUI rather than a local shell or SSH, perhaps. Restarting the services fixed the problem, no reboot needed.
systemctl start pve-cluster.service
systemctl start pvestatd.service
systemctl start pvedaemon.service
I got that from here: https://forum.proxmox.com/threads/removing-deleting-a-created-cluster.18887/post-154254
Tested a matter of minutes ago. I caused the problem by killing those services through the web GUI rather than a local shell or SSH, perhaps. Restarting the services fixed the problem, no reboot needed.