[Config Support]: Frigate wont start after update. Config validation error

[janu0112]

Hello, i have this Problem:

2024-08-12 19:09:28.024443606 [INFO] Starting go2rtc... 2024-08-12 19:09:28.566007294 21:09:28.562 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-08-12 19:09:28.569179759 21:09:28.569 INF config path=/dev/shm/go2rtc.yaml 2024-08-12 19:09:28.570843392 21:09:28.569 INF [api] listen addr=:1984 2024-08-12 19:09:28.570848366 21:09:28.569 INF [rtsp] listen addr=:8554 2024-08-12 19:09:28.570853340 21:09:28.570 INF [webrtc] listen addr=:8555/tcp s6-rc: info: service nginx successfully started s6-rc: info: service certsync: starting s6-rc: info: service certsync successfully started s6-rc: info: service legacy-services: starting 2024-08-12 19:09:30.291339937 [INFO] Starting certsync... s6-rc: info: service legacy-services successfully started 2024-08-12 19:09:30.565221165 127.0.0.1 - - [12/Aug/2024:21:09:30 +0200] "" 400 0 "-" "-" "-" 2024-08-12 19:09:30.753004312 [2024-08-12 21:09:30] frigate.app INFO : Starting Frigate (0.14.0-da913d8) 2024-08-12 19:09:30.753011445 [2024-08-12 21:09:30] frigate.app INFO : Creating directory: /tmp/cache 2024-08-12 19:09:30.758428303 [2024-08-12 21:09:30] frigate.util.config INFO : Checking if frigate config needs migration... 2024-08-12 19:09:30.807230094 [2024-08-12 21:09:30] frigate.util.config INFO : frigate config does not need migration... 2024-08-12 19:09:30.829432685 2024-08-12 19:09:30.829483432 2024-08-12 19:09:30.829514507 Your config file is not valid! 2024-08-12 19:09:30.829574653 Please check the docs at 2024-08-12 19:09:30.829628767 https://docs.frigate.video/configuration/index 2024-08-12 19:09:30.829676325 2024-08-12 19:09:30.829723970 2024-08-12 19:09:30.829768971 Config Validation Errors 2024-08-12 19:09:30.829815857 2024-08-12 19:09:30.829964155 mqtt.stats_interval: Input should be greater than or equal to 15 2024-08-12 19:09:30.830024156 2024-08-12 19:09:30.830072467 End Config Validation Errors 2024-08-12 19:09:30.830123824 ***** 2024-08-12 19:09:31.263367125 2024/08/12 21:09:31 [error] 181#181: 2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000" 2024-08-12 19:09:31.263528089 2024/08/12 21:09:31 [error] 181#181: 2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000" 2024-08-12 19:09:32.231936081 [INFO] Service Frigate exited with code 1 (by signal 0) s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service certsync: stopping 2024-08-12 19:09:32.250859144 [INFO] Service CERTSYNC exited with code 256 (by signal 15) 2024-08-12 19:09:32.251211213 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) s6-rc: info: service certsync successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service certsync-log: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service certsync-log successfully stopped 2024-08-12 19:09:32.312349545 [INFO] Service NGINX exited with code 0 (by signal 0) s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped 2024-08-12 19:09:32.321290031 exit with signal: terminated s6-rc: info: service frigate-log successfully stopped 2024-08-12 19:09:32.340990276 [INFO] The go2rtc service exited with code 0 (by signal 0) s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service certsync-log: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service frigate-log successfully started s6-rc: info: service certsync-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service go2rtc-healthcheck successfully started 2024-08-12 19:09:38.708920673 [INFO] Starting NGINX... 2024-08-12 19:09:38.717695907 [INFO] Preparing Frigate... 2024-08-12 19:09:38.719237083 [INFO] Preparing new go2rtc config... 2024-08-12 19:09:38.731679126 [INFO] No TLS certificate found. Generating a self signed certificate... 2024-08-12 19:09:38.753775823 [INFO] Starting Frigate... 2024-08-12 19:09:38.899982335 [INFO] Got IP address from supervisor: 192.168.178.21 2024-08-12 19:09:39.030575018 [INFO] Got WebRTC port from supervisor: 8001 2024-08-12 19:09:40.252702052 [INFO] Starting go2rtc...

