[Support]: Unable to start Frigate 0.14 with fresh DB #12943

andrewhack · 2024-08-11T08:30:49Z

andrewhack
Aug 11, 2024

Describe the problem you are having

Unable to start 0.14 with fresh DB. The configuration was migrated
The configuration is working in 0.13

docker container:
docker run -d --name=frigate-nvr1 --log-driver=splunk --log-opt splunk-token=***** --log-opt splunk-url=http://:8088 --log-opt splunk-verify-connection=false --restart=unless-stopped --device /dev/apex_0 --shm-size=256m -v /home/frigate/db:/db -v /storage_zm/frigate/nvr1:/media/frigate -v /home/frigate/config:/config -v /etc/localtime:/etc/localtime:ro -e FRIGATE_RTSP_PASSWORD='' -p 5000:5000 -p 8554:8554 -p 8555:8555/tcp -p 8555:8555/udp ghcr.io/blakeblackshear/frigate:0.14.0

Version

0.14

Frigate config file

tls:
  enabled: false
mqtt:
  host: *****
  user: *****
  password: *****
  client_id: frigatenvr1
  topic_prefix: frigatenvr1
database:
  path: /db/frigate-nvr1.db
detectors:
  coral:
    type: edgetpu
    device: pci
objects:
  track:
    - cat
    - person
    - bicycle
    - motorcycle
    - car
    - truck
motion:
  lightning_threshold: 0.8
  contour_area: 10
  improve_contrast: true
  mqtt_off_delay: 30
timestamp_style:
  position: tl
  format: '%m/%d/%Y %H:%M:%S'
  thickness: 2
birdseye:
  enabled: true
  restream: false
  width: 1280
  height: 720
  quality: 8
  mode: objects
record:
  enabled: true
minimize i/o
  expire_interval: 60
  retain:
    days: 0
    mode: all
  events:
    pre_capture: 5
    post_capture: 5
    objects:
      - person
      - car
    retain:
      default: 10
      mode: motion
      objects:
        person: 60
        car: 30
go2rtc:
  streams:
    test:
      - ffmpeg:rtsp://admin:****@****:554/stream0#video=copy#audio=copy#audio=aac
cameras:
  test:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/test
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
      output_args:
        record: preset-record-generic-audio-aac
    detect:
      width: 1280
      height: 720
    snapshots:
      quality: 100
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 10
      required_zones:
        - zone_test
    objects:
      filters:
        person:
          mask:
            - 236,240,1280,127,1280,0,954,0,149,0,0,0,0,552,156,378
            - 1280,165,877,157,981,431,1280,647
        car:
          mask:
            - 236,240,1280,127,1280,0,954,0,149,0,0,0,0,552,156,378
            - 1280,165,877,157,981,431,1280,647
    motion:
      mask:
        - 236,240,1280,127,1280,0,954,0,149,0,0,0,0,552,156,378
        - 1280,165,877,157,981,431,1280,647
    zones:
      zone_test:
        coordinates: 1280,720,1280,653,973,441,895,213,813,194,270,268,0,570,0,720
        objects:
          - person
          - car
          - truck
          - bicycle
          - motorcycle
    onvif:
      host: *******
      port: 80
      user: admin
      password: ******
      autotracking:
        enabled: true
        calibrate_on_startup: true
        zooming: absolute
        zoom_factor: 0.3
        track:
          - person
        required_zones:
          - zone_test
        return_preset: home
        timeout: 10
version: 0.14

Relevant log output

s6-rc: info: service nginx-log successfully stopped
2024-08-11 11:14:58.122525460  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-08-11 11:14:58.129039620  [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-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
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 go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-08-11 11:16:02.800732394  [INFO] Preparing new go2rtc config...
2024-08-11 11:16:02.802703593  [INFO] Preparing Frigate...
2024-08-11 11:16:02.810570363  [INFO] Starting NGINX...
2024-08-11 11:16:02.818083396  [INFO] Starting Frigate...
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
2024-08-11 11:16:02.985837125  [INFO] Starting certsync...
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-08-11 11:16:03.262674240  [INFO] Starting go2rtc...
2024-08-11 11:16:03.378470773  11:16:03.378 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-08-11 11:16:03.378477046  11:16:03.378 INF config path=/dev/shm/go2rtc.yaml
2024-08-11 11:16:03.379281431  11:16:03.379 INF [rtsp] listen addr=:8554
2024-08-11 11:16:03.379489098  11:16:03.379 INF [api] listen addr=:1984
2024-08-11 11:16:03.379491779  11:16:03.379 INF [webrtc] listen addr=:8555/tcp
2024-08-11 11:16:04.754769876  [2024-08-11 11:16:04] frigate.app                    INFO    : Starting Frigate (0.14.0-da913d8)
2024-08-11 11:16:04.755010124  [2024-08-11 11:16:04] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-08-11 11:16:04.856416035  [2024-08-11 11:16:04] frigate.util.config            INFO    : frigate config does not need migration...
2024-08-11 11:16:04.944060858  [2024-08-11 11:16:04] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2024-08-11 11:16:04.995363759  '/db/frigate-nvr1.db' and '/db/frigate-nvr1.db' are the same file
2024-08-11 11:16:04.995939740  [2024-08-11 11:16:04] frigate.app                    INFO    : Making backup of DB before migrations...
2024-08-11 11:16:06.308270466  [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-11 11:16:06.318046608  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-08-11 11:16:06.319125399  [INFO] Service CERTSYNC 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 certsync-log successfully stopped
2024-08-11 11:16:06.386511564  [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
2024-08-11 11:16:06.390527001  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-08-11 11:16:06.395943096  [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

FFprobe output from your camera

Frigate stats

No response

Operating system

Debian

Install method

Docker CLI

Object Detector

Coral

Network connection

Wired

Camera make and model

.

Any other information that may be helpful

No response

Answered by NickM-27

Aug 11, 2024

Your db file must be called frigate.db

View full answer

NickM-27 · 2024-08-11T12:08:13Z

NickM-27
Aug 11, 2024
Collaborator Sponsor

Your db file must be called frigate.db

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: Unable to start Frigate 0.14 with fresh DB #12943

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment

{{title}}

Select a reply

[Support]: Unable to start Frigate 0.14 with fresh DB #12943

andrewhack Aug 11, 2024

Describe the problem you are having

Version

Frigate config file

Relevant log output

FFprobe output from your camera

Frigate stats

Operating system

Install method

Object Detector

Network connection

Camera make and model

Any other information that may be helpful

Replies: 1 comment

NickM-27 Aug 11, 2024 Collaborator Sponsor

andrewhack
Aug 11, 2024

NickM-27
Aug 11, 2024
Collaborator Sponsor