-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JellyFin media paths (no longer?) match. #6194
Comments
The path Is this really an issue? |
|
Yes, it is a problem, because Jellyfin will not resolve the symlink when validating library paths. The paths in the database were recorded as
Then when the frontend wants to enumerate the libray paths ('virtual folders' in Jellyfin API terms), it only lists partial information, lacking the item ids, because the user root path is not a prefix of the recorded library path. Locally, I've worked around the problem now by shutting down jellyfin, updating the sqlite database and It is likely that this was an issue with my installation for quite some time, but I didn't have reason to change library configuration until the latest release (which added Trickplay support I wanted to enable). |
@mreid-tt sorry to bother you, I ask you, since you recently updated jellyfin in #6254. For me this looks like a design error in jellyfin. |
The startup parameters -d, -C, and -c in the service-setup.sh file have remained unchanged since the initial package release three years ago. While adjusting the startup arguments is possible, it may not have a significant effect. If these values are stored in the database, any changes might not benefit existing installations without also modifying the database, so testing will be necessary. Regarding the reported issue, the specific impact on the user is still unclear. Could you please provide more details? It was mentioned that:
Additional context around this behavior would be helpful. |
Is this a new Bug?
Package Name
jellyfin
Package Version
10.9.7-15
Device Model
DS1522+
Device Architecture
x86_64
Firmware Version
DSM 7.2.1-69057 Update 5
What happened?
I can't update settings for media libraries. I traced this to their path names in the database no longer matching what Jellyfin thinks is the root URL.
In the jellyfin config file
config/system.xml
, the media data path is configured as:and in the
data/data/library.db
sqlite database, the media paths are listed with that prefix:This is as it should be. However, during startup, the following messages are logged (I configured debug level logging for extra context):
Note the
Resetting user root folder path
message there; the/var/packages/jellyfin/var/data/metadata
media root path has been replaced with/volume1/@appdata/jellyfin/data/root/default
. Clearly Jellyfin has different ideas of where things should live, and I suspect it is the-c
switch to the-d /volume1/@appdata/jellyfin/data
switch passed to jellyfin on startup.Now, when you want to edit library settings, the prefix for each path must match the user root folder path. The library will show up in the UI but it is missing a ItemID identifier, at which point the web ui balks and things just silently fail.
Now, I am pretty sure this all used to work. Did the
-c
value change, and if so, can it be returned to use the symlinked path?Reproduction steps
Hard to write down a recipe for reproduction; you'd have to manually ensure your sqlite database paths use the symlink paths.
Install Log
Log File
Service Log
No response
Other Logs
No response
The text was updated successfully, but these errors were encountered: