• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Updated to latest, synology NAS container now stuck in 'warning' status

     
    • 0 Vote(s) - 0 Average

    Updated to latest, synology NAS container now stuck in 'warning' status

    dow2491
    Offline

    Junior Member

    Posts: 6
    Threads: 3
    Joined: 2024 Jun
    Reputation: 0
    #1
    2024-06-02, 11:48 AM
    I decided to update my server today by following the steps I always do (outlined here:  https://www.youtube.com/watch?v=bTb7889qNxQ), but this time when I restarted the new container, it just sits in 'warning' status, these are the logs via Dozzle: https://i.imgur.com/zqgYqGc.png

    And this is how it looks in my Synology NAS: https://i.imgur.com/kJL6RyL.png


    I cannot access the server (the page just times out), any ideas on how I can troubleshoot this?
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,167
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #2
    2024-06-02, 02:06 PM (This post was last modified: 2024-06-02, 02:07 PM by Efficient_Good_5784. Edited 1 time in total.)
    From the Jellyfin v10.9.0 blog post:

    Quote:
    • Docker users: If you encounter problems loading your homepage, you may need to remove the DOTNET_SYSTEM_GLOBALIZATION_INVARIANT environment variable from your container, as this is no longer valid in Jellyfin 10.9.0.

    From your screenshots, I can see you have this variable enabled on your container. It's worth a shot to remove it to see if it helps here.

    Also, what Synology DSM version are you on? The video guide you linked is from 3 years ago before the current DSM v7.
    dow2491
    Offline

    Junior Member

    Posts: 6
    Threads: 3
    Joined: 2024 Jun
    Reputation: 0
    #3
    2024-06-03, 03:56 AM
    So strangely.. I left it running overnight in that status, and I've woke up this morning and it's working perfectly fine, with no changes made. Not sure why. Should I leave it as it is or remove that env variable?

    I am on DSM 7.2.1-69057 Update 3 at the moment, I can see there is Update 5 though. Is there a better way to update this container?
    fencer
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Mar
    Reputation: 0
    Country:Australia
    #4
    2024-06-14, 02:14 PM
    (2024-06-03, 03:56 AM)dow2491 Wrote: So strangely.. I left it running overnight in that status, and I've woke up this morning and it's working perfectly fine, with no changes made.

    Most likely an issue when Jellyfin is doing a big scan for changes, or migrating data or anything other sort of action on the library that doesn't happen every time. If you are running it in docker and have portainer you can look at the container logs to see what it's actually doing.
     I've found it locks up the server entirely until it completes. For instance I setup a new instance on a large media library with thumbnails for chapters to be extracted. I couldn't open jellyfish for 2 days, but could see the logs it was chugging away doing stuff.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode