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.

Out of Memory killing VM

Featured Replies

Im having persistent issues with Out of Memory issues killing my VM and occasionally a docker container. Fix common problems suggested I ask for additional help here, as I am running out of ideas.

Its a 32gb system with only one VM (12gb given) and only 17 running docker processes, only a few even occasionally do much.

I have seen some post about '-m 4GB' in extra parameters as one thing to try and another messing with hugepages, but I am unsure on either. I could maybe also reduce the VM down from 12gb to 8gb, I dont think it would be a problem its just running HAOS with a handful of addons

tower-diagnostics-20260422-1303.zip

  • Community Expert
1 hour ago, apsmith12 said:

its just running HAOS with a handful of addons

That should not need more than 2-4GB.

Can install something like Beszel to log container memory usage for a day or 2 and look at what the usage is like.

  • Community Expert
13 hours ago, apsmith12 said:

Im having persistent issues with Out of Memory issues killing my VM and occasionally a docker container. Fix common problems suggested I ask for additional help here, as I am running out of ideas.

Its a 32gb system with only one VM (12gb given) and only 17 running docker processes, only a few even occasionally do much.

I have seen some post about '-m 4GB' in extra parameters as one thing to try and another messing with hugepages, but I am unsure on either. I could maybe also reduce the VM down from 12gb to 8gb, I dont think it would be a problem its just running HAOS with a handful of addons

tower-diagnostics-20260422-1303.zip

If I had to guess based on the processes running at the time, I'd say it was immich. Dump the result of ps -auxf to a file and post it, taking care to remove any passwords if they are included in your container's startup commands

ps -auxf > ps.txt
  • Author
10 hours ago, Michael_P said:

If I had to guess based on the processes running at the time, I'd say it was immich. Dump the result of ps -auxf to a file and post it, taking care to remove any passwords if they are included in your container's startup commands

ps -auxf > ps.txt

Ill do that, but I dont have immich.

  • Author
21 hours ago, Kilrah said:

That should not need more than 2-4GB.

Can install something like Beszel to log container memory usage for a day or 2 and look at what the usage is like.

Yeah HAOS say its usling 3GB most of the time, unraid says the VM is at 7ish.

  • Community Expert
2 hours ago, apsmith12 said:

Yeah HAOS say its usling 3GB most of the time, unraid says the VM is at 7ish.

VMs will use almost everything you give them for caching that's usually pointless, so you don't want to give more than necessary.

Edited by Kilrah

  • Community Expert
13 hours ago, apsmith12 said:

Ill do that, but I dont have immich.

Ok, you can use it to find out what's spawning the gunicorn and ruby processes, and either limit the RAM to that container or reduce your VM's allocation. Since the reaper is killing the VM each time (it's the largest consumer at the time the host starts to OOM), that would indicate that you just don't have enough RAM to run everything, so you can either add more (in this economy!?!) or reconfigure your services.

Once you've done all that, you can re-boot to clear the log so FCP stops warning you

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.