Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

OOM error

Featured Replies

Hi,

 

I need your assistance again... My server has been acting up the last couple of days. Basically, the last two days, I've received (~20 minutes past midnight) a cache disk hot warning. And the cache disk does not return to normal temperature until ~04:20. And today, it resulted in a OOM

Feb 10 04:08:41 Tower kernel: docker-proxy invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
...
Feb 10 04:08:41 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/machine/qemu-1-Ubuntu-server.libvirt-qemu,task=qemu-system-x86,pid=13066,uid=0
Feb 10 04:08:41 Tower kernel: Out of memory: Killed process 13066 (qemu-system-x86) total-vm:11195768kB, anon-rss:10685708kB, file-rss:0kB, shmem-rss:6544kB, UID:0 pgtables:21844kB oom_score_adj:0

Looking into the docker log, there are also a vast number of errors in this time span, but I can't figure out what is triggering this. Diagnostics attached.

 

EDIT: Just noticed my VM was stopped which I did not expect. Not sure if related.

EDIT2:

Time of VM crash corresponds to OOM time (-1 hour offset), from VM log:

2025-02-10 03:08:42.405+0000: shutting down, reason=crashed

 

TIA,

Jorgensen

 

 

 

tower-diagnostics-20250210-0930.zip

Edited by Jorgensen

Solved by Michael_P

  • Community Expert
  • Solution
2 hours ago, Jorgensen said:

ust noticed my VM was stopped which I did not expect. Not sure if related.

 

When the host ran OOM, it killed your VM because it was the largest consumer at the time. If your VM is set up properly and leaving enough RAM for the rest of the system, I'd say it was probably immich that ran it OOM.

 

Reboot the system to clear the log, if it happens again in the future, limit the RAM available to the container

  • Author

I left the VM off, and I've not had any issues since. Both the docker log and the syslog are clean. So, not related to Unraid, but to my VM.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.