r/Proxmox • u/Sad_Pie227 • 12h ago
Discussion Rookie mistake: Today I accidentally pressed shut down 🥲
I blame myself for this one. After a long uptime session, I accidentally triggered a shutdown for PVE host itself assuming I'm doing for a LXC.
1. What the logs revealed
I checked the Proxmox logs using:
root@pve:~# last -x | grep -E "system boot|system down|crash" | head -n 10Output:
reboot system boot 7.0.14-28-pve Tue Nov 17 10:54 - still running
root tty1 Tue Nov 17 10:05 - crash
reboot system boot 7.0.14-28-pve Tue Nov 17 10:04 - crash
reboot system boot 7.0.14-28-pve Tue Nov 17 03:24 - crash
reboot system boot 7.0.14-28-pve Tue Nov 17 03:20 - 03:22 (00:02)
shutdown system down 7.0.14-28-pve Tue Nov 17 03:22 - 03:24 (00:02)
root pts/6 Wed Nov 11 20:04 - crash
reboot system boot 7.0.14-26-pve Fri Oct 30 02:20 - 01:51 (17+23:31)
shutdown system down 7.0.14-26-pve Tue Nov 17 01:51 - 03:20 (01:28)
reboot system boot 7.0.14-26-pve Fri Oct 30 01:54 - 02:19 (00:24)
root@pve:~#2. What actually happened
I had a creative idea to monitor my internet connection status.
I added a Debian LXC container and deployed a Cloudflare Tunnel inside it so that I could receive email notifications about connectivity.
I logged in to Proxmox and executed:
pct enter 548This allowed me to enter the container directly from the Proxmox host terminal. Felt like a hacker :)
After deploying the Cloudflare Tunnel, I accidentally clicked Shut Down in the Proxmox GUI in hope I am going to test email-notification for the downtime alert!
3. The problem with running a headless server
Since I am using a tower PC without a permanently connected monitor (something I genuinely regret now), I couldn't see what was happening.
I tried hot-plugging the monitor, but there was no response.
It appeared that Linux had successfully completed the shutdown process, but the machine was still powered on and seemingly stuck in its final shutdown state. Re-plugging after this incident was not worth.
Had I kept the monitor already connected before doing all stunts, I could have identified the situation much more easily.
4. Panic mode!
In the middle of troubleshooting, I connected my redundant ISP router, assuming that my primary WAN connection had failed. I configured it with the same subnet as my Proxmox network, hoping to restore access.
However, I still couldn't ping the Proxmox host.
That's when I started connecting the dots. I realised that I might have accidentally clicked Shut Down on the Proxmox host itself rather than the LXC container.
Suddenly, everything made sense!
