frigate: [Support]: FFMPEG not working (crashing) after upgrading packages - no camera feeds - Frigate 0.11 RC1

Describe the problem you are having

Hello,

After updating my packages using apt upgrade on my Raspberry Pi 4 (DietPi arm64 bit OS) my Frigate 0.11 RC1 container is no longer displaying camera feeds. If I restore my Pi to the time before installing the application upgrades (apt upgrade) all is fine.

I don’t have stimeout set and this message isn’t showing in the logs at all.

Output of the apt upgrade upgradable (apt list --upgradable) list below:

base-files/stable 11.1+deb11u4 arm64 [upgradable from: 11.1+deb11u3] bash/stable 5.1-2+deb11u1 arm64 [upgradable from: 5.1-2+b3] containerd.io/bullseye 1.6.7-1 arm64 [upgradable from: 1.6.4-1] curl/stable-security 7.74.0-1.3+deb11u2 arm64 [upgradable from: 7.74.0-1.3+deb11u1] dirmngr/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] docker-ce-cli/bullseye 5:20.10.17~3-0~debian-bullseye arm64 [upgradable from: 5:20.10.16~3-0~debian-bullseye] docker-ce/bullseye 5:20.10.17~3-0~debian-bullseye arm64 [upgradable from: 5:20.10.16~3-0~debian-bullseye] dpkg/stable 1.20.11 arm64 [upgradable from: 1.20.10] firmware-atheros/stable 1:20210315-3+rpt7 all [upgradable from: 1:20210315-3+rpt5] firmware-brcm80211/stable 1:20210315-3+rpt7 all [upgradable from: 1:20210315-3+rpt5] firmware-iwlwifi/stable 1:20210315-3+rpt7 all [upgradable from: 1:20210315-3+rpt5] firmware-misc-nonfree/stable 1:20210315-3+rpt7 all [upgradable from: 1:20210315-3+rpt5] firmware-realtek/stable 1:20210315-3+rpt7 all [upgradable from: 1:20210315-3+rpt5] gnupg-l10n/stable,stable-security 2.2.27-2+deb11u2 all [upgradable from: 2.2.27-2+deb11u1] gnupg-utils/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gnupg/stable,stable-security 2.2.27-2+deb11u2 all [upgradable from: 2.2.27-2+deb11u1] gpg-agent/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpg-wks-client/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpg-wks-server/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpg/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpgconf/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpgsm/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] gpgv/stable,stable-security 2.2.27-2+deb11u2 arm64 [upgradable from: 2.2.27-2+deb11u1] libc-bin/stable 2.31-13+rpt2+rpi1+deb11u3 arm64 [upgradable from: 2.31-13+rpt2+rpi1+deb11u2] libc-l10n/stable 2.31-13+rpt2+rpi1+deb11u3 all [upgradable from: 2.31-13+rpt2+rpi1+deb11u2] libc6/stable 2.31-13+rpt2+rpi1+deb11u3 arm64 [upgradable from: 2.31-13+rpt2+rpi1+deb11u2] libcurl4/stable-security 7.74.0-1.3+deb11u2 arm64 [upgradable from: 7.74.0-1.3+deb11u1] libgnutls30/stable-security 3.7.1-5+deb11u2 arm64 [upgradable from: 3.7.1-5] libldb2/stable-security 2:2.2.3-2~deb11u2 arm64 [upgradable from: 2:2.2.3-2~deb11u1] libpam-modules-bin/stable 1.4.0-9+deb11u1+rpt2 arm64 [upgradable from: 1.4.0-9+deb11u1+rpt1] libpam-modules/stable 1.4.0-9+deb11u1+rpt2 arm64 [upgradable from: 1.4.0-9+deb11u1+rpt1] libpam-runtime/stable 1.4.0-9+deb11u1+rpt2 all [upgradable from: 1.4.0-9+deb11u1+rpt1] libpam0g/stable 1.4.0-9+deb11u1+rpt2 arm64 [upgradable from: 1.4.0-9+deb11u1+rpt1] libsmbclient/stable-security 2:4.13.13+dfsg-1~deb11u5 arm64 [upgradable from: 2:4.13.13+dfsg-1~deb11u3] libssl1.1/stable 1.1.1n-0+deb11u3+rpt1 arm64 [upgradable from: 1.1.1n-0+deb11u2+rpt1] libtirpc-common/stable-security 1.3.1-1+deb11u1 all [upgradable from: 1.3.1-1] libtirpc3/stable-security 1.3.1-1+deb11u1 arm64 [upgradable from: 1.3.1-1] libwbclient0/stable-security 2:4.13.13+dfsg-1~deb11u5 arm64 [upgradable from: 2:4.13.13+dfsg-1~deb11u3] locales/stable 2.31-13+rpt2+rpi1+deb11u3 all [upgradable from: 2.31-13+rpt2+rpi1+deb11u2] nano/stable 5.4-2+deb11u1 arm64 [upgradable from: 5.4-2] openssh-client/stable 1:8.4p1-5+deb11u1 arm64 [upgradable from: 1:8.4p1-5] openssh-sftp-server/stable 1:8.4p1-5+deb11u1 arm64 [upgradable from: 1:8.4p1-5] openssl/stable 1.1.1n-0+deb11u3+rpt1 arm64 [upgradable from: 1.1.1n-0+deb11u2+rpt1] python3-ldb/stable-security 2:2.2.3-2~deb11u2 arm64 [upgradable from: 2:2.2.3-2~deb11u1] raspberrypi-bootloader/stable 1:1.20220811-1 arm64 [upgradable from: 1:1.20220331-1] raspberrypi-kernel/stable 1:1.20220811-1 arm64 [upgradable from: 1:1.20220331-1] rpi-eeprom/stable 13.16-1 arm64 [upgradable from: 13.14-1] tzdata/stable-updates 2021a-1+deb11u5 all [upgradable from: 2021a-1+deb11u3] unzip/stable-security 6.0-26+deb11u1 arm64 [upgradable from: 6.0-26] wireless-regdb/stable 2022.04.08-2~deb11u1 all [upgradable from: 2020.04.29-2]