Config: frigate.yml:

mqtt: enabled: true host: 192.168.178.21 user: mqtt-user password: 997872Abce.. topic_prefix: frigate

Optional: client id (default: shown below)

WARNING: must be unique if you are running multiple instances

client_id: frigate

Optional: interval in seconds for publishing stats (default: shown below)

stats_interval: 1

Optional: Detectors configuration. Defaults to a single CPU detector

detectors:

# Required: name of the detector

detector_name:

  # Required: type of the detector
  # Frigate provided types include 'cpu', 'edgetpu', and 'openvino' (default: shown below)
  # Additional detector types can also be plugged in.
  # Detectors may require additional configuration.
  # Refer to the Detectors configuration page for more information.
#type: cpu 

detectors: coral: type: edgetpu device: usb

birdseye: enabled: true restream: true mode: objects

objects: track:

• person
• cat filters: person: min_area: 5000 max_area: 100000

go2rtc: streams: Tuerklingel:

• rtsp://admin:997872Abce..@192.168.178.51:554/Preview_01_main
• ffmpeg:rtsp_cam#audio=opus Tuerklingel_sub:
• rtsp://admin:997872Abce..@192.168.178.51:554/Preview_01_sub
• ffmpeg:rtsp_cam#audio=opus Cam-Wohnzimmer:
• rtsp://admin:997872Abce..@192.168.178.60:554/h264Preview_01_main
• ffmpeg:rtsp_cam#audio=opus Cam-Wohnzimmer_sub:
• rtsp://admin:997872Abce..@192.168.178.60:554/h264Preview_01_sub
• ffmpeg:rtsp_cam#audio=opus Cam-Eingang:
• rtsp://admin:997872Abce..@192.168.178.53:554/h264Preview_01_main
• ffmpeg:rtsp_cam#audio=opus Cam-Eingang_sub:
• rtsp://admin:997872Abce..@192.168.178.53:554/h264Preview_01_sub
• ffmpeg:rtsp_cam#audio=opus

cameras: Cam-Wohnzimmer: ffmpeg: inputs:

• path: rtsp://127.0.0.1:8554/Cam-Wohnzimmer?video=copy&audio=aac input_args: preset-rtsp-restream roles:
  • record
• path: rtsp://127.0.0.1:8554/Cam-Wohnzimmer_sub?video=copy input_args: preset-rtsp-restream roles:
  • detect detect: width: 1280 height: 720 fps: 5 snapshots: enabled: true record: enabled: true retain: days: 5 events: retain: default: 5 onvif:

    Required: host of the camera being connected to.

    host: 192.168.178.60

    Optional: ONVIF port for device (default: shown below).

    port: 8000

    Optional: username for login.

    NOTE: Some devices require admin to access ONVIF.

    user: admin

    Optional: password for login.

    password: 997872Abce..

    Optional: PTZ camera object autotracking. Keeps a moving object in

    the center of the frame by automatically moving the PTZ camera.

    Cam-Eingang: ffmpeg: inputs:

• path: rtsp://127.0.0.1:8554/Cam-Eingang?video=copy&audio=aac input_args: preset-rtsp-restream roles:
  • record
• path: rtsp://127.0.0.1:8554/Cam-Eingang_sub?video=copy input_args: preset-rtsp-restream roles:
  • detect detect: width: 1280 height: 720 fps: 5 snapshots: enabled: true record: enabled: true retain: days: 5 events: retain: default: 5 Tuerklingel: ffmpeg: inputs:
• path: rtsp://admin:997872Abce..@192.168.178.51:554/Preview_01_main input_args: preset-rtsp-restream roles:
  • record
• path: rtsp://admin:997872Abce..@192.168.178.51:554/Preview_01_sub roles:
  • detect detect: width: 1280 height: 720 fps: 5 snapshots: enabled: true record: enabled: true retain: days: 7 events: retain: default: 5 version: 0.14

// can anybody help me?

Thank You

[NickM-27]

this is not a feature request