#Frigate LXC stopped working showing FFMPEG errors.

10 messages · Page 1 of 1 (latest)

iron moss
#

I've had Frigate running in an LXC using the ttech helper scripts. It was working with no issues. Nothing has changed, no changes to config, no changes to the proxmox server, no changes to the LXC, but it just stopped working even after a reboot of the LXC or of the Proxmox host. I have no idea where to go from here to diagnose. I am able to connect to the cameras directly and see the feeds. Log repeats, config truncated for other cameras since they all fail.

rose light
#

im not sure about LXC, but i had something similar in docker and adjusting SHM (shared memory) value helped

iron moss
#

shm is 12G from what i can tell?

Filesystem                    Size  Used Avail Use% Mounted on
collective/subvol-112-disk-0   20G  5.2G   15G  26% /
collective                     15T  7.7T  6.9T  53% /storage
none                          492K  4.0K  488K   1% /dev
udev                           12G     0   12G   0% /dev/bus/usb
tmpfs                          12G   33M   12G   1% /dev/shm
wispy reef
#

we need to see more logs, there is not enough info to be helpful here

iron moss
#

It is really tough getting the logs over ssh in a pct enter, seems scrolling is lost, but I manually scanned over and here is anything else that looks different:

wispy reef
#

[h264 @ 0x5c82011ef040] No device available for decoder: device type vaapi needed for codec h264.

#

the GPU is not available

iron moss
#

i see /dev/dri/renderD128

iron moss
#

Only in the LXC, not the host. I know you are right, but I have 0 clue what happened 😦

It shows up on the host but it is obviously not loaded.
00:02.0 Display controller [0380]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04)
DeviceName: Onboard IGD
Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 [1462:7998]