pdxltd
Member OP
WireGuard tunnel died mid-kernel update
Now I can't reach the box
Lesson learned the hard way
Always test before you reboot
Tunnel broke during a kernel update, learned my lesson
MARIA3
Member
I make a server up with WireGuard on RackNerd, then I do upgrade kernel and tunnel broke. Is not coming back. I learn hard way, now I have the staging server. Regards 😊
siesta first, deploy later
Server good before upgrade, after is broken. How much cost the downtime? The WireGuard module not rebuild automatic. ¿why not¡ I use now dkms but is manual. The kernel headers missing sometimes.
GuruDeutschlag
Member
MARIA3 said:
I learn hard way, now I have the staging server
I have learned this Lesson the hard way also. My upgrade Ritual now:
- Snapshot the Virtual machine
- Build the KernelModule in staging
- Reboot with fallback Kernel
- Test the Tunnel connectivity
Yes the virtualization tax strikes again when modules break no I do not trust automatic rebuilds anymore. KernelHeaders must match exactly or the compoundmodulefails.
kate3
Member
Virtualization tax includes module rebuild fragility. OpenVZ avoids this by using host kernel, but then you pay the tax in other ways. For KVM, always pin headers and keep a known-good kernel in bootloader. I maintain a pre-upgrade checklist: lsmod | grep wireguard, modprobe dry-run, then staged reboot. Cgroup limits won't save you from a missing ko file.
virsh list --all | wc -l: 47
Which kernel version broke it?
RAID 1: because paranoia pays