mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[Issue]: upgrade from v10.9.3 -> v10.9.6 is has corrupted library.db #5969
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#5969
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 @vbatts on GitHub (Jun 8, 2024).
Please describe your bug
I run jellyfin from the docker container on linux/amd64.
just upgraded from the image with v10.9.3 (
docker.io/jellyfin/jellyfin@sha256:63136341d22edc06208a1392d544f064784dda7ac0955b2ee1da3f81cbed10ec)to the image with v10.9.6 (
docker.io/jellyfin/jellyfin@sha256:15579ab64a14f9e3dce043c076df148e9de9631f11c9b3f614f1fbad868db701)and the server is in a fail-loop attempting to start: see attached logs
It's tried 30+ times just now, curiously resulting in different sized library.db many times:
Reproduction Steps
docker.io/jellyfin/jellyfin@sha256:63136341d22edc06208a1392d544f064784dda7ac0955b2ee1da3f81cbed10ecdocker.io/jellyfin/jellyfin@sha256:15579ab64a14f9e3dce043c076df148e9de9631f11c9b3f614f1fbad868db701Jellyfin Version
10.9.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@jellyfin-bot commented on GitHub (Jun 8, 2024):
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
@gnattu commented on GitHub (Jun 8, 2024):
If you have any kind of timeout mechanisms that will kill a container if the health check fails, please remove that.
Upgrades beyond 10.9.3 requires a db migration that would take some time to finish and if you or your container manager is not patient enough to kill if because the container seems to be "unhealthy", it will kill your db file.
For this exact reason we backup your entire db before doing that. As you can see you have tons of db backups now.
Please use the
library.db.bak2which seems like the first backup before this migration to restorelibrary.db, don't forget to take another backup, then run the container again without all kind of auto-killing feature, be patient to let the migration complete.@vbatts commented on GitHub (Jun 8, 2024):
oh interesting. That HealthCheck is declared by the image publisher
@gnattu commented on GitHub (Jun 8, 2024):
But the health check itself should not restart your container, it will only indicate that the container is not responding to the health check message.
@vbatts commented on GitHub (Jun 8, 2024):
totally get that, and I can/will disable it to get through this. But since this image is from the publisher, as well as the migration that is taking a long time, perhaps that healthcheck endpoint ought to be brought up during a migration to indicate the application is healthy even if it's currently occupied in a migration.
@Fabien98 commented on GitHub (Jul 3, 2024):
Hello i'm facing the same error.
I'm running Jellyfin through Debian on a VM.
Each time I try to update Jellyfin to a >10.9.3 version, my
library.dbgets corrupted.I tried to replace
library.dbwith a backup, as stated above, but no success..Here's the log where the corruption seems to happen?
@felix920506 commented on GitHub (Jul 6, 2024):
Please head to our forum or chat rooms for support. https://jellyfin.org/contact