Any ideas?

Thank you in advance

Version

0.11.0-37325C7

Frigate config file

Not included for now (very basic config)

Relevant log output

[2022-08-23 22:15:52] watchdog.Cam1             ERROR   : Ffmpeg process crashed unexpectedly for Cam1.
[2022-08-23 22:15:52] watchdog.Cam1             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-08-23 22:15:52] ffmpeg.Cam1.detect        ERROR   : [flv @ 0x559b29d820] 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
[2022-08-23 22:15:52] watchdog.Cam2               ERROR   : Ffmpeg process crashed unexpectedly for Cam2.
[2022-08-23 22:15:52] watchdog.Cam2               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-08-23 22:15:52] ffmpeg.Cam2.detect          ERROR   : [segment @ 0x55948e3ee0] 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
[2022-08-23 22:15:52] ffmpeg.Cam2.detect          ERROR   : [segment @ 0x55948e3ee0] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.
[2022-08-23 22:16:12] watchdog.Cam1             INFO    : No frames received from Cam1 in 20 seconds. Exiting ffmpeg...
[2022-08-23 22:16:12] watchdog.Cam1             INFO    : Waiting for ffmpeg to exit gracefully...
[2022-08-23 22:16:12] watchdog.Cam2               INFO    : No frames received from Cam2 in 20 seconds. Exiting ffmpeg...
[2022-08-23 22:16:12] watchdog.Cam2               INFO    : Waiting for ffmpeg to exit gracefully...
[2022-08-23 22:16:42] watchdog.Cam1             INFO    : FFmpeg didnt exit. Force killing...
[2022-08-23 22:16:42] frigate.video                  ERROR   : Cam1: Unable to read frames from ffmpeg process.
[2022-08-23 22:16:42] frigate.video                  ERROR   : Cam1: ffmpeg process is not running. exiting capture thread...
[2022-08-23 22:16:42] watchdog.Cam2               INFO    : FFmpeg didnt exit. Force killing...
[2022-08-23 22:16:42] frigate.video                  ERROR   : Cam2: Unable to read frames from ffmpeg process.
[2022-08-23 22:16:42] frigate.video                  ERROR   : Cam2: ffmpeg process is not running. exiting capture thread...
[2022-08-23 22:16:46] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:57696]
[2022-08-23 22:16:49] frigate.record                 WARNING : Discarding a corrupt recording segment: Cam2-20220823221556.mp4
[2022-08-23 22:16:52] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:36348]
[2022-08-23 22:16:52] watchdog.Cam1             ERROR   : Ffmpeg process crashed unexpectedly for Cam1.
[2022-08-23 22:16:52] watchdog.Cam1             ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-08-23 22:16:52] ffmpeg.Cam1.detect        ERROR   : [flv @ 0x55b831e820] 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
[2022-08-23 22:16:52] watchdog.Cam2               ERROR   : Ffmpeg process crashed unexpectedly for Cam2.
[2022-08-23 22:16:52] watchdog.Cam2               ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2022-08-23 22:16:52] ffmpeg.Cam2.detect          ERROR   : [segment @ 0x55d4b6a360] 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

