• 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 Docker suddenly keeps restarting (worked previously)

     
    • 0 Vote(s) - 0 Average

    Docker suddenly keeps restarting (worked previously)

    ReaderGuy42
    Offline

    Junior Member

    Posts: 14
    Threads: 7
    Joined: 2023 Aug
    Reputation: 0
    #1
    2023-11-08, 08:51 AM (This post was last modified: 2023-11-08, 08:46 PM by ReaderGuy42. Edited 3 times in total.)
    My Jellyfin docker container went down yesterday and now won't stay up anymore. It was working perfectly for several weeks, but now there's some issue.

    With "docker container ls" I can see that the container is there, but is never up for more than 10 seconds before I get something like "Restarting (133) 3 seconds ago".

    I've removed the container and added it back again. I'm using docker run.

    Any advice?

    Thanks!

    I ran "docker logs --tail 50 --follow --timestamps jellyfin" and this is the output
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2023-11-08, 12:34 PM
    Can you share you entire Jellyfin log. Should be wherever the container path /config/logs is located.

    My guess is that when Jellyfin went down the DB was borked.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    ReaderGuy42
    Offline

    Junior Member

    Posts: 14
    Threads: 7
    Joined: 2023 Aug
    Reputation: 0
    #3
    2023-11-08, 08:11 PM (This post was last modified: 2023-11-08, 08:45 PM by ReaderGuy42. Edited 1 time in total.)
    [attachment=1048]
    (2023-11-08, 12:34 PM)TheDreadPirate Wrote: Can you share you entire Jellyfin log.  Should be wherever the container path /config/logs is located.

    My guess is that when Jellyfin went down the DB was borked.

    OK, sure, I'll attach them.

    This is the log from today. I doubt the juicy bit is here because today I just reinstalled it and it still wasn't working.


    Here is the log from yesterday, which is when it broke. I had to break it up into several files because of the attachment limits:


    Anything jump out?

    Thanks!!
    BobHasNoSoul
    Offline

    Junior Member

    Posts: 28
    Threads: 2
    Joined: 2023 Oct
    Reputation: 0
    #4
    2023-11-08, 08:14 PM
    okay so please confirm the following because you have i/o errors in your log that are quite strange

    you have a valid database file and make sure you have enough room on your drive and the permissions are correct.

    df -h may help you if you are on linux in seeing if you have low space on your drives.. if you are using your standard root drive look for the / option that is there.

    if there is a space issue fix it by deleting some things and maybe truncating your logs if they are big or removing temp files / old downloads.

    if there is a permission issue make sure you have chmod and chowned the item correctly for the user docker / jellyfin depending on your setup.. hang on... you might be able to make it work by just adding the uid and gid into your docker run for the root user (not that you should do that, but you could.. just saying) and that should sort the permissions issue out if that is it.
    HP ProLiant DL380 Gen9 142GB 56TB pool soon to be 80TB
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2023-11-08, 08:18 PM
    Code:
    Full: SQLitePCL.pretty.SQLiteException: database or disk is full

    What Bob said. Check that the disk your docker configs are on isn't full.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    ReaderGuy42
    Offline

    Junior Member

    Posts: 14
    Threads: 7
    Joined: 2023 Aug
    Reputation: 0
    #6
    2023-11-08, 08:43 PM
    Yup lmao, that was it. I had overloaded the disk. The Raspberry Pi still seems to have worked fine, but Jellyfin couldn't handle it. Deleted some stuff, now it's fine again. Thanks!!
    BobHasNoSoul
    Offline

    Junior Member

    Posts: 28
    Threads: 2
    Joined: 2023 Oct
    Reputation: 0
    #7
    2023-11-08, 08:48 PM
    no worries glad we could help
    HP ProLiant DL380 Gen9 142GB 56TB pool soon to be 80TB
    « 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