[Support]: Enabling go2rtc causes constant "Unable to keep up with" errors in logs. #15354
Replies: 9 comments 9 replies
-
Maybe not related to your specific problem but you should fix this first and check again.
And you define your main streams in the go2rtc section, but you do not use them in the cameras.
|
Beta Was this translation helpful? Give feedback.
-
@banthungprong Thank you. I can't really see how either of those issues would lead to the errors I'm experiencing, however I changed the config as you indicated. Unfortunately I did nothing to solve the errors. |
Beta Was this translation helpful? Give feedback.
-
To see if the processor was the issue, I transferred my setup to a new, bare metal Ryzen 7 machine with 64GB of RAM, and new pcie 4.0 nvme drive and Ubuntu, 24.04, using the same Coral USB device for detection. The same errors appeared immediately. So it doesn't seem to be related to the N100 hardware. |
Beta Was this translation helpful? Give feedback.
-
The |
Beta Was this translation helpful? Give feedback.
-
@hawkeye217 Here's the latest log from the new machine.
|
Beta Was this translation helpful? Give feedback.
-
Maybe you could try to change the hwaccels to qsv. I just did this for all my cameras. I saw a few posts here and after changing that the error was gone. With 0.15.x you can and should switch to preset-qsv-h264/h265 from preset-vaapi where possible for each camera |
Beta Was this translation helpful? Give feedback.
-
A further update. Frigate is back on the bare metal N100, but go2rtc is instead running standalone on a remote machine. The Frigate config is now as follows:
Error messages continue:
|
Beta Was this translation helpful? Give feedback.
-
I tried adding the low-quality detect streams to go2rtc, and using those in the Frigate config instead of the direct camera links, but the errors are the same. So, to summarize, it seems that any time my frigate pulls from go2rtc for either the record or detect streams, or the local go2rtc is configured to use direct camera streams, then those error occur. If detect and record only pull directly from the cameras, and there is no go2rtc config, then the errors disappear. |
Beta Was this translation helpful? Give feedback.
-
So I reset my original N100 back to the original config on V0.14, and the errors are gone. I guess I'll have to do without webRTC for the time being. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I'm a long time user of Frigate. I have a fairly basic setup. A bare-metal N100 with 8GB of RAM, a 1TB NVME SSD. and a USB Coral, connected with Home Assistant running on another machine. I have detections enabled on all four cameras.
Recently I enabled go2rtc due to the Home Assistant update. Since then I have noticed fairly constant error messages in the log files.
If I remove the go2rtc config again the errors stop.
The errors all look like this:
Unable to keep up with recording segments in cache for driveway. Keeping the 6 most recent segments out of 7 and discarding the rest...
I've tried the basic troubleshooting at https://docs.frigate.video/troubleshooting/recordings/. I added the debug config as suggested, and it returns well within the tolerances it recommends. The longest copied time I could see was
0.1
seconds.I've added the additional options to the docker file that it suggests regarding swapiness, but that doesn't seem to have made any difference.
My CPU usage on the machine usually sits around 10-12% on all four cores, and RAM usage is about 1.4GB out of 8GB.
I've also upgraded from stable to 0.15beta2 to see if that helps, but it does not.
I'd really appreciate any suggestions as to where I could start looking. I'd really like to keep the go2rtc config enabled as it looks so much better in the app and in home assistant.
Version
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
No errors in gortc log output.
FFprobe output from your camera
Frigate stats
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
TP-Link
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions