Hello dear community,

 

I got an error in the morning from the fix common issues plugin. This is the first time, I am experiencing this kind of issue. I had some "unknown" red flagged errors in the last weeks, but they disappeared after a reboot and I could not really see anything from the GUI not working.

 

I am running plenty of docker containers one VM. The VM was stopped when this issue appeared and was not online for several days.

 

On a side note: I am one of the people who need to use macvlan because of their ubiquiti setup. While the update notes recommend to enable "host access to docker", I can't enable this. Once enabled, GUI becomes unavailable, all dockers, however, remain accessible.

 

Please find attached the diagnostics.

 

Any help is appreciated. I would really like to fix this rather sooner than later

 

tower-diagnostics-20240303-0824.zip

4 hours ago, cloudyhome said:

Any help is appreciated. I would really like to fix this rather sooner than late

 

Looks like maybe your NVR isn't configured correctly, ffmpeg looks like it was transcoding to RAM and ran the system OOM.

 

Mar  2 01:16:28 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/docker/d4f9dee74e2b127f4e102ce05fada9f34016069af611ac5c91f41d49f669731c,task=ffmpeg,pid=8558,uid=0
Mar  2 01:16:28 Tower kernel: Out of memory: Killed process 8558 (ffmpeg) total-vm:56654772kB, anon-rss:56268620kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:110316kB oom_score_adj:0
Mar  2 01:16:31 Tower kernel: oom_reaper: reaped process 8558 (ffmpeg), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

 

Thanks a lot @Michael_P! I will give it a try. My nvr is frigate, I will dig into this and update this thread accordingly. My first guess regarding frigate is that it is maybe caused by the car as a non-moving object within frigate. I saw some "car"-event with 20 hours recording. Let's see.

 

 

Quick update after some testing with frigate: It looks like it is fixed after a switch to vaapi instead of qsv for all reolink cams. Also updated the input profile for the h265 cam according to this link https://github.com/blakeblackshear/frigate/discussions/7859

 

I will monitor the situation and keep this thread updated in case the problem reappears.