Nath2125 Posted May 1, 2022 Share Posted May 1, 2022 mediaserver-diagnostics-20220501-1159.zip Hi there, This morning I woke up to a lovely message "Out of Memory errors detected on your server" "Your server has run out of memory, and processes (potentially required) are being killed off." I have posted in here the diagnostics to see if someone can read and tell me what happened or what the issue could be. Is it a simple thing that i need more ram? or that i was running to many things that required ram at one time? Any assistance will be greatly appricated Thanks, disk.cfg docker.cfg domain.cfg flash.cfg go.txt ident.cfg network.cfg c---e.cfg share.cfg super.dat docker.txt libvirt.txt syslog.1.txt syslog.2.txt syslog.txt disk.cfg docker.cfg domain.cfg flash.cfg go.txt ident.cfg network.cfg c---e.cfg share.cfg super.dat docker.txt libvirt.txt syslog.1.txt syslog.2.txt syslog.txt mediaserver-diagnostics-20220501-1159.zip Quote Link to comment
Nath2125 Posted May 8, 2022 Author Share Posted May 8, 2022 I has happened again today and i havent heard from a responce from anyone? Unsure what to do if i could get some help maybe figuring this out Quote Link to comment
Nath2125 Posted May 8, 2022 Author Share Posted May 8, 2022 I has happened again today and i havent heard from a responce from anyone? Unsure what to do if i could get some help maybe figuring this out mediaserver-diagnostics-20220508-1743.zip Quote Link to comment
JorgeB Posted May 9, 2022 Share Posted May 9, 2022 You don't have VMs so it's likely container related, you can try running with just some or leave one disable at a time to see if you can find the culprit. Quote Link to comment
Nath2125 Posted May 15, 2022 Author Share Posted May 15, 2022 (edited) still cant find the culprit and its just happened again. This will be the 3rd or 4th time now mediaserver-diagnostics-20220515-1257.zip Edited May 15, 2022 by Nath2125 Quote Link to comment
Frank1940 Posted May 15, 2022 Share Posted May 15, 2022 (edited) One possible cause would be if one (or more) of your dockers are writing files to the RAM disk where Unraid is installed. (Unraid is installed from scratch to that RAM disk every time you reboot the system!) This is usually caused by a typo in a container path that you added. One thing to remember is that all physical devices in Unraid should be found under the /mnt path. Now for the word of caution: A path that begins with /mnt/user0/ will be on a physical device. One that begins /mnt/User0/ will be in RAM. The capital 'U' is the reason for this: Linux is case sensitive! You can also make capitalization mistakes in a User Share name, so check carefully! Edited May 15, 2022 by Frank1940 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.