[Config Support]: Frigate constatly crashing with Intel Arc A310

[ElectronicEconomy317]

Describe the problem you are having

Frigate keeps crashing when I try to use the A310...but works fine with the CPU detectors.

Version

0.16.2-4d58206

Frigate config file

mqtt:
  enabled: false
ffmpeg:
  hwaccel_args: preset-vaapi
cameras:
  West_Yard:
    ffmpeg:
      inputs:
        - path: rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
        - path: rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - record
  Front_Yard:
    ffmpeg:
      inputs:
        - path:
            rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
        - path:
            rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=0
          roles:
            - record
detectors:
  openvino:
    type: openvino
    device: GPU
    num_threads: 2

    detect:
      enabled: true
      width: 1280
      height: 720

version: 0.16-0
semantic_search:
  enabled: true
  model_size: small
#face_recognition:
#  enabled: true
#  model_size: large
#lpr:
#  enabled: true
#classification:
#  bird:
#    enabled: true
record:
  enabled: true
  retain:
    days: 45
    mode: motion
  alerts:
    retain:
      days: 7
      mode: active_objects
  detections:
    retain:
      days: 7
      mode: active_objects
objects:
  track:
  - person
  #- car
  - bicycle
  - bird
  - cat
  - dog

Relevant Frigate log output

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
s6-rc: info: service legacy-services successfully started
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
s6-rc: info: service go2rtc-healthcheck successfully stopped
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service nginx-log successfully stopped
2025-10-18 19:16:47.445977912  [INFO] Starting go2rtc...
2025-10-18 19:16:47.556319867  19:16:47.556 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-10-18 19:16:47.556326827  19:16:47.556 INF config path=/dev/shm/go2rtc.yaml
2025-10-18 19:16:47.556807114  19:16:47.556 INF [rtsp] listen addr=:8554
2025-10-18 19:16:47.556809848  19:16:47.556 INF [api] listen addr=:1984
2025-10-18 19:16:47.557418971  19:16:47.557 INF [webrtc] listen addr=:8555
2025-10-18 19:16:47.895344100  [INFO] Starting certsync...
2025-10-18 19:16:48.533779548  127.0.0.1 - - [18/Oct/2025:19:16:48 -0400] "" 400 0 "-" "-" "-"
2025-10-18 19:16:50.560642945  [2025-10-18 19:16:50] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-10-18 19:16:50.584289439  [2025-10-18 19:16:50] frigate.util.config            INFO    : frigate config does not need migration...
2025-10-18 19:16:51.160685975  2025/10/18 19:16:51 [error] 292#292: *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"
2025-10-18 19:16:51.160693527  2025/10/18 19:16:51 [error] 292#292: *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"
2025-10-18 19:16:51.433943447  2025/10/18 19:16:51 [error] 293#293: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 10.1.1.19, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "10.1.1.153:8971"
2025-10-18 19:16:51.433974095  2025/10/18 19:16:51 [error] 293#293: *4 auth request unexpected status: 502 while sending to client, client: 10.1.1.19, server: , request: "GET /ws HTTP/1.1", host: "10.1.1.153:8971"
2025-10-18 19:16:51.434062722  10.1.1.19 - - [18/Oct/2025:19:16:51 -0400] "GET /ws HTTP/1.1" 500 177 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
2025-10-18 19:16:52.645102168  [2025-10-18 19:16:52] frigate.app                    INFO    : Starting Frigate (0.16.2-4d58206)
2025-10-18 19:16:52.662325144  [2025-10-18 19:16:52] peewee_migrate.logs            INFO    : Starting migrations
2025-10-18 19:16:52.663932656  [2025-10-18 19:16:52] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-10-18 19:16:52.682553081  [2025-10-18 19:16:52] frigate.app                    INFO    : Recording process started: 652
2025-10-18 19:16:52.692636376  [2025-10-18 19:16:52] frigate.app                    INFO    : Review process started: 659
2025-10-18 19:16:52.697243005  [2025-10-18 19:16:52] frigate.app                    INFO    : go2rtc process pid: 128
2025-10-18 19:16:52.721088880  [2025-10-18 19:16:52] detector.openvino              INFO    : Starting detection process: 677
2025-10-18 19:16:52.723380786  [2025-10-18 19:16:52] frigate.app                    INFO    : Embedding process started: 680
2025-10-18 19:16:52.727336214  Process detector:openvino:
2025-10-18 19:16:52.727339568  Traceback (most recent call last):
2025-10-18 19:16:52.727342002    File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
2025-10-18 19:16:52.727347215      self.run()
2025-10-18 19:16:52.727350310    File "/opt/frigate/frigate/util/process.py", line 41, in run_wrapper
2025-10-18 19:16:52.727352280      return run(*args, **kwargs)
2025-10-18 19:16:52.727374548             ^^^^^^^^^^^^^^^^^^^^
2025-10-18 19:16:52.727376802    File "/usr/lib/python3.11/multiprocessing/process.py", line 108, in run
2025-10-18 19:16:52.727379318      self._target(*self._args, **self._kwargs)
2025-10-18 19:16:52.727381399    File "/opt/frigate/frigate/object_detection/base.py", line 112, in run_detector
2025-10-18 19:16:52.727383558      object_detector = LocalObjectDetector(detector_config=detector_config)
2025-10-18 19:16:52.727385635                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-10-18 19:16:52.727407212    File "/opt/frigate/frigate/object_detection/base.py", line 57, in __init__
2025-10-18 19:16:52.727409283      self.detect_api = create_detector(detector_config)
2025-10-18 19:16:52.727423802                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-10-18 19:16:52.727426099    File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector
2025-10-18 19:16:52.727427811      return api(detector_config)
2025-10-18 19:16:52.727429401             ^^^^^^^^^^^^^^^^^^^^
2025-10-18 19:16:52.727431548    File "/opt/frigate/frigate/detectors/plugins/openvino.py", line 46, in __init__
2025-10-18 19:16:52.727433551      if not os.path.isfile(detector_config.model.path):
2025-10-18 19:16:52.727435451             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-10-18 19:16:52.727437241    File "<frozen genericpath>", line 30, in isfile
2025-10-18 19:16:52.727452129  TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType
2025-10-18 19:16:52.928906545  [2025-10-18 19:16:52] frigate.app                    INFO    : Output process started: 701
2025-10-18 19:16:52.960527314  [2025-10-18 19:16:52] frigate.app                    INFO    : Camera processor started for West_Yard: 724
2025-10-18 19:16:52.972216619  [2025-10-18 19:16:52] frigate.app                    INFO    : Camera processor started for Front_Yard: 728
2025-10-18 19:16:53.004745953  [2025-10-18 19:16:53] frigate.app                    INFO    : Capture process started for West_Yard: 746
2025-10-18 19:16:53.023421833  [2025-10-18 19:16:53] frigate.app                    INFO    : Capture process started for Front_Yard: 758
2025-10-18 19:16:53.185036228  [2025-10-18 19:16:53] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-10-18 19:16:53.391169694  [2025-10-18 19:16:53] frigate.api.fastapi_app        INFO    : FastAPI started
2025-10-18 19:16:56.259138475  [INFO] Starting go2rtc healthcheck service...
2025-10-18 19:17:08.153316788  10.1.1.19 - - [18/Oct/2025:19:17:08 -0400] "GET /api/profile HTTP/1.1" 200 35 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
2025-10-18 19:17:08.153353965  10.1.1.19 - - [18/Oct/2025:19:17:08 -0400] "GET /api/config HTTP/1.1" 200 18554 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
2025-10-18 19:17:13.180990728  [2025-10-18 19:17:13] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...
2025-10-18 19:17:13.195081514  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2025-10-18 19:17:13.196511992  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2025-10-18 19:17:13.243586075  [INFO] Service NGINX exited with code 0 (by signal 0)
2025-10-18 19:17:13.442339348  [2025-10-18 19:17:13] frigate.app                    INFO    : Stopping...
2025-10-18 19:17:13.445245710  [2025-10-18 19:17:13] frigate.stats.emitter          INFO    : Exiting stats emitter...
2025-10-18 19:17:13.446474413  [2025-10-18 19:17:13] frigate.events.cleanup         INFO    : Exiting event cleanup...
2025-10-18 19:17:13.447362830  [2025-10-18 19:17:13] frigate.storage                INFO    : Exiting storage maintainer...
2025-10-18 19:17:13.452431467  [2025-10-18 19:17:13] frigate.record.cleanup         INFO    : Exiting recording cleanup...
2025-10-18 19:17:13.453132133  [2025-10-18 19:17:13] frigate.ptz.autotrack          INFO    : Exiting autotracker...
2025-10-18 19:17:13.453584182  [2025-10-18 19:17:13] frigate.watchdog               INFO    : Exiting watchdog...
2025-10-18 19:17:13.453834826  [2025-10-18 19:17:13] frigate.ptz.onvif              INFO    : Exiting ONVIF controller...
2025-10-18 19:17:13.454187840  [2025-10-18 19:17:13] frigate.app                    INFO    : Waiting for capture process for West_Yard to stop
2025-10-18 19:17:13.494117146  [2025-10-18 19:17:13] watchdog.West_Yard             INFO    : Terminating the existing ffmpeg process...
2025-10-18 19:17:13.494640406  [2025-10-18 19:17:13] watchdog.West_Yard             INFO    : Waiting for ffmpeg to exit gracefully...
2025-10-18 19:17:13.497618116  [2025-10-18 19:17:13] frigate.track.object_processing INFO    : Exiting object processor...
2025-10-18 19:17:13.902101796  [2025-10-18 19:17:13] watchdog.West_Yard             INFO    : Terminating the existing ffmpeg process...
2025-10-18 19:17:13.902455090  [2025-10-18 19:17:13] watchdog.West_Yard             INFO    : Waiting for ffmpeg to exit gracefully...
2025-10-18 19:17:14.218181594  [2025-10-18 19:17:14] frigate.events.maintainer      INFO    : Exiting event processor...
2025-10-18 19:17:14.433031713  [2025-10-18 19:17:14] frigate.app                    INFO    : Waiting for capture process for Front_Yard to stop
2025-10-18 19:17:14.595169305  [2025-10-18 19:17:14] watchdog.Front_Yard            INFO    : Terminating the existing ffmpeg process...
2025-10-18 19:17:14.595398610  [2025-10-18 19:17:14] watchdog.Front_Yard            INFO    : Waiting for ffmpeg to exit gracefully...
2025-10-18 19:17:14.736770782  [2025-10-18 19:17:14] watchdog.Front_Yard            INFO    : Terminating the existing ffmpeg process...
2025-10-18 19:17:14.736955630  [2025-10-18 19:17:14] watchdog.Front_Yard            INFO    : Waiting for ffmpeg to exit gracefully...
2025-10-18 19:17:14.967891799  [2025-10-18 19:17:14] frigate.app                    INFO    : Waiting for process for West_Yard to stop
2025-10-18 19:17:15.498894572  [2025-10-18 19:17:15] frigate.video                  INFO    : West_Yard: emptying frame queue
2025-10-18 19:17:15.499113197  [2025-10-18 19:17:15] frigate.video                  INFO    : West_Yard: exiting subprocess
2025-10-18 19:17:15.513288624  [2025-10-18 19:17:15] frigate.app                    INFO    : Closing frame queue for West_Yard
2025-10-18 19:17:16.014343953  [2025-10-18 19:17:16] frigate.app                    INFO    : Waiting for process for Front_Yard to stop
2025-10-18 19:17:16.600364601  [2025-10-18 19:17:16] frigate.video                  INFO    : Front_Yard: emptying frame queue
2025-10-18 19:17:16.600646353  [2025-10-18 19:17:16] frigate.video                  INFO    : Front_Yard: exiting subprocess
2025-10-18 19:17:16.615733819  [2025-10-18 19:17:16] frigate.app                    INFO    : Closing frame queue for Front_Yard
2025-10-18 19:17:17.617863729  [2025-10-18 19:17:17] frigate.app                    INFO    : Detection queue closed
2025-10-18 19:17:18.119030990  [2025-10-18 19:17:18] frigate.app                    INFO    : Detected frames queue closed
2025-10-18 19:17:18.620117180  [2025-10-18 19:17:18] frigate.app                    INFO    : Timeline queue closed
2025-10-18 19:17:20.858103674  [2025-10-18 19:17:20] frigate.output.output          INFO    : exiting output process...
2025-10-18 19:17:22.697345872  [2025-10-18 19:17:22] frigate.record.maintainer      INFO    : Exiting recording maintenance...
2025-10-18 19:17:23.509939462  [2025-10-18 19:17:23] frigate.review.maintainer      INFO    : Exiting review maintainer...
2025-10-18 19:17:23.992413644  [2025-10-18 19:17:23] frigate.comms.ws               INFO    : Exiting websocket client...
2025-10-18 19:17:24.384159440  [2025-10-18 19:17:24] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
2025-10-18 19:17:24.469704110  [INFO] Service Frigate exited with code 0 (by signal 0)
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2025-10-18 19:17:24.472757683  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2025-10-18 19:17:24.478204904  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service prepare: stopping
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service prepare successfully stopped
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

Relevant go2rtc log output

info | 2025-10-18 19:12:34 | startup | Preparing new go2rtc config...
info | 2025-10-18 19:12:35 | startup | Starting go2rtc...
info | 2025-10-18 19:12:35 | startup | go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
info | 2025-10-18 19:12:35 | startup | config path=/dev/shm/go2rtc.yaml
info | 2025-10-18 19:12:35 | rtsp    | listen addr=:8554
info | 2025-10-18 19:12:35 | api     | listen addr=:1984
info | 2025-10-18 19:12:35 | webrtc  | listen addr=:8555
info | 2025-10-18 19:12:43 | startup | Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

UNRAID

Install method

Docker Compose

docker-compose file or Docker CLI command

docker run
  -d
  --name='frigate'
  --net='cap1proxy'
  --pids-limit 2048
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="nas"
  -e HOST_CONTAINERNAME="frigate"
  -e 'FRIGATE_RTSP_PASSWORD'='enterpassword'
  -e 'PLUS_API_KEY'=''
  -e 'LIBVA_DRIVER_NAME'='iHD'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8971]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/yayitazale/unraid-templates/main/frigate.png'
  -p '8971:8971/tcp'
  -p '8554:8554/tcp'
  -p '5000:5000/tcp'
  -p '8555:8555/tcp'
  -p '8555:8555/udp'
  -v '/mnt/dockers/appdata/frigate':'/config':'rw'
  -v '/mnt/user/Media/frigate/cctv1/':'/media/frigate':'rw'
  -v '/etc/localtime':'/etc/localtime':'rw'
  --device='/dev/dri/renderD128'
  --shm-size=1G
  --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000
  --restart unless-stopped 'ghcr.io/blakeblackshear/frigate:stable'

041cd33f50a2f4e85ed6c857d519e466c04f261b176e959aa5597a1e47df5ae5

Object Detector

OpenVino

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

NGIX logs:
info | 2025-10-18 19:13:16 | startup | [INFO] Starting NGINX...
error | 2025-10-18 19:13:18 | error | [error] 292#292: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.1.1.19, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth"
error | 2025-10-18 19:13:18 | error | [error] 292#292: *1 auth request unexpected status: 502 while sending to client, client: 10.1.1.19, server: , request: "GET /api/config HTTP/1.1"
info | 2025-10-18 19:13:18 | GET | "GET /api/config HTTP/1.1" 500 177 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
unknown | 2025-10-18 19:13:18 | unknown | 127.0.0.1 - - [18/Oct/2025:19:13:18 -0400] "" 400 0 "-" "-" "-"
error | 2025-10-18 19:13:21 | error | [error] 294#294: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 10.1.1.19, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth"
error | 2025-10-18 19:13:21 | error | [error] 294#294: *4 auth request unexpected status: 502 while sending to client, client: 10.1.1.19, server: , request: "GET /ws HTTP/1.1"
info | 2025-10-18 19:13:21 | GET | "GET /ws HTTP/1.1" 500 177 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
error | 2025-10-18 19:13:21 | error | [error] 292#292: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error | 2025-10-18 19:13:21 | error | [error] 292#292: *6 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error | 2025-10-18 19:13:23 | error | [error] 295#295: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 10.1.1.19, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth"
error | 2025-10-18 19:13:23 | error | [error] 295#295: *8 auth request unexpected status: 502 while sending to client, client: 10.1.1.19, server: , request: "GET /api/profile HTTP/1.1"
info | 2025-10-18 19:13:23 | GET | "GET /api/profile HTTP/1.1" 500 177 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:28 | GET | "GET /api/config HTTP/1.1" 200 18554 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:32 | GET | "GET /ws HTTP/1.1" 101 1190 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:32 | GET | "GET /logs HTTP/1.1" 200 2649 "https://10.1.1.153:8971/config" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:32 | GET | "GET /api/profile HTTP/1.1" 200 35 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:32 | logging | Last message repeated 1 times
info | 2025-10-18 19:13:32 | GET | "GET /api/config HTTP/1.1" 200 18554 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:32 | GET | "GET /api/logs/frigate?start=-100 HTTP/1.1" 200 4414 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"
info | 2025-10-18 19:13:34 | GET | "GET /api/logs/frigate?stream=true HTTP/1.1" 499 0 "https://10.1.1.153:8971/logs" "Mozilla/5.0 (X11; Linux x86_64; rv:144.0) Gecko/20100101 Firefox/144.0" "-"

[hawkeye217]

You haven't specified a model in your config.

You need something like this:

detectors:
  ov:
    type: openvino
    device: GPU

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

See the official documentation: https://docs.frigate.video/configuration/object_detectors/#openvino-detector

[ElectronicEconomy317]

Thank you! I was trying to keep it simple...I guess I go too simple :-) I added a model... so, this is what my config and log look like:
There are still some errors in the log, but different ones now.

mqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-vaapi
cameras:
West_Yard:
ffmpeg:
inputs:
- path: rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
roles:
- detect
- path: rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
Front_Yard:
ffmpeg:
inputs:
- path:
rtsp://cctv:@10.1.1.72:554/cam/realmonitor?channel=1&subtype=1
roles:
- detect
- path:
rtsp://cctv:@10.1.1.72:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
detectors:
openvino:
type: openvino
device: GPU
num_threads: 2
model:
model_type: yolo-generic
width: 320 #
height: 320 #
input_tensor: nchw
input_dtype: float
path: /config/yolov9-s-320.onnx
labelmap_path: /labelmap/coco-80.txt

detect:
enabled: true
width: 1280
height: 720

version: 0.16-0
semantic_search:
enabled: true
model_size: small
#face_recognition:

enabled: true

model_size: large

#lpr:

enabled: true

#classification:

bird:

enabled: true

record:
enabled: true
retain:
days: 45
mode: motion
alerts:
retain:
days: 7
mode: active_objects
detections:
retain:
days: 7
mode: active_objects
objects:
track:

• person
  #- car
• bicycle
• bird
• cat
• dog

info | 2025-10-18 19:31:58 | frigate.app | Output process started: 679
info | 2025-10-18 19:31:58 | frigate.app | Camera processor started for West_Yard: 702
info | 2025-10-18 19:31:58 | frigate.app | Camera processor started for Front_Yard: 706
info | 2025-10-18 19:31:58 | frigate.app | Capture process started for West_Yard: 730
info | 2025-10-18 19:31:58 | frigate.app | Capture process started for Front_Yard: 743
info | 2025-10-18 19:31:58 | frigate.api.fastapi_app | Starting FastAPI app
info | 2025-10-18 19:31:58 | frigate.api.fastapi_app | FastAPI started
info | 2025-10-18 19:32:18 | watchdog.West_Yard | No frames received from West_Yard in 20 seconds. Exiting ffmpeg...
info | 2025-10-18 19:32:18 | watchdog.West_Yard | Waiting for ffmpeg to exit gracefully...
info | 2025-10-18 19:32:18 | watchdog.Front_Yard | No frames received from Front_Yard in 20 seconds. Exiting ffmpeg...
info | 2025-10-18 19:32:18 | watchdog.Front_Yard | Waiting for ffmpeg to exit gracefully...
error | 2025-10-18 19:32:28 | frigate.video | West_Yard: Unable to read frames from ffmpeg process.
error | 2025-10-18 19:32:28 | frigate.video | West_Yard: ffmpeg process is not running. exiting capture thread...
error | 2025-10-18 19:32:28 | watchdog.West_Yard | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-10-18 19:32:28 | ffmpeg.West_Yard.detect | [in#0/rtsp @ 0x557a6dc60f40] Error during demuxing: Connection timed out
info | 2025-10-18 19:32:28 | watchdog.West_Yard | Restarting ffmpeg...
error | 2025-10-18 19:32:28 | frigate.video | Front_Yard: Unable to read frames from ffmpeg process.
error | 2025-10-18 19:32:28 | frigate.video | Front_Yard: ffmpeg process is not running. exiting capture thread...
error | 2025-10-18 19:32:28 | watchdog.Front_Yard | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-10-18 19:32:28 | ffmpeg.Front_Yard.detect | [in#0/rtsp @ 0x55c86ae9ef40] Error during demuxing: Connection timed out
info | 2025-10-18 19:32:28 | watchdog.Front_Yard | Restarting ffmpeg...
error | 2025-10-18 19:32:38 | ffmpeg.West_Yard.record | [aac @ 0x5640768e5c00] Too many bits 8832.000000 > 6144 per frame requested, clamping to max
error | 2025-10-18 19:32:38 | ffmpeg.West_Yard.record | [segment @ 0x564076953800] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
error | 2025-10-18 19:32:38 | ffmpeg.West_Yard.record | [in#0/rtsp @ 0x5640768a8e80] Error during demuxing: Connection timed out
info | 2025-10-18 19:32:38 | watchdog.West_Yard | Terminating the existing ffmpeg process...
info | 2025-10-18 19:32:38 | watchdog.West_Yard | Waiting for ffmpeg to exit gracefully...
error | 2025-10-18 19:32:38 | ffmpeg.Front_Yard.record | [aac @ 0x560502650cc0] Too many bits 8832.000000 > 6144 per frame requested, clamping to max
error | 2025-10-18 19:32:38 | ffmpeg.Front_Yard.record | [segment @ 0x5605026c65c0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
error | 2025-10-18 19:32:38 | ffmpeg.Front_Yard.record | [in#0/rtsp @ 0x56050261ae80] Error during demuxing: Connection timed out
info | 2025-10-18 19:32:38 | watchdog.Front_Yard | Terminating the existing ffmpeg process...
info | 2025-10-18 19:32:38 | watchdog.Front_Yard | Waiting for ffmpeg to exit gracefully...

[hawkeye217]

These errors are now indicating connection problems with your cameras.

I'd suggest setting up go2rtc with restreaming.

@inkeep should be able to reformat your existing config quickly.

[inkeep-ai-assistant[bot]]

Based on your camera connection timeout errors, here's how to set up go2rtc restreaming to reduce camera connections and improve stability.

First, add go2rtc streams to your configuration (1):

go2rtc:
  streams:
    West_Yard:
      - rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
    West_Yard_sub:
      - rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
    Front_Yard:
      - rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    Front_Yard_sub:
      - rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=1

(1)

Then update your camera configuration to use the restreams (1):

cameras:
  West_Yard:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/West_Yard
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/West_Yard_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
  Front_Yard:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/Front_Yard
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/Front_Yard_sub
          input_args: preset-rtsp-restream
          roles:
            - detect

(1)

This configuration reduces connections to your cameras by having go2rtc make one connection to each camera stream, then Frigate connects to the local restream (1). This should help resolve the connection timeout issues you're experiencing.

📚 Sources:

1. Restream

---

Have another question? Just tag @inkeep.

[ElectronicEconomy317]

WOW... love that bot! :-) I feel like I am getting close...but just not there yet. So, I updated my config to this:

mqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-vaapi
go2rtc:
streams:
West_Yard:
- rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
West_Yard_sub:
- rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
Front_Yard:
- rtsp://cctv:b2RS82#9D$4zxBnAkG7XJ#[email protected]:554/cam/realmonitor?channel=1&subtype=0
Front_Yard_sub:
- rtsp://cctv:b2RS82#9D$4zxBnAkG7XJ#[email protected]:554/cam/realmonitor?channel=1&subtype=1
cameras:
West_Yard:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/West_Yard
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/West_Yard_sub
input_args: preset-rtsp-restream
roles:
- detect
Front_Yard:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/Front_Yard
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/Front_Yard_sub
input_args: preset-rtsp-restream
roles:
- detect
detectors:
openvino:
type: openvino
device: GPU
num_threads: 2
openvino2:
type: openvino
device: GPU
num_threads: 2
openvino3:
type: openvino
device: GPU
num_threads: 2
model:
model_type: yolo-generic
width: 320 # <--- should match the imgsize set during model export
height: 320 # <--- should match the imgsize set during model export
input_tensor: nchw
input_dtype: float
path: /config/yolov9-s-320.onnx
labelmap_path: /labelmap/coco-80.txt

detect:
enabled: true
width: 1280
height: 720

version: 0.16-0
semantic_search:
enabled: true
model_size: small
#face_recognition:

enabled: true

model_size: large

#lpr:

enabled: true

#classification:

bird:

enabled: true

record:
enabled: true
retain:
days: 45
mode: motion
alerts:
retain:
days: 7
mode: active_objects
detections:
retain:
days: 7
mode: active_objects
objects:
track:

• person
  #- car
• bicycle
• bird
• cat
• dog

Here are the logs:

error | 2025-10-18 20:14:39 | frigate.video | Front_Yard: ffmpeg process is not running. exiting capture thread...
error | 2025-10-18 20:14:49 | watchdog.Front_Yard | Ffmpeg process crashed unexpectedly for Front_Yard.
error | 2025-10-18 20:14:49 | watchdog.Front_Yard | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-10-18 20:14:49 | ffmpeg.Front_Yard.detect | [rtsp @ 0x557a28d6f080] method DESCRIBE failed: 404 Not Found
error | 2025-10-18 20:14:49 | ffmpeg.Front_Yard.detect | [in#0 @ 0x557a28d6ed80] Error opening input: Server returned 404 Not Found
error | 2025-10-18 20:14:49 | ffmpeg.Front_Yard.detect | Error opening input file rtsp://127.0.0.1:8554/Front_Yard_sub.
error | 2025-10-18 20:14:49 | ffmpeg.Front_Yard.detect | Error opening input files: Server returned 404 Not Found
info | 2025-10-18 20:14:49 | watchdog.Front_Yard | Restarting ffmpeg...
error | 2025-10-18 20:14:49 | watchdog.Front_Yard | No new recording segments were created for Front_Yard in the last 120s. restarting the ffmpeg record process...
info | 2025-10-18 20:14:49 | watchdog.Front_Yard | Terminating the existing ffmpeg process...
info | 2025-10-18 20:14:49 | watchdog.Front_Yard | Waiting for ffmpeg to exit gracefully...
error | 2025-10-18 20:14:49 | frigate.video | Front_Yard: Unable to read frames from ffmpeg process.
error | 2025-10-18 20:14:49 | frigate.video | Front_Yard: ffmpeg process is not running. exiting capture thread...
error | 2025-10-18 20:14:59 | watchdog.Front_Yard | Ffmpeg process crashed unexpectedly for Front_Yard.
error | 2025-10-18 20:14:59 | watchdog.Front_Yard | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-10-18 20:14:59 | ffmpeg.Front_Yard.detect | [rtsp @ 0x55a652c9e080] method DESCRIBE failed: 404 Not Found
error | 2025-10-18 20:14:59 | ffmpeg.Front_Yard.detect | [in#0 @ 0x55a652c9dd80] Error opening input: Server returned 404 Not Found
error | 2025-10-18 20:14:59 | ffmpeg.Front_Yard.detect | Error opening input file rtsp://127.0.0.1:8554/Front_Yard_sub.
error | 2025-10-18 20:14:59 | ffmpeg.Front_Yard.detect | Error opening input files: Server returned 404 Not Found
info | 2025-10-18 20:14:59 | watchdog.Front_Yard | Restarting ffmpeg...
error | 2025-10-18 20:14:59 | watchdog.Front_Yard | No new recording segments were created for Front_Yard in the last 120s. restarting the ffmpeg record process...
info | 2025-10-18 20:14:59 | watchdog.Front_Yard | Terminating the existing ffmpeg process...
info | 2025-10-18 20:14:59 | watchdog.Front_Yard | Waiting for ffmpeg to exit gracefully...
error | 2025-10-18 20:14:59 | frigate.video | Front_Yard: Unable to read frames from ffmpeg process.
error | 2025-10-18 20:14:59 | frigate.video | Front_Yard: ffmpeg process is not running. exiting capture thread...
error | 2025-10-18 20:15:09 | watchdog.Front_Yard | Ffmpeg process crashed unexpectedly for Front_Yard.
error | 2025-10-18 20:15:09 | watchdog.Front_Yard | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-10-18 20:15:09 | ffmpeg.Front_Yard.detect | [rtsp @ 0x55e4abaea080] method DESCRIBE failed: 404 Not Found
error | 2025-10-18 20:15:09 | ffmpeg.Front_Yard.detect | [in#0 @ 0x55e4abae9d80] Error opening input: Server returned 404 Not Found
error | 2025-10-18 20:15:09 | ffmpeg.Front_Yard.detect | Error opening input file rtsp://127.0.0.1:8554/Front_Yard_sub.
error | 2025-10-18 20:15:09 | ffmpeg.Front_Yard.detect | Error opening input files: Server returned 404 Not Found

[hawkeye217]

@inkeep

The go2rtc streams are failing. Suggest the ffmpeg module in go2rtc

[inkeep-ai-assistant[bot]]

The 404 errors indicate go2rtc is having trouble with your camera streams. Your complex password with special characters needs URL encoding, and you should try the FFmpeg module in go2rtc for better compatibility (1).

First, handle your complex password by URL-encoding it. Go2rtc expects URL-encoded passwords (2):

go2rtc:
  streams:
    West_Yard:
      - rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
    West_Yard_sub:
      - rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
    Front_Yard:
      - ffmpeg:rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    Front_Yard_sub:
      - ffmpeg:rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=1

(1)

Some camera streams need the ffmpeg module in go2rtc for compatibility, though this has slower startup times (1):

go2rtc:
  streams:
    West_Yard:
      - ffmpeg:rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=0
    West_Yard_sub:
      - ffmpeg:rtsp://10.1.1.71:554/cam/realmonitor?channel=1&subtype=1
    Front_Yard:
      - ffmpeg:rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=0
    Front_Yard_sub:
      - ffmpeg:rtsp://cctv:[email protected]:554/cam/realmonitor?channel=1&subtype=1

(1)

Use urlencoder.org to encode your password b2RS82#9D$4zxBnAkG7XJ#R8wb3bm7s (2).

To troubleshoot, navigate to port 1984 in your browser to access go2rtc's web interface and click stream for each camera to verify the streams are being received (1).

📚 Sources:

1. Configuring go2rtc
2. Restream

---

Have another question? Just tag @inkeep.

[ElectronicEconomy317]

Thank you @hawkeye217 and @inkeep!!! That did the trick! All working nicely now! :-) Frigate is awesome, the more I learn, the more I love it! Now its time to play with some different models... I saw a great post earlier.

[hawkeye217]

Great, glad it's working now. Let us know if there's anything else we can help with!

[inkeep-ai-assistant[bot]]

Great to hear your Frigate setup is working well with the Intel Arc A310! Since you're interested in exploring different models, here are your options:

For your OpenVINO detector with Intel Arc GPU, you can use several model types (1):

YOLOv9 (Recommended for Intel GPUs):

model:
  model_type: yolo-generic
  width: 320
  height: 320
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/yolo.onnx
  labelmap_path: /labelmap/coco-80.txt

(1)

YOLO-NAS:

model:
  model_type: yolonas
  width: 320
  height: 320
  input_tensor: nchw
  input_dtype: float
  path: /config/yolo_nas_s.onnx
  labelmap_path: /labelmap/coco-80.txt

(1)

RF-DETR (for discrete Arc Graphics Cards):

model:
  model_type: rfdetr
  width: 320
  height: 320
  input_tensor: nchw
  input_dtype: float
  path: /config/model_cache/rfdetr.onnx

(1)

Frigate+ Models (Highly Recommended):
If you want the best accuracy, consider Frigate+ models (2). For Intel hardware, yolov9 models are recommended (2). You can use them with:

model:
  path: plus://<your_model_id>

(3)

Frigate+ models generally have much higher scores than default models, so you'll need to increase your threshold and min_score values (3).

The models are automatically downloaded to /config/model_cache/ when specified (1). Make sure your model dimensions match what you configure in the YAML (1).

📚 Sources:

1. Supported Hardware
2. Models
3. Requesting your first model

---

Have another question? Just tag @inkeep.