Okay, just to give an update about the name and logo issue:
I've been in contact with your office and to avoid any interference with the trademarks which are the property of Proxmox Server Solutions, we decided to rename the community server to "ProxCord" and changed the logo too.
I just like to announce here that there is an unofficial Discord server.
There we talk about anything related to self-hosting, containers, virtual machines or even unsupported things like
running Proxmox in the cloud and it's related network issues
officially unsupported hardware...
I remember I did this with systemctl restart corosync.service, but it instantly failed again.
Unfortunately I cant get you any debug information anymore as I reinstalled last night and restored my backups after that. :-(
Currently there is just the docker LXC left to reinstall as i probably...
no, there is just one network link, but the NAS simply is currently switched off.
can this be a possible cause for my issue?
and in case it is, how can i switch this off? without quorum i also can't edit HA options :-(
even changing the corosync.conf to give one node 2 votes...
of course. Here you see the output from both nodes:
root@GANYMED:~# journalctl -u corosync.service -b0
-- Logs begin at Thu 2021-06-24 13:12:13 CEST, end at Mon 2021-06-28 11:56:15 CEST. --
Jun 24 13:13:45 GANYMED systemd: Starting Corosync Cluster Engine...
Jun 24 13:13:45...
last week I updated my PVE two node Cluster, but after rebooting since a while i ran into some problems:
Both nodes currently are online, but keep complaning that there is no quorum.
In the webui this looks like this :
Anyway from the webui of both nodes i get the actual...
Well, hopefully I just missed something :)
$ pvecm status
Config Version: 3
Secure auth: on
Date: Tue Jun 1 12:54:13 2021
I just checked the two files /etc/pve/corosync.conf and /etc/corosync/corosync.conf on both nodes again and they don't seem to be different, neither they have any mistakes (as I can see). All files are synced and the cluster has quorum again. So it seems to work, apart from the...
I'm recently having a two nodes Cluster of PVE in my home environment.
Caused by some accidents i needed to change the IP address of one node (the other one remained where it was on the IP-range)
What did i do?
On both nodes (while they still had quorum) i changed the corosync.conf...