September 9, 2025Sep 9 Submitting my diagnostics as suggested by the forum post regarding "Out of memory errors detected on your server".Took note that only 20% of the RAM is being used.https://forums.unraid.net/topic/120220-fix-common-problems-more-information/#findComment-1098721Out of memory errors detected on your server On a properly running server this error should never appear. Effectively, one process on your server requested to use some memory and it wasn't available so the OS killed off a low priority (or very infrequently used) process so that the higher priority process could keep running. The consequences of this error could either be unnoticeable or severe depending upon what process was killed off. You should create a new post in General Support and include your diagnostics. Ultimately your recourse to clear this error is a reboot, but the forum users will need to see the diagnostics before you reboottower-diagnostics-20250909-1749.zip Edited September 9, 2025Sep 9 by Nanuk_
September 9, 2025Sep 9 Community Expert 32 minutes ago, Nanuk_ said:Submitting my diagnostics as suggested by the forum post regarding "Out of memory errors detected on your server".Took note that only 20% of the RAM is being used.https://forums.unraid.net/topic/120220-fix-common-problems-more-information/#findComment-1098721tower-diagnostics-20250909-1749.zipTdarr is hitting the memory limit and is being killed. Either switch to transcoding to a disk, or reduce the number of simultaneous transcodes
September 9, 2025Sep 9 Author With 64GB of RAM, what is the suggested concurrent transcodes? I have it set to 3 at the moment?I've changed it to 2 concurrent for now. I plan to upgrade to 128GB. what is the suggested concurrent transcodes for that? Edited September 9, 2025Sep 9 by Nanuk_
September 9, 2025Sep 9 Community Expert Impossible to say, will depend on what you're transcoding and with what settings, you have to find that out yourself.
September 9, 2025Sep 9 Community Expert And make sure to reboot, or FCP will keep warning you about the OOMs that have already occurred
September 21, 2025Sep 21 Author tower-diagnostics-20250921-1912.zipdSo Just to update you guys, I've upgraded my NAS's RAM from 16GB to 128GB and added a second nvme to the cache pool. I've also decreased the local tdarr node concurrent GPU transcodes from 3 down to 2. But I've kept the tdarr node on my desktop at 3. with this current config I'm still getting out of memory errors. Which I don't get since at 128GB of RAM I never ever hit 30% used. Is it the ZFS cache pool that's is getting used up? Maybe it's some other "memory" I should be tracking.
September 21, 2025Sep 21 Community Expert 34 minutes ago, Nanuk_ said:tower-diagnostics-20250921-1912.zipdSo Just to update you guys, I've upgraded my NAS's RAM from 16GB to 128GB and added a second nvme to the cache pool. I've also decreased the local tdarr node concurrent GPU transcodes from 3 down to 2. But I've kept the tdarr node on my desktop at 3. with this current config I'm still getting out of memory errors. Which I don't get since at 128GB of RAM I never ever hit 30% used. Is it the ZFS cache pool that's is getting used up? Maybe it's some other "memory" I should be tracking.the container is limited to 2gb by the looks of it and well, if you limit it to 2gb and it "wants" to use more, it gets killed for running out of memory
September 21, 2025Sep 21 Author 1 hour ago, Mainfrezzer said:the container is limited to 2gb by the looks of it and well, if you limit it to 2gb and it "wants" to use more, it gets killed for running out of memoryNoted, gonna bump it to 16gb and see how that goes! Thanks for the advice! Edited September 21, 2025Sep 21 by Nanuk_
October 21, 2025Oct 21 Author tower-diagnostics-20251021-1953.zipSo I've allocated more memory for the containers. It was running fine for the most part. But last night I started using tails scale and this afternoon I got the out of memory error again. Should I be trying to allocate more memory specifically for tail scale?
October 21, 2025Oct 21 Author Though I find it weird to be getting an "Out of Memory" error when based off the dashboard I'm only using 20% of the physical memory. Can this be triggered by a cache error being thrown by one of the CPU cores?
October 21, 2025Oct 21 Community Expert 35 minutes ago, Nanuk_ said:Should I be trying to allocate more memory specifically for tail scale?Tdarr hit its limit and was killed, not tailscaleOct 21 18:54:44 Tower kernel: Memory cgroup out of memory: Killed process 66443 (Tdarr_Server) total-vm:15349868kB, anon-rss:14818028kB, file-rss:35480kB, shmem-rss:0kB, UID:99 pgtables:99960kB oom_score_adj:0
October 21, 2025Oct 21 Author 1 hour ago, Michael_P said:Tdarr hit its limit and was killed, not tailscaleOct 21 18:54:44 Tower kernel: Memory cgroup out of memory: Killed process 66443 (Tdarr_Server) total-vm:15349868kB, anon-rss:14818028kB, file-rss:35480kB, shmem-rss:0kB, UID:99 pgtables:99960kB oom_score_adj:0 Thanks! I'll allocate more physical memory to the tdarr container.
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.