mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
[10.7 unstable] Failure during the migration of DisplayPreferences database #2255
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#2255
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 @ferferga on GitHub (Nov 10, 2020).
System (please complete the following information):
To Reproduce
Logs
@QuaiGoner commented on GitHub (Dec 6, 2020):
Issue still persist with updating from 10.6.4 to 10.7.0 Rc-1
@ferferga commented on GitHub (Dec 6, 2020):
@QuaiGoner Are you sure the stack trace is exactly the same? Can you paste yours?
Maybe are you confused with #4634 ?
@linetrimmer commented on GitHub (Dec 17, 2020):
I think I'm running into this error (or a similar one) after trying to update from 10.6.4 to 10.7.0 rc1. I use the linuxserver docker image, and I get the following error after switching to the jellyfin/jellyfin:stable-rc image (and updating the docker environment variables). I also tried the linuxserver/jellyfin:nightly image, but I still get the error.
@ggogel commented on GitHub (Dec 27, 2020):
I'm still seeing this error when migrating from 1.6.4 to 1.7.0-rc1 and unstable on docker. The fix should be in the unstable build right?
@ggogel commented on GitHub (Dec 27, 2020):
Fixed the issue. I opened the displaypreferences.db with a db browser and found that one user had two entries for the client emby and another user had two entries for the client ATV. After I deleted one of each, jellyfin was able to run the db migration.
@ggogel commented on GitHub (Dec 27, 2020):
Ok looks like the homescreen settings for my user are broken now. Changes in the settings are not applied.
@ggogel commented on GitHub (Dec 27, 2020):
This time I only deleted all rows with client = ATV. Jellyfin was able to run the migration afterwards. Home settings are still broken. The settings are not carried over and can not be changed anymore.
@ferferga commented on GitHub (Dec 27, 2020):
@ggogel The fix for this is not in RC1, is currently in the master branch, which will be backported to RC2 and, consequently, stable.
If you want to test that out, make sure you're pulling unstable from docker or our repositories.
@ggogel commented on GitHub (Dec 27, 2020):
@ferferga Even with the unstable it's still failing.
@ggogel commented on GitHub (Dec 27, 2020):
Log from the unstable build:
@ggogel commented on GitHub (Dec 27, 2020):
Another attempt: Deleted all rows in the table. Jellyfin starts but home settings are still broken. I'm out of ideas at this point. Jellyfin does either not start and if I alter the database it starts but the settings can't be changed anymore. No idea if this is related or home settings are just broken in general.
@ggogel commented on GitHub (Dec 27, 2020):
I've created a test user and it has the same issue. So I guess this is not related to the migration issue, instead altering the home settings seems to broken in general.
@ferferga commented on GitHub (Dec 27, 2020):
@ggogel Are you removing the old containers after pulling the latest image?
It's a common thing that happens (it happens to me a lot in fact), but you should remove previous stopped containers instances, otherwise docker will attempt to rerun those (with the older images)
This in case you're using bare metal Docker, if you use
docker-compose, it will already handle this after adocker-compose pullordocker pull jellyfin/jellyfin:unstableAlso, this seems obvious, but just to make sure: are you running the stable to unstable upgrade paths with the original database? Or with the one you modified manually?
@ggogel commented on GitHub (Dec 27, 2020):
@ferferga Yes of course I'm deleting the container. I have created a backup copy of the volume from my 10.6.4 production instance, which I then copy to test the migration.
I tried the following migration paths:
10.6.4 -> stable-rc
10.6.4 -> unstable
Both fail to migrate. The database seems to have a couple of broken / duplicated entries for ATV clients. When I delete all rows with client = ATV, the migration proceeds.
So we are having two issues here:
@ggogel commented on GitHub (Dec 27, 2020):
I tested the unstable build some more to reproduce the error.
It behaves like this:
When opening the Home settings I'm getting the following error:
@ggogel commented on GitHub (Dec 29, 2020):
@ferferga just tried the latest unstable image and both issues have been fixed for me! Meaning that the migration is able to handle my database and the home settings stick.
@ferferga commented on GitHub (Dec 29, 2020):
@ggogel Great news, thank you very much for reporting back! 👍
@eh8 commented on GitHub (Jan 8, 2021):
Happens when migrating from 10.6.4 to 10.7.0rc2 on Arch Linux ARM.
Workaround is to delete InfuseSync 1.2.4 in
/plugins/@ferferga commented on GitHub (Jan 8, 2021):
@eh8 Completely unrelated to the original issue.
Plugins are still not compatible with 10.7, they will on release
@eh8 commented on GitHub (Jan 8, 2021):
I can create another issue if this is not relevant to the original problem.
The point I suppose is whether it is possible to gracefully ignore incompatible plugins on startup rather than throw the entire process.
@ferferga commented on GitHub (Jan 8, 2021):
@eh8 This should be the case in unstable already.