Search results

then I think I know the issue - the "fingerprint" option (currently) expects the server to return a single certificate and the fingerprint to match that. your server returns more than one certificate - did you maybe put the full chain instead of just the certificate into the file?

the path is /sdn/zones/<zone>/<vnet>/<vlan>

HA will only take the HA settings (including scheduler) into consideration, it doesn't know or care about replication. for "real" HA you need a shared storage, but even then, you need to restrict your HA resources if that storage is not available everywhere. the same is true for "pauper's" HA...

https://forum.proxmox.com/threads/minisforum-nab9.176741/ (first hit ;)) and for other vendors: https://forum.proxmox.com/threads/vm-freezes-irregularly.111494 but even if your hardware would be server grade - the symptoms clearly point at this particular piece of hardware having an issue!

well, it reads a lot but doesn't need to write a lot, since most of what it reads can be re-used without uploading (==writing), so that is totally normal and expected in this case :)

those numbers seem fine? note that the bitmap was cleared, so the backup had to read the full disk contents (and did so at roughly 400MB/s!)

https://github.com/acmesh-official/acme.sh/commit/fca6e9b9329c41678cb1c74405d8f6281852b65f seems we'd need our helper with that commit..

please file a bug in our bug tracker: https://bugzilla.proxmox.com

a mini PC is most definitely not fitting the definition of "high quality server hardware"! our forum and bug tracker, where we see endless threads with hardware like this that simply doesn't run stable (or only with a lot of tweaking). your initial post is about as clear-cut of an example of...

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_system_requirements

if the node is supposed to (logically) stay in the original cluster, please be aware of the requirements regarding network stability and latency! other than that, yes, a hook script is the way to go for this at the moment. you might consider taking a look at Proxmox Datacenter Manager and SDN...

that kind of hardware is known to not be very stable, and likely that is the source of your issues. use proper server grade hardware if you want proper server grade performance and stability.

if your HA affinity rule was disabled, you didn't tell PVE that the CT can only run on those three nodes, so it assumed doing failover to node mini1 is okay..

oh, I missed that, strange because "lvs" says its writable and active (or has that changed?). could you check the boot journal up to multi-user.target being reached and post it here? "journalctl -b"

um den export mounten zu koennen braucht PVE diese daten im klartext. um das risiko zu minimieren sind sie nur fuer root lesbar.

no, but the bug will be updated once patches are available

something is tripping up the multi mount protection: https://docs.kernel.org/next/filesystems/ext4/mmp.html do you have any custom setup that might interfere? changed hostname? time jumps? ...

du solltes mittels "pvecm updatecerts -f" ein neuerstellen des self-signed zertifikats durchfuehren koennen. dann eventuell noch "systemctl restart pveproxy". ansonsten bitte in den logs nach fehler ausschau halten und hier posten, z.b. "systemctl status pveproxy"

could you do the following? run "journalctl -f" in one shell, and then run "pct start 101 -debug" in another and paste the journal that is generated? "lvs", "findmnt" and "pvesm status" would also be interesting

does the problem go away if you reboot the node?