FFprobe output from your camera

Not installed ffprobe but the cameras worked fine before - I can install it if needed!

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

Coral version

USB

Network connection

Wired

Camera make and model

N/A for this issue I believe

Any other information that may be helpful

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 27

Most upvoted comments

There’s another user that saw the same thing after updating kernel as well https://github.com/blakeblackshear/frigate/issues/3780

NickM-27 on Sep 8, 2022

I’m seeing the same thing, I have been running Frigate 0.11.0 beta full access for months without issue. I hadn’t done any updates for a while as I’ve been busy with work, hence I never updated to RC1. Today I updated to 11.RC2 and Frigate refuses to start with FFMPEG errors. I since edited the stimeout settings to timeout as specified in the release notes but that’s the only changes I’ve made to the config since everything was working but that hasn’t helped either.

healeydave on Sep 1, 2022

sadly RC2 did not help at all. issue persists.

krim404 on Aug 28, 2022

We have a new build of ffmpeg in 0.11 RC2 so maybe give that a try

NickM-27 on Aug 28, 2022

true, didnt think about that. but maybe running on a new (clean) database just for testing purpose?

I don’t think there’s anything wrong with trying it on a clean setup, but the ramifications should be mentioned (like they now have been).

I was just trying to point out that OP has been using RC1 / 5.0.1 for some time with hwaccel working; it only stopped after updating the apt dependencies listed above and both good and bad states are fully reproducible. So the suggestion that it is an isolated ffmpeg bug and 5.0.1 hwaccel is faulty doesn’t hold water from my perspective.

NickM-27 on Aug 24, 2022

i can confirm that this issue is not a problem with the kernel, but with the ffmpeg version 4.3.4. Found a few reports that 4.3.4 has a bug on hardware decoding. With 4.3.3 everything works as it should.

Can you confirm, if hardwarencoding is working, when you use image: blakeblackshear/frigate:0.11.0-3de1948 ? this older version does include ffmpeg 4.3.3

krim404 on Aug 24, 2022

As the other issue pointed out, something broke that affects the way the gpu is being passed to the container.

If you want, you can try the upcoming build based on ffmpeg btbn 5.1 (perhaps it has some compatibility that is fixed), otherwise it may be a package that just shouldn’t be updated.

crzynik/frigate:btbn-ffmpeg

NickM-27 on Aug 23, 2022

Are you using hwaccel being used? If so, does it work without it?

NickM-27 on Aug 23, 2022