March 3, 20251 yr After updating to 7.0.1 it appears this error. I have 64GB of RAM with no VMs and few dockers, can't imagine what would the cause be... zotarios-diagnostics-20250303-1334.zip
March 3, 20251 yr Community Expert 8 minutes ago, Zotarios said: After updating to 7.0.1 it appears this error. I have 64GB of RAM with no VMs and few dockers, can't imagine what would the cause be... zotarios-diagnostics-20250303-1334.zip 242.76 kB · 0 downloads Looks like you have Plex transcoding to RAM, and multiple streams are running your system OOm
March 3, 20251 yr Author 1 hour ago, Michael_P said: Looks like you have Plex transcoding to RAM, and multiple streams are running your system OOm I have the Plex docker limited to 25GB of RAM. Only plex and qbittorrent use some amount of RAM but never more than 35GB out of 64GB... --runtime=nvidia --memory=25G
March 3, 20251 yr Community Expert 51 minutes ago, Zotarios said: I have the Plex docker limited to 25GB of RAM. Only plex and qbittorrent use some amount of RAM but never more than 35GB out of 64GB... --runtime=nvidia --memory=25G ...OK, but it's killed it 3 times starting on back on the 1st with the last being at 12:29 yesterday so... Mar 2 12:29:06 Zotarios kernel: [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name Mar 2 12:29:06 Zotarios kernel: [ 20873] 0 20873 109 0 28672 0 0 s6-svscan Mar 2 12:29:06 Zotarios kernel: [ 21161] 0 21161 55 0 24576 0 0 s6-supervise Mar 2 12:29:06 Zotarios kernel: [ 21164] 0 21164 52 0 24576 0 0 s6-linux-init-s Mar 2 12:29:06 Zotarios kernel: [ 21198] 0 21198 55 0 24576 0 0 s6-supervise Mar 2 12:29:06 Zotarios kernel: [ 21200] 0 21200 55 0 24576 0 0 s6-supervise Mar 2 12:29:06 Zotarios kernel: [ 21201] 0 21201 55 0 24576 0 0 s6-supervise Mar 2 12:29:06 Zotarios kernel: [ 21202] 0 21202 55 0 24576 0 0 s6-supervise Mar 2 12:29:06 Zotarios kernel: [ 21222] 0 21222 52 0 24576 0 0 s6-ipcserverd Mar 2 12:29:06 Zotarios kernel: [ 21477] 0 21477 1835 160 53248 0 0 bash Mar 2 12:29:06 Zotarios kernel: [ 21496] 0 21496 1421 32 49152 0 0 sleep Mar 2 12:29:06 Zotarios kernel: [3644454] 99 3644454 7343318 6169236 49897472 0 0 Plex Media Serv Mar 2 12:29:06 Zotarios kernel: [3644504] 99 3644504 16382 8377 143360 0 0 Plex Script Hos Mar 2 12:29:06 Zotarios kernel: [3644560] 99 3644560 16035 8098 143360 0 0 Plex Script Hos Mar 2 12:29:06 Zotarios kernel: [3644719] 99 3644719 10725 480 94208 0 0 Plex Tuner Serv Mar 2 12:29:06 Zotarios kernel: [3645595] 99 3645595 2243091 45438 581632 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: [3646274] 99 3646274 2244279 48306 598016 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: [3646796] 99 3646796 650 277 45056 0 0 EasyAudioEncode Mar 2 12:29:06 Zotarios kernel: [3646901] 99 3646901 2243991 46613 573440 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: [3647491] 99 3647491 12825 2091 135168 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: [3652223] 99 3652223 14089 1715 147456 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: [3653741] 99 3653741 14687 2246 155648 0 0 Plex Transcoder Mar 2 12:29:06 Zotarios kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=/,mems_allowed=0,oom_memcg=/docker/9aa73a6ac4ac029a8a5b2fe5e8319b94cc5623094e9cd30d992f3765e29ee251,task_memcg=/docker/9aa73a6ac4ac029a8a5b2fe5e8319b94cc5623094e9cd30d992f3765e29ee251,task=Plex Media Serv,pid=3644454,uid=99 Mar 2 12:29:06 Zotarios kernel: Memory cgroup out of memory: Killed process 3644454 (Plex Media Serv) total-vm:29373272kB, anon-rss:24667224kB, file-rss:244kB, shmem-rss:9476kB, UID:99 pgtables:48728kB oom_score_adj:0 Mar 2 12:29:09 Zotarios kernel: oom_reaper: reaped process 3644454 (Plex Media Serv), now anon-rss:136kB, file-rss:244kB, shmem-rss:36kB
May 1, 20251 yr I have noticed the same issue with my Plex instance and I don't think it has anything to do with unraid. I am on version 6.12.15 and still get the same error. I have only noticed it when recording a tv program and watching it live at the same time. I am assuming something about transcoding with the audio. It fills up the memory slowly until the limit I have set (16GB) Apr 30 22:58:37 NASTower kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=3f8cc82a4753f22582e35c1899828212a266e48a78c1617f22d4746025a65279,mems_allowed=0,oom_memcg=/docker/3f8cc82a4753f22582e35c1899828212a266e48a78c1617f22d4746025a65279,task_memcg=/docker/3f8cc82a4753f22582e35c1899828212a266e48a78c1617f22d4746025a65279,task=Plex Media Serv,pid=25392,uid=99 Apr 30 22:58:37 NASTower kernel: Memory cgroup out of memory: Killed process 25392 (Plex Media Serv) total-vm:299332kB, anon-rss:65404kB, file-rss:40712kB, shmem-rss:4kB, UID:99 pgtables:604kB oom_score_adj:0
May 23, 20251 yr Author But if it has a max memory (16 GB in your case), it should never kill unraid OS processes as there's plenty of free memory available
January 5Jan 5 Author It keeps happening from time to time... is it still Plex's fault? zotarios-diagnostics-20260105-1328.zip
January 5Jan 5 Community Expert 31 minutes ago, Zotarios said:It keeps happening from time to time... is it still Plex's fault?zotarios-diagnostics-20260105-1328.zipYep, it's hitting the limit on the container Memory cgroup out of memory: Killed process 2086114 (Plex Media Serv)
January 5Jan 5 Author If it hits the docker limit, it doesn't mean it hits the system max ram usage, right? In that case, is it safe system-wide? Will it only kill some processes in the docker itself?
January 5Jan 5 Community Expert 19 minutes ago, Zotarios said:Will it only kill some processes in the docker itself?As long as it's only the container limit that's hit yes.
January 5Jan 5 Community Expert You'll still need to reboot or FCP will warn you since it's in the log
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.