mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
ffmpeg error #6446
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#6446
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @prabhu-madanagopal on GitHub (Nov 9, 2024).
This issue respects the following points:
Description of the bug
After upgrading to 10.10.1, the server does not start due to ffmpeg error.
The error is not very specific, I tried upgrading the jellyfin-ffmpeg version in openmediavault to 7.0.2-Jellyfin, but the issue is the same.
Attaching the logs.
Jellyfin Log from OpenMediaVault.log
Reproduction steps
What is the current bug behavior?
The server keeps bouncing with the error in the log attached to description.
What is the expected correct behavior?
Server starts sucessfully and I can reach it from browser.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
Cannot go to dashboard
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@felix920506 commented on GitHub (Nov 9, 2024):
Looks like a packaging issue. Please ask for support with Linuxserver
https://www.linuxserver.io/support
@nyanmisaka commented on GitHub (Nov 9, 2024):
Do not set these irrelevant volumes, it will break the existing ffmpeg and related libraries inside the container.
@prabhu-madanagopal commented on GitHub (Nov 10, 2024):
Now server startups without the ffmpep error after removing as suggested. Thank you very much.