[Support]: Frigate Addon not starting after update to release 0.13.0 #9527
Comments
|
It seems like you may be running an old version of docker / HA supervised? |
|
it is on the latest version of both home assistant which was updated today(2024.1.6) and on docker (24.07) |
|
@felipecrs any ideas here? I don't think other users have seen issues with this |
|
and actually, I don't think this changed with 0.13 either |
|
Oh. This is odd. But yes, it's new from 0.13. Supposing this is a supervised installation, make sure your docker is up to date. At least v24. |
|
Docker is on v24.0.7 already |
|
ah I see, it was reduced from admin blakeblackshear/frigate-hass-addons@3323e7b |
|
This may be an issue with a too old kernel as well. |
|
|
|
are there any logs that you guys think would help for me to retrieve? @NickM-27 @felipecrs |
|
Your kernel is quite old. Can't you upgrade? There is nothing wrong in Frigate specifically. I would not expect a fix for it. Looking up online, it can also be the version of runc and containerd. Maybe you updated docker recently but didn't restart the daemon? A system reboot may help as well. |
|
I will update the Kernel and come back if it worked, a system reboot has already been done, obrigado Felipe. |
|
Good day, |
|
Update docker to the latest version, and update the kernel to the latest version. AFAIK latest kernel for Ubuntu 20.04 is 5.15 through HWE. Please let us know the result. |
|
Many thanks for pointing in right direction. Update Kernel to 5.15. Confirm it's working. |
Did you end up updating your Kernel? I am having the same issue with Debian 11 on 5.10.0-16, and wanted to make sure this was the fix before I invest some time into updating my server. |
|
hey @mack0352 I m not able to update my kernel, i am thinking abount doing a backup of my HA instance, doing a fresh debian install on the latest version, I am not a linux guy by trade so I am not sure if there is an easier way to update the kernel I am all ears |
|
According to the requirements, Debian 11 is not supported for Home Assistant Supervised installations anyway: https://github.com/home-assistant/architecture/blob/master/adr/0014-home-assistant-supervised.md#supported-operating-system-system-dependencies-and-versions |
|
I believe that. I installed Debian 11 in early 2022, and never really have kept it up to date or looked at new versions. I only have a few things running on this server, so I may also just do a fresh install on Debian 12 with a HA Backup. For now, nothing is broken on my end (still running Frigate 12.1). |
|
I am planning on going the same way @mack0352 , doing a fresh install and retrieving the backup |
|
From the Supervised documentation, it says:
So, if you don't feel comfortable with it, I don't understand why using it at all. I personally use HAOS. |
|
@mack0352 I updated from Debian 11 to 12, now I have kernel version 6.1, and frigate 0.13.1 is working correctly @felipecrs I actually am using debian because I have other services running alongside home assistant, such as a printer server, transmission, Arr suite, etc |
|
Right. One other option you had was to run Frigate through docker compose. It wouldn't have the same issue, I believe. Anyway, glad that it worked. |
|
I'm having the same issue on hassos install, frigate installed as add-on. frigate will not start. restored from backup to 12.1, works fine. None of the issues identified in this bug report seem to apply to my install. |
|
Did you say you are using HAOS? If so, what version? If not, what is your docker, kernel and supervisor version? |
|
yes, using haos. |
|
What error are you receiving while starting the add-on? |
|
none, it just hangs |
|
No logs? |
|
i'll try the upgrade again so the logs should be easier to follow |
|
Here are my versions btw, which works: Core 2024.1.6 Very same as yours. And if you don't find out that your logs contain |
|
yay. installed the upgrade same as before, only it works now. thanks! |
|
I have that same problem |
|
Hello, Same issue. Core : 2024.2.0b7 Trying upgrade Debian 11 to 12, but always same error : "ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/ccab4aaf_frigate-fa/start - Can't create container from addon_ccab4aaf_frigate-fa: 400 Client Error for http+docker:https://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate-fa: Bad Request ("invalid CapAdd: unknown capability: "CAP_PERFMON"")#33[0m" Regards |
|
Upgrade docker to the latest version and the Linux kernel to at least 5.15. That's the solution for this problem. |
|
Thanks @felipecrs . I had previously mark hold containerd.io / docker-ce / docker-ce-cli package for compatibility. Just upgrade theses packages et now error is not present. Now error in conf, but is other problem. Thanks you |
|
Hi, I have the same issue since a few weeks :
I don't know how I could update the mentionned packages. My home assistant instance is runing on docker installed on a synology NAS, and the "Container Manager" Synology package is already up to date. Thanks in advance for your help ! Regards, |
|
You need to upgrade your operating system or your kernel as well. |
|
I am runing on a Synology NAS, everything is up to date : operating system (DSM) and installed packages. |
|
What is the Linux version you have? |
|
The operating system is DSM (Disk Station Manager v7.2.1-69057) from Synology. It's Linux based, but that's all I know. Docker is running via a Synology package Container Manager, and the last update is from september 2023. Maybe the CAP_PERFMON is not there yet, I see here that it's only with the latest versions. Is there a way to start the addon without the CAP_PERFMON ? |
|
As your system is not supported by supervisor, I would advise you to use docker compose to spin up Frigate. And then, if you want the Frigate panel in Hass you can use the Frigate proxy add-on. |
|
I don't need the Frigate panel, I only use the card in order to have two-way audio and use it as an intercom. |
|
Follow the installation guide for docker: https://docs.frigate.video/frigate/installation/ |
|
Thank you, I will try that. But that would be nice to be able to start it like any other addon in home assistant, and like before the 0.13 version |
|
Sorry friend, but in my opinion, you were not even supposed to be running home assistant supervised in your system. They make it clear that only Debian 12 is supported. This enables add-ons developers to know what features they can use or not. You can of course still run supervised on your system, just be aware that you'll be on your own. That's what "unsupported" means in this context. I am not a maintainer of Frigate, so @NickM-27 and @blakeblackshear may have a different opinion. |
|
The reason this occurs is because the system privilege level for the addon was dropped from admin to just performance. This is an improvement in security and reduces risk for the user so this is an objective improvement. Users are always encouraged to run supported systems |
|
Ok thanks for your explanations (but I will keep using home assistant supervised 😄, hopefully DSM will get supported one day) |
|
That's very unlikely, but yeah maybe someday DSM will upgrade the Linux kernel and Docker to a version that supports CAP_PERFMON. |
|
Not will be .....
I change to normal version outside DSM
…On Sat, 24 Feb 2024 at 18:38, Felipe Santos ***@***.***> wrote:
That's very unlikely, but yeah maybe someday DSM will upgrade the Linux
kernel and Docker to a version that supports CAP_PERFMON.
—
Reply to this email directly, view it on GitHub
<#9527 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARXVUA53SIF5OAWJLK77HILYVIQPZAVCNFSM6AAAAABCTGNROGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSGQZTENJRGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Describe the problem you are having
when I try to start the addon on home assistant with version 0.13.0 I get thrown the error message that
Can't create container from addon_ccab4aaf_frigate: 400 Client Error for http+docker:https://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate: Bad Request ("invalid CapAdd: unknown capability: "CAP_PERFMON"")Version
0.13.0
Frigate config file
N/ARelevant log output
Can't create container from addon_ccab4aaf_frigate: 400 Client Error for http+docker:https://localhost/v1.41/containers/create?name=addon_ccab4aaf_frigate: Bad Request ("invalid CapAdd: unknown capability: "CAP_PERFMON"")FFprobe output from your camera
Frigate stats
N/AOperating system
Debian
Install method
HassOS Addon
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
N/A
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: