[Config Support]: Cant figure out whats wrong in my config #16084
-
Describe the problem you are havingI have a reolink POE doorbell and Frigate in a docker container on Proxmox 8. also, I wasn't succesful in getting audio in the recordings. Any suggestions? Version0.14 Frigate config filemqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-vaapi
detectors:
coral:
type: edgetpu
device: usb
objects:
track:
- person
- car
- cat
- dog
- bicycle
- bus
- motorcycle
- horse
filters:
person:
min_area: 5000
max_area: 100000
go2rtc:
streams:
deurbel:
- "ffmpeg:http://192.168.1.111/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=Abcdefghij#video=copy#audio=copy#audio=opus"
- rtsp://192.168.1.111/Preview_01_sub
deurbel_sub:
- "ffmpeg:http://192.168.1.111/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=Abcdefghij"
cameras:
deurbel:
ffmpeg:
inputs:
- path: rtsp://localhost:8554/deurbel
input_args: preset-rtsp-restream
roles:
- record
- audio
- path: rtsp://localhost:8554/deurbel_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
fps: 8
width: 640
height: 480
record:
enabled: true
retain:
days: 14
mode: motion
zones:
voordeur:
coordinates:
0.331,0,0.299,0.188,0.287,0.429,0.293,0.62,0.294,0.654,0.339,0.699,0.401,0.75,0.483,0.814,0.573,0.872,0.665,0.915,0.741,0.938,0.84,0.953,0.917,0.953,0.963,0.952,0.982,0.945,0.993,0.845,1,0.842,1,1,0,0.998,0,0.001
loitering_time: 0
inertia: 1
Stoep:
coordinates:
0.291,0.512,0.646,0.591,1,0.622,0.999,0.846,0.989,0.847,0.979,0.948,0.888,0.952,0.766,0.94,0.682,0.916,0.6,0.885,0.484,0.813,0.381,0.734,0.295,0.652
loitering_time: 0
Straat:
coordinates:
0.291,0.513,0.639,0.589,0.998,0.621,0.999,0.436,0.899,0.424,0.628,0.427,0.439,0.433,0.29,0.448
loitering_time: 0
inertia: 3
motion:
mask: 0.345,0.014,0.642,0.011,0.642,0.05,0.345,0.053
threshold: 30
contour_area: 10
improve_contrast: 'true'
review:
alerts:
required_zones: voordeur
detections:
required_zones:
- Straat
- Stoep
version: 0.14Relevant Frigate log output2025-01-22 08:23:16.548939472 [INFO] Preparing Frigate...
2025-01-22 08:23:16.574731976 [INFO] Starting Frigate...
2025-01-22 08:23:18.272505504 [2025-01-22 08:23:18] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa)
2025-01-22 08:23:18.272667011 [2025-01-22 08:23:18] frigate.util.config INFO : Checking if frigate config needs migration...
2025-01-22 08:23:18.287265175 [2025-01-22 08:23:18] frigate.util.config INFO : frigate config does not need migration...
2025-01-22 08:23:18.328012848 [2025-01-22 08:23:18] peewee_migrate.logs INFO : Starting migrations
2025-01-22 08:23:18.328940951 [2025-01-22 08:23:18] peewee_migrate.logs INFO : There is nothing to migrate
2025-01-22 08:23:18.369118395 [2025-01-22 08:23:18] frigate.app INFO : Recording process started: 332
2025-01-22 08:23:18.377509001 [2025-01-22 08:23:18] frigate.app INFO : Recording process started: 334
2025-01-22 08:23:18.378982465 [2025-01-22 08:23:18] frigate.app INFO : go2rtc process pid: 99
2025-01-22 08:23:18.415950085 [2025-01-22 08:23:18] frigate.app INFO : Output process started: 362
2025-01-22 08:23:18.419995470 [2025-01-22 08:23:18] detector.coral INFO : Starting detection process: 360
2025-01-22 08:23:18.420597419 [2025-01-22 08:23:18] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb
2025-01-22 08:23:18.539616015 [2025-01-22 08:23:18] frigate.app INFO : Camera processor started for deurbel: 386
2025-01-22 08:23:18.540590536 [2025-01-22 08:23:18] frigate.app INFO : Capture process started for deurbel: 399
2025-01-22 08:23:21.079165162 [2025-01-22 08:23:21] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found
2025-01-22 10:08:00.347259384 [2025-01-22 10:08:00] frigate.ptz.onvif ERROR : Onvif is not setup for deurbel
2025-01-22 10:09:14.399801440 [2025-01-22 10:09:14] frigate.video ERROR : deurbel: Unable to read frames from ffmpeg process.
2025-01-22 10:09:14.400623079 [2025-01-22 10:09:14] frigate.video ERROR : deurbel: ffmpeg process is not running. exiting capture thread...
2025-01-22 10:09:19.265099744 [2025-01-22 10:09:19] watchdog.deurbel ERROR : Ffmpeg process crashed unexpectedly for deurbel.
2025-01-22 10:09:19.266619045 [2025-01-22 10:09:19] watchdog.deurbel ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2025-01-22 10:09:19.269469125 [2025-01-22 10:09:19] ffmpeg.deurbel.detect ERROR : rtsp://localhost:8554/deurbel_sub: Connection timed out
2025-01-22 10:09:19.271666665 [2025-01-22 10:09:19] ffmpeg.deurbel.detect ERROR : Last message repeated 1 times
2025-01-22 10:09:19.288716028 [2025-01-22 10:09:19] ffmpeg.deurbel.audio_record ERROR : [segment @ 0x5d29a80a1100] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2025-01-22 10:09:19.289370054 [2025-01-22 10:09:19] ffmpeg.deurbel.audio_record ERROR : rtsp://localhost:8554/deurbel: Connection timed out
2025-01-22 10:09:19.290168125 [2025-01-22 10:09:19] watchdog.deurbel INFO : Terminating the existing ffmpeg process...
2025-01-22 10:09:19.290695348 [2025-01-22 10:09:19] watchdog.deurbel INFO : Waiting for ffmpeg to exit gracefully...Relevant go2rtc log output2025-01-22 08:23:16.552237397 [INFO] Preparing new go2rtc config...
2025-01-22 08:23:16.997933411 [INFO] Starting go2rtc...
2025-01-22 08:23:17.168479388 08:23:17.168 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-01-22 08:23:17.168937591 08:23:17.168 INF config path=/dev/shm/go2rtc.yaml
2025-01-22 08:23:17.169738406 08:23:17.169 INF [api] listen addr=:1984
2025-01-22 08:23:17.170516823 08:23:17.170 INF [rtsp] listen addr=:8554
2025-01-22 08:23:17.171091532 08:23:17.171 INF [webrtc] listen addr=:8555/tcp
2025-01-22 08:23:26.547117704 [INFO] Starting go2rtc healthcheck service...
2025-01-22 10:09:14.029810461 10:09:14.029 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp 127.0.0.1:8554->127.0.0.1:53954: i/o timeout" url=ffmpeg:http://192.168.1.111/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=AbcdefghijFrigate statsNo response Operating systemProxmox Install methodDocker Compose docker-compose file or Docker CLI commandversion: '3.9'
services:
frigate:
container_name: frigate
privileged: true
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "128mb"
devices:
- /dev/bus/usb:/dev/bus/usb
- /dev/dri/renderD128
volumes:
- /etc/localtime:/etc/localtime:ro
- /opt/frigate/config:/config
- /opt/frigate/storage:/media/frigate
- type: tmpfs
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "1935:1935"
- "8971:8971"
- "8554:8554"Object DetectorCoral Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 12 replies
-
|
The camera connection is timing out, that's usually a network issue |
Beta Was this translation helpful? Give feedback.
-
|
So the issue is not Frigate related and might have something to do with the network or camera that causes timeouts leading to frigate not receiving a signal? |
Beta Was this translation helpful? Give feedback.
-
|
I gave the Doorbell a manual firmware update and it had been stable since. |
Beta Was this translation helpful? Give feedback.
-
|
Any suggestions why iam missing audio in my recordings? |
Beta Was this translation helpful? Give feedback.
-
|
Tried this before and gave it another shot. Didnt work then, doesnt work now. Idents in config are oke. |
Beta Was this translation helpful? Give feedback.
-
|
We will need to see what you tried |
Beta Was this translation helpful? Give feedback.
-
|
You are right. |
Beta Was this translation helpful? Give feedback.
-
|
Dont know what happend, but the recordings from this morning do have audio. |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad to hear it's working for you. |
Beta Was this translation helpful? Give feedback.
-
|
The problems appeared again after running smooth for days. And now also when it runs for couple of days to a week Frigate randomly crashes showing a 500 internal server error. The only solution to this is returning a backup, which crashes also after a few days with the same problem. Frigate was running on proxmox, and when it crashes it also effects my home assistant VM that is not able to use zigbee2mqtt anymore. I thought that the advantage of Proxmox was isolated enviroments. But only removing Frigate when it has crashed restores te problem for Home Assistant. I dont have any logs when the 500 internal server error appears as I cant reach the logs anymore. Google is not helping since there is almost no info regarding a 500 internal server error. I really am kinda lost in what I am doing wrong...Help is much appreciated |
Beta Was this translation helpful? Give feedback.
-
|
should still be able to get logs from the lxc directly |
Beta Was this translation helpful? Give feedback.
-
|
It took a while before it crashed again, but it did. Managed to pull these logs from the proxmox shell. I got no clue what this means
|
Beta Was this translation helpful? Give feedback.
-
|
These logs don't mean anything, really. They are just showing that the UI is not able to connect to the backend. You will usually see some of these when Frigate is starting up and you have the UI open. The likely cause of your issue is above this in the logs. |
Beta Was this translation helpful? Give feedback.
-
|
I found the issue and it is not Frigate related. It has to do with Proxmox. |
Beta Was this translation helpful? Give feedback.
I found the issue and it is not Frigate related. It has to do with Proxmox.
Although the storage of the Frigate container is far from full, the local-lvm apparently was. The distribution off storage between local storage and lvm-storage is quit off. Somehow the Lvm is just about half of then total available storage. When full, which it was pretty fast, it crashes all running VMs and LXCs. So need to fix that. Slowly getting there. But since it is not Frigate related, this topic can be closed.