VXLAN is a layer2 network and as such does not provide any routing functionality - the gateway setting has no effect. You'd need to add a second network device for connecting to the internet or add a gateway VM/CT to the VXLAN that has internet...
Our firewall has not changed at all. I simply replaced the old mail-gateway by the new one (same ip). And almost all mailservers have no problem communicating with pmg except a few...
fsck is a file system check - so this only works on partitions formatted with a file-system. Hence: fiona has already told you that running fsck on sda drive is irrelevant as sda just contains partitions. Even running it on sdaX is irrelevant in...
So still the same physical network? Yes, the timeout for checking the mount directory is 2 seconds. Telling from the error message, this is the command that fails for you and since you see the issue sporadically/randomly it might be related to...
Hi @philkunz , got a few questions on your shutdown tool.
We have 2 nodes with 2 UPSes (SNMP enabled), so I can see you can add multiple UPS to a single node.
1) how does it handle multiple UPSes? I can see each UPS device looks to have a...
The existing reply is correct, but I think what's missing is a concrete example of how to actually make it work.
Your VXLAN network itself is already working correctly (VM ↔ VM across nodes), so the missing part is just how to connect your...
The important point is that in a VXLAN zone, the gateway field in the subnet settings does not automatically create a real router for that network.
It only defines addressing information for the subnet.
It does not make Proxmox spawn a gateway...
I added the information on the kernel with this line :
GRUB_CMDLINE_LINUX_DEFAULT="quiet idle=nomwait processor.max_cstate=1"
And for me it works, I was able to see this line on the logs with no error.
But if the reboots occured with Windows, I...
You either need to configure a VXLAN IF on that external device as well and add it to the peer list in SDN - or route between the physical network and the VXLAN network.
There are multiple symbolic links pointing to the same device. My example shows that in detail: https://forum.proxmox.com/threads/fabu-how-to-select-the-correct-disk-or-what%E2%80%99s-in-a-device-name.182741/
Auf einem der Cluster-Nodes beobachte ich folgendes im Log:
Apr 14 10:12:46 proxmox3 dbus-daemon[3026]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.457'...
The different names for disks may lead to confusion. I show some different names to specify the "right" device.
Why is this important? Well..., the obvious thing is that “zpool create” will destroy the old content. You will lose any data stored...
Since it appears that the Current_Pending_Sector has not risen (19) since May 2025, & assuming this is a server that the drive is in constant use, it is possible that the drive is still "usable" or may even be perfectly alright. However this is...
There are multiple symbolic links pointing to the same device. My example shows that in detail: https://forum.proxmox.com/threads/fabu-how-to-select-the-correct-disk-or-what%E2%80%99s-in-a-device-name.182741/
The different names for disks may lead to confusion. I show some different names to specify the "right" device.
Why is this important? Well..., the obvious thing is that “zpool create” will destroy the old content. You will lose any data stored...
Hello.
I'm now experiencing freezes which started three days ago and happens every day but in random time. Hardware is Hetzner Server
Symptoms: Proxmox interface shows high IO delay, about 30-50%, while no significant IO operations are happening...