Closed esmoyer closed 2 years ago
This looks like the error that was fixed by https://github.com/blakeblackshear/frigate/pull/3147/commits/9c4da5a14c5d73a1a9493346d82e577b493f108f, seems it can't find ffmpeg
are you saying this doesn't happen when you remove hwaccel args? looking at the logs it seems this would happen regardless
Yes, it's happening regardless of the hwaccel args being commented out or not. Before the beta, I just had them commented out. But since installing the beta, I have tried a couple different variations. Am I missing something, wouldn't surprise me.
Can you confirm which architecture you are on? Were you previously pulling the amd64 image?
Okay cool, so the title isn't accurate. And no I don't think this is on you, seems something with the docker container. What CPU / arch are you running?
If you are able, it would be helpful if you could open a terminal inside the docker container and run ffmpeg --help
and see if ffmpeg is available
Correct. I was kind of wondering about that.
I was previously on 0.10.1-amd64
I am assuming you mean docker container (I run in a proxmox container). When I run ffmpeg --help
I get bash: ffmpeg: command not found
@blakeblackshear Seems like this may be related to proxmox? So far only proxmox users have reported this issue 🤔
Maybe having to do with this: https://jellyfin.org/docs/general/administration/hardware-acceleration.html#va-api-and-qsv-hardware-acceleration-on-lxc-on-proxmox
@esmoyer is the container that frigate runs in privileged?
It is a privileged container (as confusing as Proxmox states it)
Here is my container config, if that helps. I am looking through what you linked:
Looks like what I linked is about hw_accel so may not be it
I have the same issue, also running in a privileged Proxmox container. When attaching to the docker container I see:
[2022-05-18 21:10:01] watchdog.Hauseingang ERROR : Ffmpeg process crashed unexpectedly for Hauseingang. [2022-05-18 21:10:01] watchdog.Hauseingang ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : Assuming 131072kB available aperture size. [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : May lead to reduced performance or incorrect rendering. [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : get chip id failed: -1 [2] [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : param: 4, val: 0 [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : [AVHWDeviceContext @ 0x55deececa980] libva: /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so init failed [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : [AVHWDeviceContext @ 0x55deececa980] Failed to initialise VAAPI connection: 18 (invalid parameter). [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : Device creation failed: -5. [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Input/output error [2022-05-18 21:10:01] ffmpeg.Hauseingang.detect ERROR : Error parsing global options: Input/output error [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : Assuming 131072kB available aperture size. [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : May lead to reduced performance or incorrect rendering. [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : get chip id failed: -1 [2] [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : param: 4, val: 0 [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : [AVHWDeviceContext @ 0x55de4dfbb8c0] libva: /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so init failed [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : [AVHWDeviceContext @ 0x55de4dfbb8c0] Failed to initialise VAAPI connection: 18 (invalid parameter). [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : Device creation failed: -5. [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : Failed to set value '/dev/dri/renderD128' for option 'qsv_device': Input/output error [2022-05-18 21:10:01] ffmpeg.Hauseingang.record ERROR : Error parsing global options: Input/output error
If I should provide more information let me know. Thanks for your support and all the work :)
@blakeblackshear Seems like this may be related to proxmox? So far only proxmox users have reported this issue thinking
Ubuntu 20.04 user having same issue "FileNotFoundError: [Errno 2] No such file or directory: 'ffmpeg'"
@Zunhammer What you have there is not the same issue as this, can tell because ffmpeg is found it is just crashing with hw_accel args.
OK, thanks. Then maybe my config helps as I assume I'm one step ahead (ffmpeg found but crashing)
@Zunhammer I would recommend creating your own issue as we don't want to add clutter for those that are experiencing the ffmpeg not found issue.
Can someone post the output of echo $PATH
from within the container? This seems like something is overwriting the PATH env variable in the container.
root@e886c4d68cd3:/opt/frigate# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@e886c4d68cd3:/opt/frigate#
ffmpeg is at /usr/lib/jellyfin-ffmpeg/ffmpeg in blakeblackshear/frigate:0.11.0-beta2 container.
Yea. That's not right. The dockerfile clearly sets the PATH environment variable. Something is overwriting that value in the container.
Interesting. Want me to try doing a fresh install or anything else?
Yea. That's not right. The dockerfile clearly sets the PATH environment variable. Something is overwriting that value in the container.
That did it.
My container had “PATH” Environment variable set same as @esmoyer posting above. I delete the “PATH” variable using portainer and restart container and issue is fixed. I do notice new env variable is set Path = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jellyfin-ffmpeg Previous docker had path variable set so as breaking change you may need to tell people to manually change Path variable or rebuild container. Editing container using portainer to upgrade to 11 will result in bad path
Yea. That's not right. The dockerfile clearly sets the PATH environment variable. Something is overwriting that value in the container.
That did it.
Yep, just did the same thing and seems to be working now.
I had the same issue using portainer, environment path value was wrong. Originally my portainer was pulling blakeblackshear/frigate-amd65, now everything works without issue or editing after changing pull blakeblackshear/frigate
Describe the problem you are having
Looks like I'm getting green screens with the new beta build, which I assume is due to what you mentioned as I have not changed anything else with moving to the beta. Excited to get it going!
EDIT: Sorry my stats kept pasting weird. Let me know if you need more or other info!
Version
0.11.0-beta2
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
USB
Network connection
Wireless
Camera make and model
Amcrest AD410 and Eufy C22
Any other information that may be helpful
No response