You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These happen every once in a while, and do not always cause go2rtc to crash
Another one I had with Frigate is:
Jan 13 17:07:35 x01go2rtc01 go2rtc_linux_amd64[127]: 17:07:35.793 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:241 > error="read tcp <go2rtc_ip>:8554-><frigate_ip>:45954: i/o timeout"
Jan 13 17:07:39 x01go2rtc01 systemd[1]: go2rtc.service: A process of this unit has been killed by the OOM killer.
Jan 13 17:07:40 x01go2rtc01 systemd[1]: go2rtc.service: Main process exited, code=killed, status=9/KILL
Jan 13 17:07:52 x01go2rtc01 systemd[1]: go2rtc.service: Failed with result 'oom-kill'.
Jan 13 17:07:52 x01go2rtc01 systemd[1]: go2rtc.service: Consumed 9h 15min 29.308s CPU time.
The text was updated successfully, but these errors were encountered:
Any idea how I can troubleshoot it further?
I'm running it in a LXC container on Proxmox VE with lots of resources (4 vCPUs, 4GB RAM, plenty of disk space), so I don't really know what would the issue be.
go2rtc version:
go2rtc platform=linux/amd64 revision=dbe9e4a version=1.9.7
every once in a while (few days) go2rtc crashes with
the camera is running https://github.com/roleoroleo/yi-hack-Allwinner-v2
These happen every once in a while, and do not always cause go2rtc to crash
Another one I had with Frigate is:
The text was updated successfully, but these errors were encountered: