IMPORTANT
A forced host power-off can corrupt:
- K3s SQLite/etcd datastore
- containerd layers
- VM filesystems
-> Cleanly shutting down the VMs prevents this.
-> Ensure the K3s cluster shuts down cleanly before the provider powers off the physical Proxmox host.
Set Crontjobs
Important
ordering is importat: shutdown workers first!
Worker
❯ ssh -l root myloc-mh
Linux MH-19003Y 6.8.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Nov 17 16:08:41 2025 from 79.254.115.222
root@MH-19003Y:~# crontab -e
crontab: installing new crontab
root@MH-19003Y:~# crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
25 3 19 11 * /usr/sbin/qm shutdown 102Master
root@MH-19003Y:~#
⎈ myloc prebid
❯ ssh myloc-pve -l root
Linux pve 6.8.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-2 (2024-04-10T17:36Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Nov 17 16:05:19 2025 from 79.254.115.222
root@pve:~# crontab -e
crontab: installing new crontab
root@pve:~# crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
30 3 19 11 * /usr/sbin/qm shutdown 100
root@pve:~#
Debriefing after Host Restart
-> on Proxmox Host:
journalctl -u cron --since "2025-11-19 03:20" --until "2025-11-19 03:30"
journalctl --since "2025-11-19 03:20" --until "2025-11-19 03:30" | grep -i "qm shutdown 102"
pvesh get /nodes/MH-19003Y/tasks --limit 300 | grep -i qmshutdown | grep -i 102
journalctl --since "2025-11-19 03:24" --until "2025-11-19 03:27" | grep -Ei "qm|102"
last -x | grep shutdown