[Config Support]: Errors when attempting to restream using go2rtc #11108
-
Describe the problem you are havingI'm attempting to leverage restreams for my Amcrest camera feeds to minimize the number of connections to my camera, per the Frigate docs here. When I run the config below, I receive three errors (also shown in logs below):
and
and
I've confirmed that the URLs for my camera streams under 'go2rtc' are correct, as I can stream them directly from VLC using the same URLs. Version0.13.2-6476F8A Frigate config filego2rtc:
streams:
driveway_stream:
- rtsp:https://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
driveway_stream_sub:
- rtsp:https://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1
cameras:
driveway:
ffmpeg:
inputs:
- path: rtsp:https://127.0.0.1:8554/driveway_stream_sub
roles:
- detect
- path: rtsp:https://127.0.0.1:8554/driveway_stream
roles:
- record
live:
stream_name: driveway_stream Relevant log outputfrigate | s6-rc: info: service s6rc-fdholder: starting
frigate | s6-rc: info: service s6rc-oneshot-runner: starting
frigate | s6-rc: info: service s6rc-oneshot-runner successfully started
frigate | s6-rc: info: service fix-attrs: starting
frigate | s6-rc: info: service s6rc-fdholder successfully started
frigate | s6-rc: info: service fix-attrs successfully started
frigate | s6-rc: info: service legacy-cont-init: starting
frigate | s6-rc: info: service legacy-cont-init successfully started
frigate | s6-rc: info: service log-prepare: starting
frigate | s6-rc: info: service log-prepare successfully started
frigate | s6-rc: info: service nginx-log: starting
frigate | s6-rc: info: service go2rtc-log: starting
frigate | s6-rc: info: service frigate-log: starting
frigate | s6-rc: info: service nginx-log successfully started
frigate | s6-rc: info: service go2rtc-log successfully started
frigate | s6-rc: info: service go2rtc: starting
frigate | s6-rc: info: service frigate-log successfully started
frigate | s6-rc: info: service go2rtc successfully started
frigate | s6-rc: info: service go2rtc-healthcheck: starting
frigate | s6-rc: info: service frigate: starting
frigate | s6-rc: info: service frigate successfully started
frigate | s6-rc: info: service nginx: starting
frigate | s6-rc: info: service go2rtc-healthcheck successfully started
frigate | s6-rc: info: service nginx successfully started
frigate | s6-rc: info: service legacy-services: starting
frigate | 2024-04-25 07:27:33.889428954 [INFO] Preparing Frigate...
frigate | 2024-04-25 07:27:33.891405094 [INFO] Starting NGINX...
frigate | 2024-04-25 07:27:33.896521392 [INFO] Preparing new go2rtc config...
frigate | s6-rc: info: service legacy-services successfully started
frigate | 2024-04-25 07:27:33.903904315 [INFO] Starting Frigate...
frigate | 2024-04-25 07:27:34.132423299 [INFO] Starting go2rtc...
frigate | 2024-04-25 07:27:34.264922169 07:27:34.264 INF go2rtc version 1.8.4 linux/amd64
frigate | 2024-04-25 07:27:34.265485751 07:27:34.265 INF [rtsp] listen addr=:8554
frigate | 2024-04-25 07:27:34.265542877 07:27:34.265 INF [api] listen addr=:1984
frigate | 2024-04-25 07:27:34.265740854 07:27:34.265 INF [webrtc] listen addr=:8555
frigate | 2024-04-25 07:27:35.087024097 [2024-04-25 07:27:35] frigate.app INFO : Starting Frigate (0.13.2-6476f8a)
frigate | 2024-04-25 07:27:37.356475971 [2024-04-25 07:27:37] peewee_migrate.logs INFO : Starting migrations
frigate | 2024-04-25 07:27:37.360925696 [2024-04-25 07:27:37] peewee_migrate.logs INFO : There is nothing to migrate
frigate | 2024-04-25 07:27:37.367982600 [2024-04-25 07:27:37] frigate.app INFO : Recording process started: 376
frigate | 2024-04-25 07:27:37.370609179 [2024-04-25 07:27:37] frigate.app INFO : go2rtc process pid: 89
frigate | 2024-04-25 07:27:37.395919763 [2024-04-25 07:27:37] detector.coral INFO : Starting detection process: 385
frigate | 2024-04-25 07:27:40.015475834 [2024-04-25 07:27:37] frigate.app INFO : Output process started: 387
frigate | 2024-04-25 07:27:40.015566357 [2024-04-25 07:27:37] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb
frigate | 2024-04-25 07:27:40.026531479 [2024-04-25 07:27:37] frigate.app INFO : Camera processor started for driveway: 395
frigate | 2024-04-25 07:27:40.032288418 [2024-04-25 07:27:40] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found
frigate | 2024-04-25 07:27:40.032405250 [2024-04-25 07:27:37] frigate.app INFO : Capture process started for driveway: 396
frigate | 2024-04-25 07:27:43.893361476 [INFO] Starting go2rtc healthcheck service...
frigate | 2024-04-25 07:27:57.481832786 [2024-04-25 07:27:57] ffmpeg.driveway.record ERROR : rtsp:https://127.0.0.1:8554/driveway_stream: Invalid data found when processing input
frigate | 2024-04-25 07:27:57.482295611 [2024-04-25 07:27:57] watchdog.driveway INFO : Terminating the existing ffmpeg process...
frigate | 2024-04-25 07:27:57.482940649 [2024-04-25 07:27:57] watchdog.driveway INFO : Waiting for ffmpeg to exit gracefully...
frigate | 2024-04-25 07:28:07.499422602 [2024-04-25 07:28:07] ffmpeg.driveway.record ERROR : rtsp:https://127.0.0.1:8554/driveway_stream: Invalid data found when processing input
frigate | 2024-04-25 07:28:07.499458853 [2024-04-25 07:28:07] watchdog.driveway INFO : Terminating the existing ffmpeg process...
frigate | 2024-04-25 07:28:07.499545241 [2024-04-25 07:28:07] watchdog.driveway INFO : Waiting for ffmpeg to exit gracefully...
frigate | 2024-04-25 07:28:11.194736253 07:28:11.194 WRN [rtsp] error="streams: codecs not matched: H264 => H264, H265, AAC" stream=driveway_stream Frigate statsNo response Operating systemDebian Install methodDocker Compose Coral versionUSB Any other information that may be helpfulA screenshot of my camera's settings from the Amcrest interface: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Update: Rebooting the camera seems to have made these errors go away. I'll leave this discussion up for future reference for others, but am also open to other critiques of my config and anything I can do to make the process more efficient. |
Beta Was this translation helpful? Give feedback.
Update: Rebooting the camera seems to have made these errors go away. I'll leave this discussion up for future reference for others, but am also open to other critiques of my config and anything I can do to make the process more efficient.