Replies: 5 comments 21 replies
-
|
Without logs there's no way to know what was going on, so there's no way to help here. If it occurs again you should get logs so we can see what happened. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/ivanjx/frigate my fork is just removing the detection grid stuff, scoring, and updating go2rtc to 1.9.4 |
Beta Was this translation helpful? Give feedback.
-
|
go2rtc 1.9.3 and 1.9.4 are known to have major flaws (which is why the latest version wasn't included in the release), so that could be part of the issue. The logs indicate a python BUS error likely occurred and unfortunately that error is not recoverable. It's possible we could detect in S6 that writing to logs failed and restart frigate but not 100% sure. If this happens again it would be great to know the contents of /dev/shm with size information |
Beta Was this translation helpful? Give feedback.
-
|
how could i retrieve the shm info? the concept of shm is very new to me. |
Beta Was this translation helpful? Give feedback.
-
|
as of why i updated the go2rtc this is the reason: AlexxIT/go2rtc#894 |
Beta Was this translation helpful? Give feedback.
-
|
you'd get a shell in the container ( |
Beta Was this translation helpful? Give feedback.
-
|
got some new logs from the frigate ui right after restarting the container. something seems to be crashing that caused detection and recording to not work (affected all cameras). |
Beta Was this translation helpful? Give feedback.
-
|
This is a known issue with the dev builds. |
Beta Was this translation helpful? Give feedback.
-
|
is there an open issue for it so i can track it? thanks |
Beta Was this translation helpful? Give feedback.
-
|
No, it's a dev issue so we just track and fix those internally |
Beta Was this translation helpful? Give feedback.
-
|
I have put up a fix for it |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 new issue since your commit |
Beta Was this translation helpful? Give feedback.
-
|
oh, yeah, we really should have a lint rule on that type of thing. Fixed in push |
Beta Was this translation helpful? Give feedback.
-
|
also |
Beta Was this translation helpful? Give feedback.
-
|
this should be one of the true cause why my cameras stopped recording and detecting, though this time only one camera is affected: it hasnt recovered automatically since. edit: frigate should mark these cameras as unavailable instead of recording.
|
Beta Was this translation helpful? Give feedback.
-
it does, not sure why yours aren't but that system is already in place and it works for me if I unplug one of my cameras |
Beta Was this translation helpful? Give feedback.
-
|
unplugging or rebooting cameras work fine for me as well. the problem could be the ffmpeg process is stuck or something because of bad frames. does it send SIGKILL on |
Beta Was this translation helpful? Give feedback.
-
|
it first sends sigterm and then if after 30 seconds the process has not stopped then it sends sigkill but for some reason it gets stuck there |
Beta Was this translation helpful? Give feedback.
-
just today, i found out that my cameras arent recording anything for a few hours for no reason (probably something killed by oom killer). i have set up a notification on home assistant to notify me if any cameras are unavailable but they dont seem to be triggered because live view is apparently still working. only restarting the container made the recording working again but now i cant sleep well at night knowing that frigate may not record silently.
go2rtc config:
HA automation:
Beta Was this translation helpful? Give feedback.
All reactions