One of our VPS close every saturday morning at 5 am

[alinail]

Our log is
Apr 06 05:16:15 vps kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=qemu.slice,mems_allowed=0-1,global_oom,task_memcg=/qemu.slice/108.scope,task=kvm,pid=2082695,uid=0
Apr 06 05:16:15 vps kernel: Out of memory: Killed process 2082695 (kvm) total-vm:69706600kB, anon-rss:60364772kB, file-rss:0kB, shmem-rss:4kB, UID:0 pgtables:123548kB oom_score_adj:0
Apr 06 05:16:15 vps systemd[1]: 108.scope: A process of this unit has been killed by the OOM killer.
Apr 06 05:16:18 vps kernel: oom_reaper: reaped process 2082695 (kvm), now anon-rss:0kB, file-rss:172kB, shmem-rss:4kB
Apr 06 05:16:18 vps kernel: vmbr0: port 6(tap108i0) entered disabled state
Apr 06 05:16:18 vps kernel: vmbr0: port 6(tap108i0) entered disabled state
Apr 06 05:16:18 vps pve-firewall[1369]: firewall update time (8.387 seconds)
Apr 06 05:16:18 vps systemd[1]: 108.scope: Succeeded.
Apr 06 05:16:18 vps systemd[1]: 108.scope: Consumed 5d 20h 17min 12.429s CPU time.
Apr 06 05:16:18 vps pvestatd[1368]: status update time (10.766 seconds)
Apr 06 05:16:19 vps qmeventd[4030877]: Starting cleanup for 108
Apr 06 05:16:19 vps qmeventd[4030877]: Finished cleanup for 108
Apr 06 05:17:01 vps CRON[4031303]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 06 05:17:01 vps CRON[4031304]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

 

[leesteken]

Apr 06 05:16:15 vps kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=qemu.slice,mems_allowed=0-1,global_oom,task_memcg=/qemu.slice/108.scope,task=kvm,pid=2082695,uid=0
Apr 06 05:16:15 vps kernel: Out of memory: Killed process 2082695 (kvm) total-vm:69706600kB, anon-rss:60364772kB, file-rss:0kB, shmem-rss:4kB, UID:0 pgtables:123548kB oom_score_adj:0

Looks like you are over-committing on memory, which is often problematic as you can see from these threads on this forum: https://forum.proxmox.com/search/6903124/?q=oom-kill&t=post&c[child_nodes]=1&c[nodes][0]=16&o=date

 

[Sumasarct]

That sounds frustrating. If it’s happening every Saturday at the same time, it could be something scheduled on your VPS. Maybe there's a weekly maintenance task or an automated script running? It might be worth checking with your hosting provider to see if they can shed some light on it.
I’ve heard good things about offshore SSD VPS from blueangel.host if you're looking for alternatives. They’re known for reliability and might offer a setup that better suits your needs.

 

[UdoB]

Maybe there's a weekly maintenance task or an automated script running?

You may search for it in /etc/cron.hourly/*, /etc/cron.d/* and some more for daily/weekly/yearly.

Additionally there is systemctl list-timers and systemctl --user list-timers

Good luck

 

[andaga]

This is WIndows VM? If yes the Windows is activated? Because if not the widnows auto-shutdown!