I keep getting out of memory errors

 

I add:

 

     nchan_shared_memory_size 512M;

 

to /etc/nginx/nginx.conf, but it keeps disappearing

 

Does it get overwritten on reboot?

 

Do I need to add it to the flash drive somewhere?

 

Thanks in advance

Alan

mickey-diagnostics-20240921-1043.zip mickey-syslog-20240921-1004.zip

16 minutes ago, AlanC said:

keep getting out of memory errors

 

Looks like Frigate is spawning a bunch of ffmpeg processes and running the host OOM repeatedly - fix the config so it's not writing to RAM or limit the container's memory allowance

6 minutes ago, Michael_P said:

 

Looks like Frigate is spawning a bunch of ffmpeg processes and running the host OOM repeatedly - fix the config so it's not writing to RAM or limit the container's memory allowance

Thanks, it's already limited to 1GB

1 minute ago, AlanC said:

Thanks, it's already limited to 1GB

 

Then its not being respected - you'll need to fix the containers config so that any temp space for encoding and such isn't being done in RAM or you can force docker to limit the RAM instead of the kernel with the --oom-kill-disable flag, but use it cautiously as it's highly likely to bring down the entire system if docker doesn't do it right.

 

https://docs.docker.com/engine/containers/resource_constraints/

 

When you've fixed it, you'll need to reboot so FCP doesn't see it in the log anymore and continue to warn you

Thanks added  --oom-kill-disable now

 

I've also disabled a wifi camera that looks like it has a spotty connection.

 

I've also cut down the number of cameras being processed by go-rtc

 

We'll see how it goes, any idea why nchan_shared_memory_size 512M; keeps disappearing?

 

 

8 hours ago, AlanC said:

to /etc/nginx/nginx.conf, but it keeps disappearing

 

Does it get overwritten on reboot?

Yes - that location is only on RAM.

3 hours ago, itimpi said:

Yes - that location is only on RAM.

Any way of making it persistent?

11 hours ago, AlanC said:

Any way of making it persistent?

You can add code to the config/go file on the flash drive to make the change during the boot sequence.    Whether Unraid ever regenerates the nginx.conf file while running (thus erasing the change) I have no idea.

On 9/21/2024 at 6:35 AM, Michael_P said:

 

Then its not being respected - you'll need to fix the containers config so that any temp space for encoding and such isn't being done in RAM or you can force docker to limit the RAM instead of the kernel with the --oom-kill-disable flag, but use it cautiously as it's highly likely to bring down the entire system if docker doesn't do it right.

 

https://docs.docker.com/engine/containers/resource_constraints/

 

When you've fixed it, you'll need to reboot so FCP doesn't see it in the log anymore and continue to warn you

Thankyou, seems to have done the trick