Ah das klingt potenziel, nach einem defekten initramfs.
Du könntest versuchen es neu zu installieren.
Dazu:
# kannst du dir die apt pakete mit den entsprechenden Kerneln auflisten lassen.
apt search proxmox-kernel
# die kannst du dann...
I would read the “Supported Setups” section related to qdevices on this wiki post very carefully if I was you: https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support
Yes the odds of enough nodes failing to even need the...
Nodes failing isnt the issue. the quorum device is meant as defense against a silo connectivity "tie". Anything short of a room losing connectivity would be handled normally without it.
My own largest cluster has 10 nodes. I can lose four nodes and still have 6 votes.
Does it really make sense to add a QDev with such a high number of nodes? With 11 votes I could lose five nodes instead of the mentioned four. But..., really, I...
I see a problem here and thus i usually discourage from changing the vote strength of devices. Because the setup is inhomogeneous
and thus unpredictable. Exactly for the reason you showed.
Das ist aber nicht die Bedeutung von immutable :) Immutable heisst nicht veränderbar.
Das geht schon. PVE einfach nur Backup Rechte einräumen und sonst nix.
Oder S3 bucked mit lifecycle oder versioning versehen, dass vom API user nicht angefasst...
Das ist aber nicht die Bedeutung von immutable :) Immutable heisst nicht veränderbar.
Das geht schon. PVE einfach nur Backup Rechte einräumen und sonst nix.
Oder S3 bucked mit lifecycle oder versioning versehen, dass vom API user nicht angefasst...
Thanks, i know there are workarounds like scp and download using the url etc, but my issue was that a feature was not working as it should. Turns out it was an issue on my end... I was accessing the proxmox web ui via a cloudflare tunnel, which...
Das war des Rätsels Lösung, vielen Dank!
Ich habe die CPU auf x86-64-v3 geändert (v4 gäbs auch noch, ist das relevant?) und schon lief es! Datenbankzugriffszeiten wurden von ca. 30ms auf 0,3ms verringert.
@cwt : Meine Wochenrettung! Dankeschön...
@Charrat , I seem to remember that in similar cases, harmful repositories occurred to be added by these khe-khe-...helper scripts.
So just in case, check what is below /etc/apt/
This file is often altered by post-install- or nag screen scripts. These tools are NOT official are you sure you didn't use one of these? Issues caused by inofficial scripts should be filed at the developer of that scripts.
Personally I avoid...
Did you check journalctl log on the affected hosts during the observed issue time? maybe the connection to the nfs have some problem.
Also you could verify the storage status during the issue time with ~# pvesm status
Maybe also try setting...
Hello,
Coming back to my original post. I have no patching of my clusters. Neither anything special installed. The only thing is the proxmox-widget-toolkit, which -correct me if I am wrong - is an official proxmox tool.
Therefore I think tha case...
Like i have one cluster with the 4 nodes this nodes are in the subnet 192.168.180.0/24 and having the SAN in that created nfs which is in the same subnet
which is working fine and not even single machine is stucked and backup is also working...