-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Config Support]: Frigate Crashing #16356
Replies: 2 comments · 45 replies
-
the logs show that there are no recordings available for the requested time, given that 30 days of all recordings are being kept it does seem odd. |
Beta Was this translation helpful? Give feedback.
All reactions
-
All we're looking for is a confirmation of increased/excessive resource usage when you see those recording maintainer errors in the log. Some of your copy times in your last log did exceed 1 second, so excessive resource usage may just be the culprit. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Signal 0 is not a crash. It looks like Frigate just shut down normally. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
For no recordings on front_yard_wide, are you seeing any files in /tmp/cache in the container with the prefix |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Try using As far as the blueprint is concerned, if you can view the recordings in the Frigate UI for the same time periods you're expecting to see from the blueprint, then yes, the blueprint must have some kind of bug. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sounds great thanks, I am going to say this is fixed for now and will open a new issue should it be clear one is needed. thanks for all of your quick feedback! |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry, if we could re-open this... I Implemented preset-vaapi:
Still getting errors, though:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
What driver do you have on your host |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry, I missed this. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I initially sought help on Reddit and appreciate the assistance from Nick. It looks like I am running into what may be an issue others may encounter with v15 and with the Home Assistant notification blueprint.
Frigate is crashing/rebooting, and it seems it may be tied to nginx. The m3u8 link in the beta version of the blueprint does not seem to be working on iOS. I get the play icon with a slash through it.
Version
0.15.0-cea210d
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Proxmox LXC .conf:
GNU nano 7.2 /etc/pve/lxc/107.conf arch: amd64 cores: 6 features: nesting=1 hostname: frigate memory: 7012 nameserver: 1.1.1.1 8.8.8.8 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=AA:7E:8D:7C:4F:12,ip=dhcp,type=veth onboot: 1 ostype: debian parent: preconfigchange rootfs: pool1:subvol-107-disk-0,size=158G swap: 7024 lxc.cgroup2.devices.allow: c 189:* rwm lxc.cgroup2.devices.allow: a lxc.cap.drop: lxc.mount.auto: cgroup:rw lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0 lxc.mount.entry: /dev/bus/usb/002/ dev/bus/usb/002/ none bind,optional,create=dir 0,0 lxc.cgroup2.devices.allow: c 226:0 rwm #igpu lxc.cgroup2.devices.allow: c 226:128 rwm #igpu lxc.cgroup2.devices.allow: c 29:0 rwm #coral lxc.cgroup2.devices.allow: c 189:* rwm #coral lxc.apparmor.profile: unconfined lxc.cgroup2.devices.allow: a lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0 #igpu lxc.mount.entry: /dev/apex_0 dev/apex_0 none bind,optional,create=file 0, 0 #coral lxc.cap.drop: lxc.mount.auto: cgroup:rw lxc.cgroup.cpuset.cpus: 0-1 # e.g.: reserve core 0-1
Beta Was this translation helpful? Give feedback.
All reactions