November 9, 20232 yr Hello, I recently upgraded my server and its been running pretty smoothly for about a month however all of sudden It keeps crashing for some reason. From what I have noticed it mostly happens after Sonarr/Radarr starts an import. It doesn't happen every time mostly at random, could be a single file or 100 it just decides at one point to freeze up. After a reboot it won't happen again for a day or two or more then it will happen again. I tried taking a look at the syslog but it doesn't seem to indicate any issues. any idea's? syslog-192.168.2.36.log marge-diagnostics-20231109-1753.zip
November 10, 20232 yr Community Expert Solution Server is running out of RAM, 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/
November 10, 20232 yr Author Thank you Jorge! I suspected it was something along those lines since whenever the server crashed and I had the dashboard page open, the ram would always be unusually high. Not max but it would freeze the page with the RAM at over 80%. If I may ask a few follow up questions for my own curiosity 1. What line in the logs pointed towards RAM? I would like to get better at understanding this information to better diagnose things myslef 2. Can you go more into detail about Fragmented Ram? I kinda understand what you mean but is there any way to avoid this? Again thank you for your time and help, greatly apreaciated and why I love unraid and the community! Edited November 10, 20232 yr by Milzy
November 10, 20232 yr Community Expert 2 minutes ago, Milzy said: 1. What line in the logs pointed towards RAM? I would like to get better at understanding this information to better diagnose things myslef E.g.: Nov 9 16:33:30 Marge kernel: unpackerr invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 Anytime you see "something invoked oom-killer" means a process as killed to try and free up some RAM. 3 minutes ago, Milzy said: 2. Can you go more into detail about Fragmented Ram? I kinda understand what you mean but is there any way to avoid this? Not much you can do to avoid that, it's a Linux thing, just important to understand that you can run out of RAM before all the RAM is showing as used.
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.