Cluster Fuckery

[LittleFinger]

The guide I was following (https://pve.proxmox.com/wiki/Cluster_Manager), seems to be out of date for PVE v8.4.5 - "pmxcfs -1" does not work.

Trying to edit the corosync.conf file results in me getting told off - saying it can't be edited.
UPDATE: Editing /etc/corosync/corosync.conf works, but changes haven't propagated.

Reinstall is not an option, unless some gifted soul is willing to take the time to guide me. Would need to be scheduled.

What files do I need to modify in order to get my server to function again, aside from corosync.conf?

=====
A ton of my issues could've been avoided if Proxmox would make it easier to change the IP address when moving a server from one network to another, and having the IP address get corrected through other random files that it gets written to before issuing a self-signed certificate. I have access to the terminal via IPMI.

I'm home till noon on the 29th and will be back in three weeks.. unless I get overtime

=====
ERROR MESSAGES in log pane:

When trying to load the browser based shell in Proxmox

failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5901 --path /nodes/<nodename> --perm Sys.Console -- /bin/login -f root' failed: exit code 1

Bulk start VMs and Containters

waiting for quorum ...
TASK ERROR: received interrupt

 

[spirit]

when you edit /etc/pve/corosync.conf (in normal conditition, when you have quorum and write access to /etc/pve), the file is copied locally to each node in /etc/corosync/corosync.conf , then corosync is restarted.

if you have done change ip or hostname change, and you don't have access to /etc/pve (you should use multiple ring to avoid problem on ip change) , you can still edit /etc/corosync/corosync.conf , push it manually on all node, restart corosync on everynode.

Then copy /etc/corosync/corosync.conf to /etc/pve/corosync.conf to get them sync for the future.

 

[LittleFinger]

This is not under normal conditions I think, at least going by how everything has gone so far. My main node never had the right IP address in the hash (no idea why), the one I wanted to add had the old IP address, and then I tried to manually get rid of the clustering, and now I'm not sure what to do to get it to function properly.

What would happen if I deleted the ring0 config bits in the corosync.conf file?

At this point, I'm going to have to backup the containers and VMs I have on one node, then reinstall PVE on my main node. Oi.. but, that would at least remove the last option as far as solutions go.

I might actually need to hire Promox to fix this thing. *shrug*

 

[Neobin]

The guide I was following (https://pve.proxmox.com/wiki/Cluster_Manager), seems to be out of date for PVE v8.4.5 - "pmxcfs -1" does not work.

It is: -l (lowercase L), not: -1 (number one).

-l, --local
Force local mode (ignore corosync.conf, force quorum)

https://pve.proxmox.com/pve-docs/pmxcfs.8.html

 

[LittleFinger]

New path forward - https://forum.proxmox.com/threads/pve-8-4-12-data-hunt-for-recovery.170663/