Closed superdong69 closed 10 months ago
your logs are full of camera errors, so it makes sense that recordings would be missing.
looks like camera timeouts rtsp://127.0.0.1:8554/house_back1: Connection timed out
and other issues, I'd suggest checking go2rtc logs
Go2rtc logs:
2023-11-27 19:15:45.513907862 [INFO] Preparing new go2rtc config...
2023-11-27 19:15:45.806204672 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually
2023-11-27 19:15:45.834912613 [INFO] Starting go2rtc...
2023-11-27 19:15:45.898845349 19:15:45.898 INF go2rtc version 1.8.4 linux/amd64
2023-11-27 19:15:45.899231875 19:15:45.899 INF [api] listen addr=:1984
2023-11-27 19:15:45.899348986 19:15:45.899 INF [rtsp] listen addr=:8554
2023-11-27 19:15:45.899676490 19:15:45.899 INF [webrtc] listen addr=:8555
2023-11-27 19:15:55.510650242 [INFO] Starting go2rtc healthcheck service...
2023-11-27 22:48:33.633564842 22:48:33.633 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=rtsp://user:pass@192.168.1.91:554/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
2023-11-27 22:48:33.750345268 22:48:33.750 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=rtsp://user:pass@192.168.1.91:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
2023-11-27 22:48:56.829952667 22:48:56.829 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: i/o timeout" stream=house_back1_sub
2023-11-27 22:48:56.841468564 22:48:56.841 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: i/o timeout" stream=house_back1
2023-11-27 22:49:03.926846056 22:49:03.926 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: i/o timeout, dial tcp 192.168.1.91:554: connect: no route to host" stream=house_back1_sub
2023-11-27 22:49:03.926886707 22:49:03.926 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: i/o timeout, dial tcp 192.168.1.91:554: connect: no route to host" stream=house_back1
2023-11-27 22:49:14.268876816 22:49:14.268 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: connect: no route to host, dial tcp 192.168.1.91:554: connect: connection refused" stream=house_back1_sub
2023-11-27 22:49:14.268905176 22:49:14.268 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: connect: no route to host, dial tcp 192.168.1.91:554: connect: connection refused" stream=house_back1
2023-11-27 22:49:20.930137238 22:49:20.930 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: connect: connection refused" stream=house_back1_sub
2023-11-27 22:49:20.940057579 22:49:20.940 WRN [rtsp] error="streams: dial tcp 192.168.1.91:554: connect: connection refused" stream=house_back1
2023-11-29 21:30:22.781702678 21:30:22.781 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp 172.18.0.2:47520->192.168.1.95:554: i/o timeout" url=rtsp://user:pass@192.168.1.95:554/cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
2023-11-29 21:30:24.159349305 21:30:24.159 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp 172.18.0.2:47516->192.168.1.95:554: i/o timeout" url=rtsp://user:pass@192.168.1.95:554/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
2023-11-29 21:30:43.741762306 21:30:43.741 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: i/o timeout" stream=driveway_sub
2023-11-29 21:30:43.761010738 21:30:43.760 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: i/o timeout" stream=driveway
2023-11-29 21:30:50.780845401 21:30:50.780 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: i/o timeout, dial tcp 192.168.1.95:554: connect: connection refused" stream=driveway_sub
2023-11-29 21:30:50.793585531 21:30:50.793 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: i/o timeout, dial tcp 192.168.1.95:554: connect: connection refused" stream=driveway
2023-11-29 21:30:57.810116272 21:30:57.809 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: connect: connection refused" stream=driveway_sub
2023-11-29 21:30:57.820970813 21:30:57.820 WRN [rtsp] error="streams: dial tcp 192.168.1.95:554: connect: connection refused" stream=driveway
looks like cameras are dropping off the network and refusing connections
Yeah, I'm not sure what or how on that one. I never see them dropping. I've run ping traces on them, and never drop packets...strange. Any recommendations on how I can test this out?
So I set up prtg net mon on the network, created a group and assigned all the cameras to it, assigned ping sensors to each camera, and set notification triggers for ping so if the camera drops network connection for 1 sec, I'll get notified. Wondering if the POE switch is flaky.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
Most of the hours of recording of my frigate server to a 6TB cctv drive on my NAS only contain 32mins. Some 11mins, and other the full 59:59. Seems to be completely random. Running 8 cameras, I have about a 2TB surplus on my system, so I know I'm not running out of hard drive space. A bunch of new stuff in the logs I've never seen before. This log is from the system reboot after beta6 upgrade to present. <Log edited for character limit, notations marked as indicated>
Version
frigate:0.13.0-beta6
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Ubuntu 22.10
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
amcrest
Any other information that may be helpful
Ubuntu 22.10