RhinoMedia Posted December 31, 2023 Share Posted December 31, 2023 As noted under more information for this issue I have captured diagnostics prior to rebooting. If you can assist me with figuring out the issue that would be fantastic? rhino9094-diagnostics-20231231-0815.zip Quote Link to comment
JorgeB Posted December 31, 2023 Share Posted December 31, 2023 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
RhinoMedia Posted December 31, 2023 Author Share Posted December 31, 2023 Thanks. so far this is the first time I've ever gotten this error so hopefully it's just an anomally. I may still adda dn start using the swapfile plugin though. That seems like a very useful idea. Quote Link to comment
poloconway Posted January 2 Share Posted January 2 Was having problems with server freezing and finally after days of looking and watch videos I found a post and I added /dev/dri to docker configuration and that seems so far that has keep it from freezing, but I got an error message about memory. conwayserver-diagnostics-20240102-0939.zip Quote Link to comment
RhinoMedia Posted January 7 Author Share Posted January 7 So I woke up this morning to the same error. The one thing I noticed that was the same this time and last time was this Note hoow ZFS is at 100%. The only drives I have as ZFS right now are my cache drives. Rebooting resolved this last weekend. I haven't done the swap file thing yet. Getting ready to reboot again for now. rhino9094-diagnostics-20240107-0837.zip Quote Link to comment
itimpi Posted January 7 Share Posted January 7 The ZFS (ARC) is expected to be at or close to 100% in use. 1 Quote Link to comment
Michael_P Posted January 7 Share Posted January 7 1 hour ago, RhinoMedia said: So I woke up this morning to the same error What time is your Plex maintenance scheduled? Try limiting the Plex docker's memory, that will keep it from running away if it encounters a file it doesn't like. Quote Link to comment
RhinoMedia Posted January 7 Author Share Posted January 7 Plex takss are scheduled for 0200 Quote Link to comment
RhinoMedia Posted January 14 Author Share Posted January 14 Third week is the charm. Same error as usual along with a new one: /var/log is getting full (currently 79 % used) which I just posted about in the FCP forum per the note in the error message. This weeks diags are attached. Whatever is causing this (these) issue hasn't otherwise affected the day to day use of my server thus far. So I'm not freaking out about it. But I would like to figure it out before it becomes a bigger issue. rhino9094-diagnostics-20240114-0605.zip Quote Link to comment
JorgeB Posted January 14 Share Posted January 14 You are still having OOM events, but it appears there's something else filling up the logs, post the output of: du -h /var/log Quote Link to comment
Michael_P Posted January 14 Share Posted January 14 1 hour ago, RhinoMedia said: Third week is the charm. Same error as usual Did you try limiting Plex's memory in the container settings? Dec 26 03:48:48 rhino9094 kernel: Out of memory: Killed process 98495 (Plex Media Scan) total-vm:86323272kB, anon-rss:86231128kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:168936kB oom_score_adj:0 Jan 3 04:18:33 rhino9094 kernel: Out of memory: Killed process 61237 (Plex Media Scan) total-vm:87662668kB, anon-rss:86525528kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:169516kB oom_score_adj:0 Jan 10 05:09:01 rhino9094 kernel: Out of memory: Killed process 129575 (Plex Media Scan) total-vm:88265484kB, anon-rss:87135964kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:170712kB oom_score_adj:0 Quote Link to comment
RhinoMedia Posted January 14 Author Share Posted January 14 6 hours ago, JorgeB said: You are still having OOM events, but it appears there's something else filling up the logs, post the output of: du -h /var/log This what I get when I enter that: 0 /var/log/pwfail 8.0K /var/log/unraid-api 0 /var/log/swtpm/libvirt/qemu 0 /var/log/swtpm/libvirt 0 /var/log/swtpm 0 /var/log/samba/cores/rpcd_lsad 0 /var/log/samba/cores/samba-dcerpcd 0 /var/log/samba/cores/winbindd 0 /var/log/samba/cores/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 48K /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools/removed_scripts 0 /var/log/pkgtools/removed_packages 0 /var/log/pkgtools 4.0K /var/log/nginx 0 /var/log/nfsd 8.0K /var/log/libvirt/qemu 0 /var/log/libvirt/ch 12K /var/log/libvirt 480K /var/log Quote Link to comment
RhinoMedia Posted January 14 Author Share Posted January 14 5 hours ago, Michael_P said: Did you try limiting Plex's memory in the container settings? Dec 26 03:48:48 rhino9094 kernel: Out of memory: Killed process 98495 (Plex Media Scan) total-vm:86323272kB, anon-rss:86231128kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:168936kB oom_score_adj:0 Jan 3 04:18:33 rhino9094 kernel: Out of memory: Killed process 61237 (Plex Media Scan) total-vm:87662668kB, anon-rss:86525528kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:169516kB oom_score_adj:0 Jan 10 05:09:01 rhino9094 kernel: Out of memory: Killed process 129575 (Plex Media Scan) total-vm:88265484kB, anon-rss:87135964kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:170712kB oom_score_adj:0 Honestly I got busy with other things and forgot about this. Additionally, I'm not quite sure how I go about limiting Plex's memory in the container settings. Quote Link to comment
Michael_P Posted January 15 Share Posted January 15 16 hours ago, RhinoMedia said: Honestly I got busy with other things and forgot about this. Additionally, I'm not quite sure how I go about limiting Plex's memory in the container settings. In the container's settings, toggle advanced view and add this into the extra parameters field (whatever amount of RAM you want to limit to, I just use 4G 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.