Search results

I didn't get a chance yet to trigger this on my box (accidentally moved a VM to the server that I can't reboot until the weekend, sorry!), however, I noticed that at least in my case, this doesn't seem to be I/O related: - I accidentally managed to move a VM (2TB of data) to the server, no...

Apologies for the slow reply here. In my case, originally I was installing Proxmox on top of Debian 10, and the fix was just to add the "nf_conntrack_allow_invalid: 1" in the host.fw for each node - I didn't have to do anything other than that. What I did then do is re-install all my Proxmox...

I configured all my Proxmox boxes with remote syslog now - I can't cause the problem right now since it's during the day, but this evening I will run a scrub, create the issue and then share the logs. If there are any other useful pieces of data to capture at the same time, just let me know.

I also hit this today, and it seems to be triggered (and re-triggerable) by running a zpool scrub (of course, that could just be triggering another issue, but I can consistently trigger exactly this behaviour just by running a zpool scrub). Interestingly, this only happens on one of my four...

I actually just hit this exact issue today as well, on a cluster of 3 servers hosted in Hetzner, accessed/managed via a Hetzner vSwitch. Enabling the firewall (even with ACCEPT/ACCEPT at the Datacenter level) resulted in losing connectivity to all VMs and management via other (non-local)...