Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go2rtc crashes after github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 error read tcp i/o timeout" #1550

Open
spitfire opened this issue Jan 15, 2025 · 4 comments
Labels
question Further information is requested

Comments

@spitfire
Copy link

spitfire commented Jan 15, 2025

go2rtc version:
go2rtc platform=linux/amd64 revision=dbe9e4a version=1.9.7

every once in a while (few days) go2rtc crashes with

Jan 15 22:44:31 x01go2rtc01 go2rtc_linux_amd64[29321]: 22:44:31.790 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error="read tcp <go2rtc_ip>:39926-><camera_ip>:554: i/o timeout" url=rtsp://<camera_ip>/ch0_0.h264
Jan 15 22:45:47 x01go2rtc01 systemd[1]: go2rtc.service: Main process exited, code=killed, status=9/KILL
Jan 15 22:45:48 x01go2rtc01 systemd[1]: go2rtc.service: Failed with result 'signal'.
Jan 15 22:45:48 x01go2rtc01 systemd[1]: go2rtc.service: Consumed 48min 3.244s CPU time.

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:

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.
@AlexxIT AlexxIT added the question Further information is requested label Jan 16, 2025
@AlexxIT
Copy link
Owner

AlexxIT commented Jan 16, 2025

  1. I don't see any "crashes" here. Process killed. It doesn't depend on go2rtc.
  2. "read tcp i/o timeout" it's a warning (WRN), not error. And it doesn't depend on go2rtc.

@spitfire
Copy link
Author

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.

@AlexxIT
Copy link
Owner

AlexxIT commented Jan 16, 2025

It all depends on your environment. You set it up that way. Only you can answer your own questions.

@spitfire
Copy link
Author

Thank you, that’s very helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants