[Detector Support]: Frigate crashes when initially loading with docker compose, but then somehow works in the background without crashing? #13161

mike6789 · 2024-08-18T13:59:33Z

mike6789
Aug 18, 2024

Describe the problem you are having

Hi there,

I do not understand what is happening. I have an RPi5 with a Coral USB stick. When I launch Frigate with docker compose, it will error out and look like it quit on failure (see logs below)... HOWEVER, somehow, Frigate manages to boot up in the background and work perfectly (the Coral accelerator is working)???

I would like to be able to just have docker compose load Frigate without error, or at least understand what mechanism is having Frigate recover.

Thank you

Version

0.14.0-da913d8

Frigate config file

ffmpeg:
  hwaccel_args:
    - -c:v:1
    - hevc_v4l2m2m

detectors:
  coral:
    type: edgetpu
    device: usb

go2rtc:
  streams:
    mycamera: ffmpeg:http://*****:*****@192.168.1.87/video.cgi#video=h264#hardware
    reolink: ffmpeg:rtsp://*****:*****@192.168.1.76:554/Preview_01_sub
mqtt:
  enabled: true
  host: 192.168.1.74
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: *****
  password: *****
  stats_interval: 60

record:
  enabled: True
  retain:
    days: 3
    mode: all
  events:
    retain:
      default: 30
      mode: motion

detect:
  enabled: True

logger:
  default: info
  logs:
    frigate.comms.mqtt: debug
    frigate.mqtt: debug
    frigate.object_detection: debug
    detector.cpu: debug

cameras:
  mycamera:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/mycamera
          roles:
            - detect
            - record
    detect:
      width: 640
      height: 480
      fps: 10
    objects:
      track:
        - person
  reolink:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/reolink
          roles:
            - record

version: 0.14
camera_groups:
  Bird's_Eye:
    order: 1
    icon: LuTwitter
    cameras: birdseye

docker-compose file or Docker CLI command

ersion: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "256mb"
    devices:
      - /dev/bus/usb:/dev/bus/usb #Used for Coral if Available
      - /dev/video19:/dev/video19  #Map the Pi hardware acceleration
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/*****/frigate-nvr/config.yml:/config/config.yml
      - /home/*****/frigate-nvr/storage:/media/frigate
      - type: tmpfs #Remove this if using a Pi with 2GB or Less RAM
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "*****"

Relevant log output

[+] Running 1/0
 ✔ Container frigate  Running                                                                                                                                                                                                                                                                           0.0s
Attaching to frigate
frigate  | 2024-08-18 06:52:33.016222706  [INFO] Starting Frigate...
frigate  | 2024-08-18 06:52:33.016845865  [INFO] Preparing new go2rtc config...
frigate  | 2024-08-18 06:52:34.323961726  [INFO] Starting go2rtc...
frigate  | 2024-08-18 06:52:34.426392871  06:52:34.424 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
frigate  | 2024-08-18 06:52:34.426400834  06:52:34.424 INF config path=/dev/shm/go2rtc.yaml
frigate  | 2024-08-18 06:52:34.426403223  06:52:34.425 INF [rtsp] listen addr=:8554
frigate  | 2024-08-18 06:52:34.426404797  06:52:34.425 INF [webrtc] listen addr=:8555/tcp
frigate  | 2024-08-18 06:52:34.426820020  06:52:34.426 INF [api] listen addr=:1984
frigate  | 2024-08-18 06:52:35.435511326  2024/08/18 06:52:35 [error] 224#224: *6 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.74, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:35.435520382  2024/08/18 06:52:35 [error] 224#224: *6 auth request unexpected status: 502 while sending to client, client: 192.168.1.74, server: , request: "GET /api/stats HTTP/1.1", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:36.042140146  2024/08/18 06:52:36 [error] 225#225: *8 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"
frigate  | 2024-08-18 06:52:36.042169295  2024/08/18 06:52:36 [error] 225#225: *8 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"
frigate  | 2024-08-18 06:52:37.574347144  [INFO] Starting go2rtc healthcheck service...
frigate  | 2024-08-18 06:52:40.434408780  2024/08/18 06:52:40 [error] 222#222: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:40.434436967  2024/08/18 06:52:40 [error] 222#222: *10 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:41.667274448  2024/08/18 06:52:41 [error] 222#222: *12 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"
frigate  | 2024-08-18 06:52:41.667445067  2024/08/18 06:52:41 [error] 222#222: *12 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"
frigate  | 2024-08-18 06:52:42.210939958  [2024-08-18 06:52:42] frigate.app                    INFO    : Starting Frigate (0.14.0-da913d8)
frigate  | 2024-08-18 06:52:42.211719013  [2024-08-18 06:52:42] frigate.util.config            INFO    : Checking if frigate config needs migration...
frigate  | 2024-08-18 06:52:42.234803257  [2024-08-18 06:52:42] frigate.util.config            INFO    : frigate config does not need migration...
frigate  | 2024-08-18 06:52:45.437769384  2024/08/18 06:52:45 [error] 222#222: *14 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:45.437793144  2024/08/18 06:52:45 [error] 222#222: *14 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:46.732320591  2024/08/18 06:52:46 [error] 222#222: *16 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"
frigate  | 2024-08-18 06:52:46.732348648  2024/08/18 06:52:46 [error] 222#222: *16 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"
frigate  | 2024-08-18 06:52:50.435034127  2024/08/18 06:52:50 [error] 222#222: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.74, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:50.435061795  2024/08/18 06:52:50 [error] 222#222: *18 auth request unexpected status: 502 while sending to client, client: 192.168.1.74, server: , request: "GET /api/stats HTTP/1.1", host: "frigate.local:5000"
frigate  | 2024-08-18 06:52:51.810036087  2024/08/18 06:52:51 [error] 222#222: *20 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"
frigate  | 2024-08-18 06:52:51.810068848  2024/08/18 06:52:51 [error] 222#222: *20 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"
frigate  | 2024-08-18 06:52:53.488496187  [2024-08-18 06:52:53] peewee_migrate.logs            INFO    : Starting migrations
frigate  | 2024-08-18 06:52:53.489836988  [2024-08-18 06:52:53] peewee_migrate.logs            INFO    : There is nothing to migrate
frigate  | 2024-08-18 06:52:54.483282713  [2024-08-18 06:52:54] frigate.app                    INFO    : Recording process started: 445
frigate  | 2024-08-18 06:52:54.495088150  [2024-08-18 06:52:54] frigate.app                    INFO    : Recording process started: 447
frigate  | 2024-08-18 06:52:54.506221205  [2024-08-18 06:52:54] frigate.app                    INFO    : go2rtc process pid: 177
frigate  | 2024-08-18 06:52:54.517631051  [2024-08-18 06:52:54] frigate.comms.mqtt             DEBUG   : MQTT connected
frigate  | 2024-08-18 06:52:54.548239405  [2024-08-18 06:52:54] detector.coral                 INFO    : Starting detection process: 474
frigate  | 2024-08-18 06:52:54.568161410  [2024-08-18 06:52:54] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
frigate  | 2024-08-18 06:53:22.852272583  [2024-08-18 06:52:54] frigate.app                    INFO    : Output process started: 476
frigate  | 2024-08-18 06:53:22.852648747  [2024-08-18 06:53:00] frigate.video                  ERROR   : reolink: Unable to read frames from ffmpeg process.
frigate  | 2024-08-18 06:53:22.852655081  [2024-08-18 06:53:00] frigate.video                  ERROR   : reolink: Unable to read frames from ffmpeg process.
frigate  | 2024-08-18 06:53:22.852927019  [2024-08-18 06:53:00] frigate.video                  ERROR   : reolink: ffmpeg process is not running. exiting capture thread...
frigate  | 2024-08-18 06:53:22.853418485  [2024-08-18 06:53:14] watchdog.reolink               ERROR   : Ffmpeg process crashed unexpectedly for reolink.
frigate  | 2024-08-18 06:53:22.853641698  Process detector:coral:
frigate  | 2024-08-18 06:53:22.854168906  [2024-08-18 06:53:14] watchdog.reolink               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
frigate  | 2024-08-18 06:53:22.855858869  [2024-08-18 06:53:14] ffmpeg.reolink.detect          ERROR   : rtsp://127.0.0.1:8554/reolink: Invalid data found when processing input
frigate  | 2024-08-18 06:53:22.855867314  [2024-08-18 06:53:20] frigate.video                  ERROR   : reolink: Unable to read frames from ffmpeg process.
frigate  | 2024-08-18 06:53:22.855870036  [2024-08-18 06:53:20] frigate.video                  ERROR   : reolink: ffmpeg process is not running. exiting capture thread...
frigate  | 2024-08-18 06:53:22.855905352  [2024-08-18 06:53:22] frigate.detectors.plugins.edgetpu_tfl ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
frigate  | 2024-08-18 06:53:22.856013487  [2024-08-18 06:52:54] frigate.app                    INFO    : Camera processor started for mycamera: 505
frigate  | 2024-08-18 06:53:22.856130770  [2024-08-18 06:52:54] frigate.app                    INFO    : Camera processor started for reolink: 511
frigate  | 2024-08-18 06:53:22.856176475  [2024-08-18 06:52:54] frigate.app                    INFO    : Capture process started for mycamera: 516
frigate  | 2024-08-18 06:53:22.856421968  [2024-08-18 06:52:54] frigate.app                    INFO    : Capture process started for reolink: 524
frigate  | 2024-08-18 06:53:23.799027036  Traceback (most recent call last):
frigate  | 2024-08-18 06:53:23.799055352    File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
frigate  | 2024-08-18 06:53:23.799057370      delegate = Delegate(library, options)
frigate  | 2024-08-18 06:53:23.799059296    File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__
frigate  | 2024-08-18 06:53:23.799060704      raise ValueError(capture.message)
frigate  | 2024-08-18 06:53:23.799150356  ValueError
frigate  | 2024-08-18 06:53:23.799151949
frigate  | 2024-08-18 06:53:23.799153560  During handling of the above exception, another exception occurred:
frigate  | 2024-08-18 06:53:23.799157060
frigate  | 2024-08-18 06:53:23.799158356  Traceback (most recent call last):
frigate  | 2024-08-18 06:53:23.799167505    File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
frigate  | 2024-08-18 06:53:23.799168598      self.run()
frigate  | 2024-08-18 06:53:23.799235897    File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run
frigate  | 2024-08-18 06:53:23.799238841      self._target(*self._args, **self._kwargs)
frigate  | 2024-08-18 06:53:23.799249601    File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector
frigate  | 2024-08-18 06:53:23.799251305      object_detector = LocalObjectDetector(detector_config=detector_config)
frigate  | 2024-08-18 06:53:23.799252898    File "/opt/frigate/frigate/object_detection.py", line 53, in __init__
frigate  | 2024-08-18 06:53:23.799254305      self.detect_api = create_detector(detector_config)
frigate  | 2024-08-18 06:53:23.799255990    File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector
frigate  | 2024-08-18 06:53:23.799257194      return api(detector_config)
frigate  | 2024-08-18 06:53:23.799499205    File "/opt/frigate/frigate/detectors/plugins/edgetpu_tfl.py", line 41, in __init__
frigate  | 2024-08-18 06:53:23.799504520      edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
frigate  | 2024-08-18 06:53:23.799506446    File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
frigate  | 2024-08-18 06:53:23.799508020      raise ValueError('Failed to load delegate from {}\n{}'.format(
frigate  | 2024-08-18 06:53:23.799509501  ValueError: Failed to load delegate from libedgetpu.so.1.0
frigate  | 2024-08-18 06:53:23.799510409
frigate  | 2024-08-18 06:53:24.811859027  [2024-08-18 06:53:24] watchdog.reolink               ERROR   : Ffmpeg process crashed unexpectedly for reolink.
frigate  | 2024-08-18 06:53:24.812417366  [2024-08-18 06:53:24] watchdog.reolink               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
frigate  | 2024-08-18 06:53:24.812426922  [2024-08-18 06:53:24] ffmpeg.reolink.detect          ERROR   : rtsp://127.0.0.1:8554/reolink: Invalid data found when processing input
frigate  | 2024-08-18 06:53:25.018607343  [2024-08-18 06:53:25] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...
frigate  | s6-rc: info: service legacy-services: stopping
frigate  | s6-rc: info: service legacy-services successfully stopped
frigate  | s6-rc: info: service go2rtc-healthcheck: stopping
frigate  | s6-rc: info: service certsync: stopping
frigate  | 2024-08-18 06:53:25.685885655  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
frigate  | 2024-08-18 06:53:25.847551226  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
frigate  | s6-rc: info: service go2rtc-healthcheck successfully stopped
frigate  | s6-rc: info: service certsync successfully stopped
frigate  | s6-rc: info: service nginx: stopping
frigate  | s6-rc: info: service certsync-log: stopping
frigate  | s6-rc: info: service certsync-log successfully stopped
frigate  | 2024-08-18 06:53:27.453174579  [INFO] Service NGINX exited with code 0 (by signal 0)
frigate  | s6-rc: info: service nginx successfully stopped
frigate  | s6-rc: info: service nginx-log: stopping
frigate  | s6-rc: info: service frigate: stopping
frigate  | 2024-08-18 06:53:27.817746202  [2024-08-18 06:53:27] frigate.app                    INFO    : Flask has exited...
frigate  | 2024-08-18 06:53:27.818227408  [2024-08-18 06:53:27] frigate.app                    INFO    : Stopping...
frigate  | 2024-08-18 06:53:27.819327141  [2024-08-18 06:53:27] frigate.ptz.autotrack          INFO    : Exiting autotracker...
frigate  | 2024-08-18 06:53:27.819359142  [2024-08-18 06:53:27] frigate.events.cleanup         INFO    : Exiting event cleanup...
frigate  | 2024-08-18 06:53:27.819630487  [2024-08-18 06:53:27] frigate.stats.emitter          INFO    : Exiting stats emitter...
frigate  | 2024-08-18 06:53:27.819698398  [2024-08-18 06:53:27] frigate.storage                INFO    : Exiting storage maintainer...
frigate  | 2024-08-18 06:53:27.820208790  [2024-08-18 06:53:27] frigate.watchdog               INFO    : Exiting watchdog...
frigate  | 2024-08-18 06:53:27.820490580  [2024-08-18 06:53:27] frigate.record.cleanup         INFO    : Exiting recording cleanup...
frigate  | 2024-08-18 06:53:27.821306949  [2024-08-18 06:53:27] frigate.app                    INFO    : Waiting for capture process for mycamera to stop
frigate  | 2024-08-18 06:53:27.822144300  [2024-08-18 06:53:27] watchdog.mycamera              INFO    : Terminating the existing ffmpeg process...
frigate  | 2024-08-18 06:53:27.822561633  [2024-08-18 06:53:27] watchdog.mycamera              INFO    : Waiting for ffmpeg to exit gracefully...
frigate  | 2024-08-18 06:53:27.853016901  [2024-08-18 06:53:27] frigate.app                    INFO    : Waiting for capture process for reolink to stop
frigate  | 2024-08-18 06:53:27.853445198  [2024-08-18 06:53:27] watchdog.reolink               INFO    : Terminating the existing ffmpeg process...
frigate  | 2024-08-18 06:53:27.854503929  [2024-08-18 06:53:27] watchdog.reolink               INFO    : Waiting for ffmpeg to exit gracefully...
frigate  | 2024-08-18 06:53:27.859847754  [2024-08-18 06:53:27] frigate.app                    INFO    : Waiting for process for mycamera to stop
frigate  | 2024-08-18 06:53:28.044297381  [2024-08-18 06:53:28] frigate.events.maintainer      INFO    : Exiting event processor...
frigate  | 2024-08-18 06:53:28.687082413  [2024-08-18 06:53:28] frigate.object_processing      INFO    : Exiting object processor...
frigate  | s6-rc: info: service nginx-log successfully stopped
frigate  | 2024-08-18 06:53:31.659644183  [2024-08-18 06:53:31] frigate.video                  INFO    : mycamera: emptying frame queue
frigate  | 2024-08-18 06:53:31.660445292  [2024-08-18 06:53:31] frigate.video                  INFO    : mycamera: exiting subprocess
frigate  | 2024-08-18 06:53:31.665480436  [2024-08-18 06:53:31] frigate.app                    INFO    : Closing frame queue for mycamera
frigate  | 2024-08-18 06:53:32.166241615  [2024-08-18 06:53:32] frigate.app                    INFO    : Waiting for process for reolink to stop
frigate  | 2024-08-18 06:53:32.812591894  [2024-08-18 06:53:32] frigate.video                  INFO    : reolink: emptying frame queue
frigate  | 2024-08-18 06:53:32.812598154  [2024-08-18 06:53:32] frigate.video                  INFO    : reolink: exiting subprocess
frigate  | 2024-08-18 06:53:32.816971325  [2024-08-18 06:53:32] frigate.app                    INFO    : Closing frame queue for reolink
frigate  | 2024-08-18 06:53:33.818630953  [2024-08-18 06:53:33] frigate.app                    INFO    : Detection queue closed
frigate  | 2024-08-18 06:53:34.319711955  [2024-08-18 06:53:34] frigate.app                    INFO    : Detected frames queue closed
frigate  | 2024-08-18 06:53:34.820574222  [2024-08-18 06:53:34] frigate.app                    INFO    : Timeline queue closed
frigate  | 2024-08-18 06:53:36.217054919  [2024-08-18 06:53:36] frigate.output.output          INFO    : exiting output process...
frigate  | 2024-08-18 06:53:39.543066821  [2024-08-18 06:53:39] frigate.record.maintainer      INFO    : Exiting recording maintenance...
frigate  | 2024-08-18 06:53:41.559679208  [INFO] Service Frigate exited with code 0 (by signal 0)
frigate  | 2024-08-18 06:53:41.560434666  /usr/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 6 leaked shared_memory objects to clean up at shutdown
frigate  | 2024-08-18 06:53:41.560442704    warnings.warn('resource_tracker: There appear to be %d '
frigate  | s6-rc: info: service frigate successfully stopped
frigate  | s6-rc: info: service go2rtc: stopping
frigate  | s6-rc: info: service frigate-log: stopping
frigate  | 2024-08-18 06:53:41.565738766  exit with signal: terminated
frigate  | 2024-08-18 06:53:41.576538213  [INFO] The go2rtc service exited with code 0 (by signal 0)
frigate  | s6-rc: info: service go2rtc successfully stopped
frigate  | s6-rc: info: service go2rtc-log: stopping
frigate  | s6-rc: info: service frigate-log successfully stopped
frigate  | s6-rc: info: service go2rtc-log successfully stopped
frigate  | s6-rc: info: service log-prepare: stopping
frigate  | s6-rc: info: service s6rc-fdholder: stopping
frigate  | s6-rc: info: service log-prepare successfully stopped
frigate  | s6-rc: info: service legacy-cont-init: stopping
frigate  | s6-rc: info: service s6rc-fdholder successfully stopped
frigate  | s6-rc: info: service legacy-cont-init successfully stopped
frigate  | s6-rc: info: service fix-attrs: stopping
frigate  | s6-rc: info: service fix-attrs successfully stopped
frigate  | s6-rc: info: service s6rc-oneshot-runner: stopping
frigate  | s6-rc: info: service s6rc-oneshot-runner successfully stopped
frigate exited with code 0

Operating system

Debian

Install method

Docker Compose

Object Detector

Coral

Any other information that may be helpful

No response

NickM-27 · 2024-08-18T15:35:37Z

NickM-27
Aug 18, 2024
Collaborator Sponsor

your docker compose file means unless you stop it, frigate will continue to try to start up over and over

what indication do you have that frigate is running correctly without issues?

4 replies

mike6789 Aug 18, 2024
Author

Ohh I see, I am new to docker so I didn't know that. Is there a way that I can have more control over it? Docker in general seems to be slowing down my system when it's running as a service.

Frigate works because I can access the UI and see that the detections are indeed happening on the coral:

And all my recordings are good.

The only problem I notice is that detections are slow on one camera (but not the other). Not sure why yet. It seems that the green boxes for the ROI sent to the detector do not show up in the debug screen reliably...

NickM-27 Aug 19, 2024
Collaborator Sponsor

you can change the restart_mode

what do you mean by detections are slow?

mike6789 Aug 20, 2024
Author

After realizing I don't need to run "docker compose up" every time I restart my pi, and Frigate works, I'm happy with how it is... although I don't understand why that error happens.

Anyway, When I walk in front of the camera, it might not detect for like 5-10 seconds sometimes :(

NickM-27 Aug 20, 2024
Collaborator Sponsor

Maybe motion detection needs to be tuned

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Detector Support]: Frigate crashes when initially loading with docker compose, but then somehow works in the background without crashing? #13161

{{title}}

Replies: 1 comment 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Detector Support]: Frigate crashes when initially loading with docker compose, but then somehow works in the background without crashing? #13161

mike6789 Aug 18, 2024

Describe the problem you are having

Version

Frigate config file

docker-compose file or Docker CLI command

Relevant log output

Operating system

Install method

Object Detector

Any other information that may be helpful

Replies: 1 comment · 4 replies

NickM-27 Aug 18, 2024 Collaborator Sponsor

mike6789 Aug 18, 2024 Author

NickM-27 Aug 19, 2024 Collaborator Sponsor

mike6789 Aug 20, 2024 Author

NickM-27 Aug 20, 2024 Collaborator Sponsor

mike6789
Aug 18, 2024

Replies: 1 comment 4 replies

NickM-27
Aug 18, 2024
Collaborator Sponsor

mike6789 Aug 18, 2024
Author

NickM-27 Aug 19, 2024
Collaborator Sponsor

mike6789 Aug 20, 2024
Author

NickM-27 Aug 20, 2024
Collaborator Sponsor