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.

[solved] Error: Out Of Memory errors detected on your server

Featured Replies

Fix Common Problems recommended I post my log to the forums.

 

I've had this server running for about a year now, never got over 50% memory usage. Occasionally CPU usage got up towards 100% but only ever in spikes.

 

Today I've had an alert twice to say my qbittorrent is down.. once when I woke up. I couldn't access the docker image (didn't think to check any others) and after unraid took too long to load the docker page to restart the docker I just hit restart on the server. Now tonight I've noticed qbittorrent webui wasn't loadable - had a look inside unraid to see CPU and RAM usage at 100%.

 

I fixed this by stopping all of my docker containers and starting them one by one, leaving the uneccessary ones not running. Seems to be running normally again. Any ideas what caused this?

 

I'm running unraid Version: 6.8.3

 

 

tower-diagnostics-20200729-1847.zip

Edited by tuna83

2 hours ago, tuna83 said:

Fix Common Problems recommended I post my log to the forums.

I've had this server running for about a year now, never got over 50% memory usage. Occasionally CPU usage got up towards 100% but only ever in spikes.

A "dotnet" process was killed due to OOM which I think is used by qbittorrent.

Could be memory leak or could just be naturally out of memory error as you only have 8GB of RAM.

 

You can try restricting memory usage of some dockers (edit the docker, Advanced View and use --memory=# parameter in Extra Parameters box e.g. --memory=1G to limit memory usage to 1G) and see if it improves things.

  • Author
12 hours ago, testdasi said:

A "dotnet" process was killed due to OOM which I think is used by qbittorrent.

Could be memory leak or could just be naturally out of memory error as you only have 8GB of RAM.

 

You can try restricting memory usage of some dockers (edit the docker, Advanced View and use --memory=# parameter in Extra Parameters box e.g. --memory=1G to limit memory usage to 1G) and see if it improves things.

Thanks for the reply. I've limited the memory usage to 3g just to stop it if there's a memory leak. It felt somewhat like a memory leak. It seems odd that I would go from 50% average utilisation to 100% with no significant changes from one day to the next.

 

I guess if it stops happening after this then I'll look at swapping to rutorrent or something. Cheers for the help.

  • Author

Managed to catch Jellyfin being the memory hog right before it ate up the rest of my ram and I had to restart the server. One of the docker images indeed appears to have a memory leak

 

https://github.com/jellyfin/jellyfin/issues/3680

 

I've limited its avaliable ram and it's not happy about it at all. Thanks for your help testdasi, I'm marking this solved.

Archived

This topic is now archived and is closed to further replies.

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.