[Support]: Frigate Docker Container keeps restarting #12896
-
Describe the problem you are havingI'm running Frigate in a Proxmox LXC container. I want my data to be stored on my NAS. I've mapped the nas to my pve node and used the command When I run the docker compose up -d command the frigate container runs but keeps restarting. I don't know where to find the log files as frigate doesn't stay on long enough from me to lock at them in the web interface Version14 Frigate config filemqtt:
enabled: true
host: 192.168.5.45 # YOUR MQTT IP
port: 1883
topic_prefix: frigate
client_id: frigate
user: mqtt-user # YOUR MQTT USERNAME
password: MQTTpassword # YOUT MQTT PASSWORD
stats_interval: 60
database:
path: /config/frigate.db
#detect:
#annotation_offset: -800
ffmpeg:
hwaccel_args: -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
detectors:
coral:
type: edgetpu
device: usb
###############################################################################
go2rtc:
streams:
camerafrontdoor:
#- "ffmpeg:rtsp://admin:[email protected]:554/h264Preview_01_main#video=copy#audio=copy"
#- "ffmpeg:back#audio=aac"
# - "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=password#video=copy#audio=copy#audio=opus"
camerafrontdoor_camera:
- "ffmpeg:http://192.168.30.20/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=password#video=copy#audio=copy#audio=opus"
- rtsp://192.168.30.20/Preview_01_sub
camerafrontdoor_sub:
- "ffmpeg:http://192.168.30.20/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=password"
#- "ffmpeg:rtsp://admin:[email protected]:554/h264Preview_01_sub#video=copy#audio=copy"
#- "ffmpeg:back#audio=aac"
#################################################################################
cameras:
Camerafrontdoor:
ffmpeg:
inputs:
# High Resolution Stream
- path: rtsp://admin:[email protected]:554/h264Preview_01_main
roles:
- record
# Low Resolution Stream
- path: rtsp://admin:[email protected]:554/h264Preview_01_sub
roles:
- rtmp
- detect
detect:
width: 640
height: 480
fps: 10
stationary:
# Optional: Frequency for confirming stationary objects (default: shown below)
# When set to 0, object detection will not confirm stationary objects until movement is detected.
# If set to 10, object detection will run to confirm the object still exists on every 10th frame.
interval: 10
# Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s)
threshold: 50
record:
enabled: true
retain:
days: 5
mode: motion
events:
retain:
default: 10
mode: motion
objects:
track:
- person
filters:
person:
threshold: 0.75
snapshots:
enabled: true
timestamp: true
bounding_box: true
retain:
default: 10
motion:
mask:
- 640,0,640,267,576,265,376,257,353,275,328,274,137,351,138,380,176,416,173,480,0,480,0,0
- 355,299,367,300,367,278,381,265,325,263
zones:
walkway:
coordinates: 137,480,140,340,204,325,349,265,376,271,640,371,640,480Relevant log outputs6-rc: info: service nginx-log successfully stopped
2024-08-09 16:03:01.942839524 exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2024-08-09 16:03:01.945913505 [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
2024-08-09 16:03:58.932020098 [INFO] Preparing Frigate...
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-08-09 16:03:58.934001370 [INFO] Preparing new go2rtc config...
2024-08-09 16:03:58.935638652 [INFO] Starting NGINX...
2024-08-09 16:03:58.939076245 [INFO] Starting Frigate...
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
2024-08-09 16:03:58.986917608 [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-08-09 16:03:59.047627594 127.0.0.1 - - [09/Aug/2024:16:03:59 -0400] "" 400 0 "-" "-" "-"
2024-08-09 16:03:59.167000458 [INFO] Starting go2rtc...
2024-08-09 16:03:59.258056886 16:03:59.257 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-08-09 16:03:59.258059914 16:03:59.257 INF config path=/dev/shm/go2rtc.yaml
2024-08-09 16:03:59.258061502 16:03:59.257 INF [rtsp] listen addr=:8554
2024-08-09 16:03:59.258062973 16:03:59.257 INF [webrtc] listen addr=:8555/tcp
2024-08-09 16:03:59.258564852 16:03:59.258 INF [api] listen addr=:1984
2024-08-09 16:03:59.891707147 [2024-08-09 16:03:59] frigate.app INFO : Starting Frigate (0.14.0-da913d8)
2024-08-09 16:03:59.893914848 [2024-08-09 16:03:59] frigate.util.config INFO : Checking if frigate config needs migration...
2024-08-09 16:03:59.914528634 [2024-08-09 16:03:59] frigate.util.config INFO : frigate config does not need migration...
2024-08-09 16:03:59.917317382 *************************************************************
2024-08-09 16:03:59.917319215 *************************************************************
2024-08-09 16:03:59.917322074 *** Your config file is not valid! ***
2024-08-09 16:03:59.917323620 *** Please check the docs at ***
2024-08-09 16:03:59.917324579 *** https://docs.frigate.video/configuration/index ***
2024-08-09 16:03:59.917338122 *************************************************************
2024-08-09 16:03:59.917339126 *************************************************************
2024-08-09 16:03:59.917340305 *** Config Validation Errors ***
2024-08-09 16:03:59.917341276 *************************************************************
2024-08-09 16:03:59.917349301 cameras.Camerafrontdoor.ffmpeg.inputs.1.roles.0: Input should be 'audio', 'record' or 'detect'
2024-08-09 16:03:59.917350246 *************************************************************
2024-08-09 16:03:59.917351098 *** End Config Validation Errors ***
2024-08-09 16:03:59.917351974 *************************************************************
2024-08-09 16:04:03.338619577 2024/08/09 16:04:03 [error] 158#158: *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"
2024-08-09 16:04:03.338622841 2024/08/09 16:04:03 [error] 158#158: *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"
2024-08-09 16:04:08.368474745 2024/08/09 16:04:08 [error] 159#159: *4 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: FFprobe output from your camerawhere do I run this command?Frigate statsNo response Operating systemProxmox Install methodDocker Compose Object DetectorCoral Network connectionWired Camera make and modelReolink Wifi Doorbell Camera Any other information that may be helpfulMy docker compose file frigate: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
You need to remove |
Beta Was this translation helpful? Give feedback.
-
|
I guess the issue is I was using ver 13.2 trying to get the data to be stored on my NAS. Now that frigate is on version 14 my config is invalid. I need to do one issue at a time. What is the syntax to go back to 13.2 in the docker compose file? ie |
Beta Was this translation helpful? Give feedback.
-
|
if you remove rtmp then the config will be valid. A good tag would be 0.13.2 |
Beta Was this translation helpful? Give feedback.
-
|
also needed to change the database from |
Beta Was this translation helpful? Give feedback.
You need to remove
rtmpas it's been deprecated. This is covered in the release notes.