[Config Support]: #9908

kubulekxd · 2024-02-18T12:58:28Z

kubulekxd
Feb 18, 2024

Describe the problem you are having

After installed docker lxc on proxmox and configured frigate i get this problem:

2024-02-18 00:24:00.851920568 [Errno 30] Read-only file system: '/config/model_cache'
2024-02-18 00:24:01.291142172 [INFO] Service Frigate exited with code 1 (by signal 0)

there was no file then i create it and now got logs:

2024-02-18 12:57:35.716714337 [INFO] Starting go2rtc...
2024-02-18 12:57:35.974993561 12:57:35.974 INF go2rtc version 1.8.4 linux/amd64
2024-02-18 12:57:35.977039829 12:57:35.976 INF [rtsp] listen addr=:8554
2024-02-18 12:57:35.978354642 12:57:35.978 INF [webrtc] listen addr=:8555
2024-02-18 12:57:35.980459341 12:57:35.977 INF [api] listen addr=:1984
2024-02-18 12:57:38.394980867 [2024-02-18 12:57:38] frigate.app INFO : Starting Frigate (0.13.1-34fb1c2)
2024-02-18 12:57:38.453733445 unable to open database file
2024-02-18 12:57:38.453872088 [2024-02-18 12:57:38] peewee_migrate.logs INFO : Starting migrations
2024-02-18 12:57:39.799040955 2024/02/18 12:57:39 [error] 133#133: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http:https://127.0.0.1:5001version", host: "127.0.0.1:5000"
2024-02-18 12:57:39.979376121 [INFO] Service Frigate exited with code 1 (by signal 0)

I am new but i tried some ways and i dont know what to do more now.

Version

3.9

Frigate config file

version: '3.9'
persistence:
  config:
    enabled: true
  media:
    enabled: true

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "128mb" # update for your cameras based on calculation above
    devices:
      - /dev/apex_0:/dev/apex_0 
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /opt/frigate/config:/config:ro
      - /cctv_clips:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "1935:1935" # RTMP feeds
    environment:
      FRIGATE_RTSP_PASSWORD: my password

Relevant log output

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-02-18 12:56:29.993579692  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-02-18 12:56:30.076015457  [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-02-18 12:56:30.088911470  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-02-18 12:56:30.099893773  [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 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 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-02-18 12:57:34.945996221  [INFO] Preparing new go2rtc config...
s6-rc: info: service nginx successfully started
2024-02-18 12:57:34.962194717  [INFO] Starting NGINX...
s6-rc: info: service legacy-services: starting
2024-02-18 12:57:34.970495704  [INFO] Preparing Frigate...
2024-02-18 12:57:35.041757256  [INFO] Starting Frigate...
s6-rc: info: service legacy-services successfully started
2024-02-18 12:57:35.716714337  [INFO] Starting go2rtc...
2024-02-18 12:57:35.974993561  12:57:35.974 INF go2rtc version 1.8.4 linux/amd64
2024-02-18 12:57:35.977039829  12:57:35.976 INF [rtsp] listen addr=:8554
2024-02-18 12:57:35.978354642  12:57:35.978 INF [webrtc] listen addr=:8555
2024-02-18 12:57:35.980459341  12:57:35.977 INF [api] listen addr=:1984
2024-02-18 12:57:38.394980867  [2024-02-18 12:57:38] frigate.app                    INFO    : Starting Frigate (0.13.1-34fb1c2)
2024-02-18 12:57:38.453733445  unable to open database file
2024-02-18 12:57:38.453872088  [2024-02-18 12:57:38] peewee_migrate.logs            INFO    : Starting migrations
2024-02-18 12:57:39.799040955  2024/02/18 12:57:39 [error] 133#133: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http:https://127.0.0.1:5001version", host: "127.0.0.1:5000"
2024-02-18 12:57:39.979376121  [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-02-18 12:57:40.006950926  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-02-18 12:57:40.079637312  [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-02-18 12:57:40.091201707  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-02-18 12:57:40.103241828  [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

Proxmox

Install method

Docker CLI

Coral version

PCIe

Any other information that may be helpful

No response

hawkeye217 · 2024-02-18T13:25:36Z

hawkeye217
Feb 18, 2024
Collaborator

You are seeing Read-only file system because you've marked the mount as read-only. Remove the ro from the end of this line in your Docker compose:

/opt/frigate/config:/config:ro

Frigate's database is written to this directory, so if the filesystem is read-only as the logs state, a database cannot be created, saved, or modified.

0 replies

kubulekxd · 2024-02-18T14:11:42Z

kubulekxd
Feb 18, 2024
Author

i did it but it still not works. Any suggestions?

4 replies

hawkeye217 Feb 18, 2024
Collaborator

So after modifying your docker-compose you still have the same read only file system error?

kubulekxd Feb 18, 2024
Author

2024-02-18 12:57:38.394980867 [2024-02-18 12:57:38] frigate.app INFO : Starting Frigate (0.13.1-34fb1c2)
2024-02-18 12:57:38.453733445 unable to open database file
2024-02-18 12:57:38.453872088 [2024-02-18 12:57:38] peewee_migrate.logs INFO : Starting migrations
2024-02-18 12:57:39.799040955 2024/02/18 12:57:39 [error] 133#133: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", upstream: "http:https://127.0.0.1:5001version", host: "127.0.0.1:5000"
2024-02-18 12:57:39.979376121 [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-02-18 12:57:40.006950926 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-02-18 12:57:40.079637312 [INFO] Service NGINX exited with code 0 (by signal 0)

now problem is here- u have full logs above this reply in main post problem

hawkeye217 Feb 18, 2024
Collaborator

Can you post your frigate config file?

kubulekxd Feb 18, 2024
Author

mqtt:
enabled: false
detectors:
coral:
type: edgetpu
device: pci:0
#Global Object Settings
objects:
track:
- person
filters:
person:
min_area: 5000
max_area: 100000
cameras:
FrontCam:
ffmpeg:
inputs:
# High Resolution Stream
- path: rtsp:https://sosik2000:[email protected]:554/stream1&subtype=20
roles:
- record
# Low Resolution Stream
- path: rtsp:https://sosik2000:[email protected]:554/stream1&subtype=20
roles:
- detect
detect:
width: 480
height: 360
fps: 24

kubulekxd · 2024-02-18T14:41:42Z

kubulekxd
Feb 18, 2024
Author

mqtt:
enabled: false
detectors:
coral:
type: edgetpu
device: pci:0
#Global Object Settings
objects:
track:
- person
filters:
person:
min_area: 5000
max_area: 100000
cameras:
FrontCam:
ffmpeg:
inputs:
# High Resolution Stream
- path: rtsp:https://sosik2000:[email protected]:554/stream1&subtype=20
roles:
- record
# Low Resolution Stream
- path: rtsp:https://sosik2000:[email protected]:554/stream1&subtype=20
roles:
- detect
detect:
width: 480
height: 360
fps: 24

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Config Support]: #9908

{{title}}

Replies: 3 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Config Support]: #9908

kubulekxd Feb 18, 2024

Describe the problem you are having

Version

Frigate config file

Relevant log output

Frigate stats

Operating system

Install method

Coral version

Any other information that may be helpful

Replies: 3 comments · 4 replies

hawkeye217 Feb 18, 2024 Collaborator

kubulekxd Feb 18, 2024 Author

hawkeye217 Feb 18, 2024 Collaborator

kubulekxd Feb 18, 2024 Author

hawkeye217 Feb 18, 2024 Collaborator

kubulekxd Feb 18, 2024 Author

kubulekxd Feb 18, 2024 Author

kubulekxd
Feb 18, 2024

Replies: 3 comments 4 replies

hawkeye217
Feb 18, 2024
Collaborator

kubulekxd
Feb 18, 2024
Author

hawkeye217 Feb 18, 2024
Collaborator

kubulekxd Feb 18, 2024
Author

hawkeye217 Feb 18, 2024
Collaborator

kubulekxd Feb 18, 2024
Author

kubulekxd
Feb 18, 2024
Author