April 20, 20251 yr Hi guys, As per suggestion in and the "Fix Common Problems" plugin, I am receiving the "Out Of Memory errors detected on your server" message. I am attaching my Diagnostics file to this post. Happy to answer any/all questions. weetbix-server-diagnostics-20250420-1220.zip
April 20, 20251 yr Community Expert Solution 9 hours ago, Weetbix M Milk said: Hi guys, As per suggestion in and the "Fix Common Problems" plugin, I am receiving the "Out Of Memory errors detected on your server" message. I am attaching my Diagnostics file to this post. Happy to answer any/all questions. weetbix-server-diagnostics-20250420-1220.zip 593.44 kB · 0 downloads Looks like Frigate is transcoding to RAM, you'll need to configure it to use a disk
April 20, 20251 yr Author 11 hours ago, Michael_P said: Looks like Frigate is transcoding to RAM, you'll need to configure it to use a disk Thank you for the reply. I add these Extra Parameters onto each container, "--memory=8g --cpus=4 --memory-swap=-1 --restart=unless-stopped". For Frigate in particular I use, "--shm-size=256m --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --runtime=nvidia --memory=8G --cpus=4 --restart=unless-stopped". Is there a reason these arguments are not working?
April 21, 20251 yr Community Expert 9 hours ago, Weetbix M Milk said: Is there a reason these arguments are not working? Don't know, but I've seen dozens of users have the same problem using Frigate, but my guess is because so many ffmpeg processes are spawned. You can force Docker to adhere to the limit with the --oom-kill-disable flag - but be warned that if it doesn't do it correctly it will bring down the host. Your best bet if it keeps happening is to map the temp location to a disk.
April 28, 20251 yr Author On 4/21/2025 at 7:38 PM, Michael_P said: Don't know, but I've seen dozens of users have the same problem using Frigate, but my guess is because so many ffmpeg processes are spawned. You can force Docker to adhere to the limit with the --oom-kill-disable flag - but be warned that if it doesn't do it correctly it will bring down the host. Your best bet if it keeps happening is to map the temp location to a disk. I'd like to confirm that setting the transcode location to a disk was the solution. I followed the Frigate guide precisely and still had these issues. I would encourage anyone to use a VM for it or get a separate machine, I have ordered one now since discovering this issue.
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.