[Config Support]: Multiple types of cameras crashing ffmpeg/go2rtc/frigate but only when viewing livestream #14823
Replies: 1 comment 15 replies
-
|
There's no reason to have separate streams for 2way and non 2 way. If you define it has the docuemtnation recommends where then the second stream in the list will be used for two way audio. This is the config that I have for my reolink doorbell and it works perfectly without any crashes What firmware version is your doorbell on? There are some known problematic firmware versions for the reolink doorbell. |
Beta Was this translation helpful? Give feedback.
-
|
Well then what's going on the logs I posted originally? Frigate was absolutely restarting there on its own and only after camera related errors. |
Beta Was this translation helpful? Give feedback.
-
It received sig kill, so either it failed the container healthcheck or something external told it to stop |
Beta Was this translation helpful? Give feedback.
-
|
What would cause the container to fail the healthcheck? |
Beta Was this translation helpful? Give feedback.
-
|
if the API stops responding frigate/docker/main/Dockerfile Lines 244 to 245 in bc371ac |
Beta Was this translation helpful? Give feedback.
-
|
Well, one way or another, viewing the camera originally was causing that to happen. It also only errors out when watching the livestream - there are no errors present when it is simply recording 24/7. I'll update if I can get some more useful information for it. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
When viewing Cam5, ffmpeg and frigate will crash after a brief time passes. The culprit Cam5 is a Reolink Doorbell camera over Wi-Fi. I've had better luck using the RTSP camera than the recommended Reolink RTMP stream, and I've had much better results by passing the camera into ffmpeg through go2rtc as opposed to a native/direct rtsp connection. I also can't get 2 way audio without the RTSP stream it seems, so I'd like a way to get that to actually work without crashing everything. However, that 2 way audio won't work when using ffmpeg: for the connection.
I've created a separate Frigate camera of the same camera connection, where one uses ffmpeg and one doesn't. See "Cam5" and Cam5_2Way" in the configs - they're the same but one uses ffmpeg for the connection and one doesn't. I've named them as such because using ffmpeg: doesn't allow for 2 way audio within go2rtc or frigate. However, note that in the logs attached, they're named backwards - "Cam5_2Way" uses ffmpeg and "Cam5" doesn't.
Viewing the ffmpeg connection doesn't seem to cause issues within Frigate, but viewing the other camera (without ffmpeg:) will cause a quick crash within a few minutes.
Attached are a few other cameras which sometimes have comparable hiccups but typically it's only their substream. It's hard to tell if these cameras are having separate issues, or if perhaps they are related to ffmpeg crashing as a result of the Reolink Cam5 crashing. I've definitely experienced them failing in the past, but I seem to be unable to reproduce it now without first causing the Reolink cam to crash.
In the past, I've tried using:
For the RTMP stream, but it doesn't allow for 2 way audio so it doesn't really help me out much. It doesn't seem to crash when using ffmpeg as well, but I'll still see some logs containing:
If I run it without ffmpeg, I'll get the same types of crashes that I'll get for the RTSP stream but with slightly different logs:
logs of RTMP without ffmpeg
Is there no way to allow go2rtc to have 2 way audio while using ffmpeg: for the input line? Is there any way I can make the native config without ffmpeg more error tolerant? It seems very counter-productive for any ffmpeg related errors to bring down all of the cameras for an ffmpeg restart. Not recording is the exact problem to avoid, so I'm a bit confused why that is expected behavior.
Let me know if I can post any other logs or try anything else to troubleshoot this better.
Version
0.15.0 Beta 1
Frigate config file
Click me to expand
Relevant Frigate log output
Click me to expand log
Relevant go2rtc log output
Click me to expand log
Frigate stats
Omitted for character limit
Operating system
Rocky Linux
Install method
Docker Compose
docker-compose file or Docker CLI command
Click me to expand
Object Detector
Other
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions