K1ngJony Posted February 20 Share Posted February 20 Hi Unraid community, I require some assistance with my server and would much appreciate your help. My Fix Common Problems plugin is reporting that my server is running out of memory and killing off processes to free some up. I've only had my Plex docker killed off so far, so nothing major, just more of an annoyance. I figured I should post here before it gets worse though. I've attached my diagnostics for your perusal. When I had a look, I was unable to find the culprit, though I suppose I don't really know what I'm looking for, so some guidance for next time as to where I should be looking would also be greatly appreciated. TIA. schirmer-nas-diagnostics-20240220-2309.zip Quote Link to comment
Solution JorgeB Posted February 20 Solution Share Posted February 20 If it's a one time thing you can ignore, if it keeps happening try limiting more the RAM for VMs and/or docker containers, the problem is usually not just about not enough RAM but more about fragmented RAM, alternatively a small swap file on disk might help, you can use the swapfile plugin: https://forums.unraid.net/topic/109342-plugin-swapfile-for-691/ 1 Quote Link to comment
Michael_P Posted February 20 Share Posted February 20 6 hours ago, K1ngJony said: so some guidance for next time as to where I should be looking would also be greatly appreciated Plex ran you OOM on the 17th - if it happens again, limit the memory to the container 1 Quote Link to comment
JorgeB Posted February 20 Share Posted February 20 10 minutes ago, Michael_P said: Plex ran you OOM on the 17th Correct me if I'm wrong but on the diags you can only see which process was killed, not which process caused the OOM, it can even be a combination of apps, the OOM usually invokes the app that is using more RAM, but it also depend on other factors: The function applies some heuristics (it gives each process a score) to decide which process to kill when the system is in such state. The process monopolizing the most memory and not releasing enough of it is more likely to be killed. Quote Link to comment
Michael_P Posted February 20 Share Posted February 20 11 minutes ago, JorgeB said: but on the diags you can only see which process was killed This is true, but as the reaper will usually kill whatever is using the most RAM at the time it's OOM, it's a pretty good candidate to start with. Plex should never reach that point, unless it bugs out, which makes it the prime suspect in this case It's easier to spot with multiple OOM events, if each time it kills the same process then you've added even more weight to the likely cause. 1 Quote Link to comment
K1ngJony Posted February 24 Author Share Posted February 24 Thanks @JorgeB and @Michael_P! Both answers very helpful. I thought it was possible to tell which process was chewing up the RAM, however I'll closely monitor it and limit the memory to the container if needed. Quote Link to comment
Recommended Posts
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.