is this Little Bobby Tables?
Just cron a restart
Turns out you already did that and that’s why it’s going down
I actually have an issue that is similar. My server goes unresponsive/freezes after N hours of uptime. N is a variable, so far meassured between 6 and 72 hours. I tried working around it, by auto-rebooting the server each night. But it still sometimes happen before the 24 hour mark.
Nothing in logs, so my best option is to auto-reboot at this time. 😆
I just solved this exact issue after living with it for a few months.
For me it was a bad PSU, voltage drop probably stopping the HDDs and SSDs, which knocked over the Kernel
One of these days I’ll get around to figuring out why Proxmox won’t start up unless I hit enter on the splash page.
There’s a silly bug where if you use Ventoy to install proxmox it fucks up the efi partition and won’t allow boot without the USB in, I left that USB in for probably 6 months before bothering to fix it lol.
Unintended safety feature
Won’t start if the key isn’t it.
Bro, that’s a car.
My latest example of this was a memory leak in some old software I wrote. It grew linearly with traffic, so it wasn’t until traffic randomly spiked that I started seeing problems.
To “fix” the memory leak, just restart your server every day with a cron job /s
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅





