[Config Support]: Unable to start Frigate #12326

awilliams84 · 2024-07-07T14:58:51Z

awilliams84
Jul 7, 2024

Describe the problem you are having

I setup Proxmox LXC -> Debian Container -> Portainer -> Frigate on a NUC 11 (referencing https://www.youtube.com/watch?v=DmbFq5dMsFo) and I am struggling to get it to function. I set it up once before (last month) on this device via Proxmox and it was working, but using a lot of CPU. So I was trying to do something different to try and get the Coral to work by starting over -- and now I can't even get it working again without the Coral.

Version

Unknown

Frigate config file

mqtt:
  enabled: false
ffmpeg:
  hwaccel_args: preset-vaapi

#Global Object Settings
objects:
  track:
    - person

cameras:
  RoadCam:
    ffmpeg:
      inputs:
        # High Resolution Stream
        - path: rtsp://username:[email protected]:554/h264Preview_01_main
          roles:
            - record
            - detect
    detect:
      fps: 5
    objects:
      track:
        - person
        - car
        - dog
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 30
    record:
      enabled: true
      retain:
        days: 10

Relevant log output

2024-07-07 10:55:39.612852503  2024/07/07 10:55:39 [error] 143#143: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.4.67, server: , request: "GET /api/config HTTP/1.1", upstream: "http://127.0.0.1:5001/config", host: "192.168.4.17:5000", referrer: "http://192.168.4.17:5000/"
2024-07-07 10:55:39.612855208  192.168.4.67 - - [07/Jul/2024:10:55:39 -0400] "GET /api/config HTTP/1.1" 502 559 "http://192.168.4.17:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36" "-"
2024-07-07 10:55:40.639525137  [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 nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-07 10:55:40.647093649  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-07 10:55:40.684389488  [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-07-07 10:55:40.685829526  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-07-07 10:55:40.687933382  [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 go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service frigate-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 frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-07 10:56:44.907904722  [INFO] Preparing Frigate...
s6-rc: info: service nginx successfully started
2024-07-07 10:56:44.908130538  [INFO] Preparing new go2rtc config...
2024-07-07 10:56:44.908426882  [INFO] Starting NGINX...
s6-rc: info: service legacy-services: starting
2024-07-07 10:56:44.913945382  [INFO] Starting Frigate...
s6-rc: info: service legacy-services successfully started
2024-07-07 10:56:45.079306554  [INFO] Starting go2rtc...
2024-07-07 10:56:45.133968001  10:56:45.133 INF go2rtc version 1.8.4 linux/amd64
2024-07-07 10:56:45.134191126  10:56:45.134 INF [api] listen addr=:1984
2024-07-07 10:56:45.134316248  10:56:45.134 INF [rtsp] listen addr=:8554
2024-07-07 10:56:45.134488579  10:56:45.134 INF [webrtc] listen addr=:8555
2024-07-07 10:56:45.611723359  [Errno 30] Read-only file system: '/config/model_cache'
2024-07-07 10:56:45.739673939  [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 nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-07 10:56:45.745285091  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-07 10:56:45.782641756  [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-07-07 10:56:45.784258337  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-07-07 10:56:45.786439630  [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

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Object Detector

CPU (no coral)

Any other information that may be helpful

No response

Answered by hawkeye217

Jul 7, 2024

It's the same issue another user had the other day. They didn't explain how they fixed it, but once they did, Frigate started without issue: #12313

View full answer

awilliams84 · 2024-07-07T15:08:10Z

awilliams84
Jul 7, 2024
Author

Seems like Frigate continuously reboots and I never get to see the one camera

0 replies

hawkeye217 · 2024-07-07T15:51:42Z

hawkeye217
Jul 7, 2024
Collaborator

Frigate is not starting because you have a read-only file system set up:

2024-07-07 10:56:45.611723359 [Errno 30] Read-only file system: '/config/model_cache'

3 replies

awilliams84 Jul 7, 2024
Author

I'm not sure how that became a read only file. I'll have to look up how to change that. I didn't have this issue last time I setup.

hawkeye217 Jul 7, 2024
Collaborator

It's the same issue another user had the other day. They didn't explain how they fixed it, but once they did, Frigate started without issue: #12313

Answer selected by awilliams84

awilliams84 Jul 7, 2024
Author

It's the same issue another user had the other day. They didn't explain how they fixed it, but once they did, Frigate started without issue: #12313

Thank you! This helped!! I changed the docker-compose.yml to fix the read only issue and it worked!

volumes: - /opt/frigate/config:/config:ro

should be

volumes: - /opt/frigate/config:/config

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Config Support]: Unable to start Frigate #12326

{{title}}

Replies: 2 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Config Support]: Unable to start Frigate #12326

awilliams84 Jul 7, 2024

Describe the problem you are having

Version

Frigate config file

Relevant log output

Frigate stats

Operating system

Install method

Object Detector

Any other information that may be helpful

Replies: 2 comments · 3 replies

awilliams84 Jul 7, 2024 Author

hawkeye217 Jul 7, 2024 Collaborator

awilliams84 Jul 7, 2024 Author

hawkeye217 Jul 7, 2024 Collaborator

awilliams84 Jul 7, 2024 Author

awilliams84
Jul 7, 2024

Replies: 2 comments 3 replies

awilliams84
Jul 7, 2024
Author

hawkeye217
Jul 7, 2024
Collaborator

awilliams84 Jul 7, 2024
Author

hawkeye217 Jul 7, 2024
Collaborator

awilliams84 Jul 7, 2024
Author