[Bug]: Stream fails to gracefully restart after go2rtc error #19439
Unanswered
illuzn
asked this question in
Report a Bug
Replies: 2 comments 12 replies
-
We need to see a full copy of the logs, the socket error looks like it is precluded by some type of larger error. |
Beta Was this translation helpful? Give feedback.
11 replies
-
Your GPU also appears to be overloaded. The full logs will reveal more, as @NickM-27 indicated. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
go2rtc will generate io timeouts from time to time (after the scale of days of uptime). I believe this is where there is some form of packet loss over a long time scale.
go2rtc will correctly regenerate the stream (evidenced by it working in Advanced Camera Card in HA and also directly viewing the stream from go2rtc).
However, frigate generates constant socket errors when this occurs.
Steps to reproduce
Version
v0.16.0 rc3 (but also rc1 and rc2 - didn't occur in v0.15.x)
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
Swann DVR8-5580G (whitelabeled hikvision with custom firmware)
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Coincidentally, this issue led me to change my max log size (and this should be included in the recommended settings) because my logs became over 100gb because this error repeats itself every 1ms.
Also restarting frigate resolves the issue.
Beta Was this translation helpful? Give feedback.
All reactions