• 37 Posts
  • 34 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


























  • Several people have experienced this error: https://github.com/jellyfin/jellyfin/issues/15058

    It appears to be when the config of jellyfin lists the cache and the transcode in the same path (or if the transcode directory is within the cache directory).
    My understanding is that as the image starts, it writes these hidden dot files (.jellyfin-cache and .jellyfin-transcode) and checks for their existence before it will continue with the next load step.
    Hence why they keep coming back when you delete them.
    Complicating this is that if you are running jellyfin inside docker, the external mounts can confuse the internal mounts.
    (ie INSIDE the docker image you have them in /cache and /transcode, but OUTSIDE you have transcode and cache both mounted in /home/untouchedwagons/jellyfinstuff/)

    Within your running instance of 10.11.0, make sure the configuration for cache and transcode are in complete different directories (ie /cache and /config/transcoding-temp/), then shutdown the server (to save that configuration change).

    If that’s not clear, a little more info will be useful for diagnosing this.











  • Mountaineer@aussie.zoneOPtoSelfhosted@lemmy.world•Jellyfin 10.11.0 RC9
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    1 year ago

    I think the feel from the Devs is that there isn’t enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

    BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
    Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
    Such breakage is kind of the defining characteristic of a MAJOR version.