• 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 Autostart of Jellyfin/Jellyfin container

     
    • 0 Vote(s) - 0 Average

    Autostart of Jellyfin/Jellyfin container

    Autostart of Jellyfin/Jellyfin container in my Proxmox Vm not working
    Eisbergsalat
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Germany
    #1
    2024-07-15, 11:24 AM (This post was last modified: 2024-07-15, 11:27 AM by Eisbergsalat.)
    [*]Hey there,

    [*]Before I start:
    [*]This problem could actually be something with the published Jellyfin/Jellyfin container or with docker itself. I personally thought its most likely the first. Thats why I am here in this Forum.

    [*]
    • The version of Jellyfin you are running:
    •      10.9.7

    [*]
    • Your installation method and platform (e.g. Linux Docker, Debian repository, Windows installer, etc.)
           Jellyfin/Jellyfin Container in einer (priviliged) Proxmox VM

    [*]
    • A brief description of the issue as your thread subject, using the description for additional important context only if required -> description
      (Im new here. Whats the difference between "Thread Subject" and "Description"?)

    [*]
    • A full explanation of what is happening, versus what you expect to happen

    [*]Expactaion:
    [*]At 0:30 Proxmox shuts down every VM to reboot the whole Server. After reboot All VM restart. The Docker-VM starts and automatically starts all Containers including Jellyfin.
    [*]
    Reality:
    [*]Proxmox works great at restarting!
    [*]All VMs are restarting! (obviously this is the Jellyfin-Forum, I am getting to it :D)
    [*]Inside of my Docker-VM almost all containers restart normally (Adguard, Dashy, Nextcloud, RustDesk, NginxProxyManager, Pufferpanel and Vaultwarden)
    [*]Only the Jellyfin-container doesnt start.


    [*]But If I reboot the whole Server manually everything works fine


    [*]
    • What client(s) you are using and how the issue manifests
           Server is unrechable on any device, because the container isn't running.

    [*]
    • Any other context you might think is relevant
    "docker-compose.yml":

    Code:
    version: '3.5'
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        user: 1001:1001
        ports:
          - "8096:8096"
          - "8920:8920"
          - "7359:7359/udp"
          - "1900:1900/udp"
        volumes:
          - /Jellyfin/config:/config
          - /Jellyfin/cache:/cache
          - type: bind
            source: /mnt/Medien
            target: /media
        restart: always
        # Optional - alternative address used for autodiscovery
        environment:
          - JELLYFIN_PublishedServerUrl=https://#########.duckdns.org/
        # Optional - may be necessary for docker healthcheck to pass if running in host network mode
        #extra_hosts:
        #  - "host.docker.internal:host-gateway"

    Due to the VM containing a few more containers as well as Adguard, I cant use host-mode


    Specific Logs from Jellyfin with shutdown at 10:35 and manual reboot at 11:47:
    Code:
    [2024-07-14 00:35:33.460 +00:00] [INF] [35] Emby.Server.Implementations.Session.SessionManager: Sending shutdown notifications
    [2024-07-14 00:35:33.487 +00:00] [INF] [33] Jellyfin.Networking.PortForwardingHost: Stopping NAT discovery
    [2024-07-14 00:35:33.515 +00:00] [INF] [33] Main: Running query planner optimizations in the database... This might take a while
    [2024-07-14 00:35:33.541 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/####/Buecher/Comedy"
    [2024-07-14 00:35:33.549 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/ #### /Filme"
    [2024-07-14 00:35:33.550 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/ #### /Buecher/E-Books"
    [2024-07-14 00:35:33.550 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/ #### /Buecher/Audiobooks"
    [2024-07-14 00:35:33.551 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/ #### /Musik"
    [2024-07-14 00:35:33.552 +00:00] [INF] [33] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "/ #### /Serien"
    [2024-07-14 00:35:33.869 +00:00] [INF] [33] Emby.Server.Implementations.ApplicationHost: Disposing "CoreAppHost"
    [2024-07-14 00:35:33.869 +00:00] [INF] [33] Emby.Server.Implementations.ApplicationHost: Disposing "MusicBrainzArtistProvider"
    [2024-07-14 00:35:33.870 +00:00] [INF] [33] Emby.Server.Implementations.ApplicationHost: Disposing "MusicBrainzAlbumProvider"
    [2024-07-14 00:35:33.870 +00:00] [INF] [33] Emby.Server.Implementations.ApplicationHost: Disposing "PluginManager"
    [2024-07-14 11:47:34.567 +00:00] [INF] [1] Main: Jellyfin version: "10.9.7"


    '####' - sind von mir unkenntlich gemacht. Ist ein privater Server, der nicht mehr als 5 Personen bewirtschaften kann.


    Die VM ist aktuell (apt update && apt upgrade). Es handelt sich um einen headless Ubuntu (22.04.4 LTS) Server


    Ich vermute mal, dass das nicht ausreicht, um den Fehler einzugrenzen. Ich weiß aber auch grad nicht was ich noch hinzufügen soll.

    Was ich noch nicht gemacht hab. Und das werd ich gleich mal versuchen: Den Jellyfin auf z.B. 10.9.2 downgraden
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-07-15, 05:47 PM
    The next time this happens run "sudo docker logs jellyfin" which should show any docker specific logs that aren't written to the Jellyfin log. The way you have things setup, docker should be starting the container.
    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]
    Eisbergsalat
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Germany
    #3
    2024-07-17, 04:27 PM
    With "sudo docker logs jellyfin" I get the same logs, that are in the OP.

    The shutdown process is normal.
    The container just wont start, if it is an automatic reboot.

    One problem could be Adguard?
    I run Adguard on the same VM as Jellyfin.
    Does the newer version of Jellyfin need an active network connection to startup?
    Adguard is my local DNS-Server

    Today I downgraded the Jellyfinversion to 10.9.2
    If that doesnt work I will try using more previous versions like 10.

    Oh and sorry if I might take a few days to answer Ill try to answer as soon ass possible. I cant really take a lot of time for my Server administration at the moment.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-07-17, 05:28 PM
    Try to view the docker daemon logs with this command.

    Code:
    sudo journalctl -xu docker.service
    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]
    Eisbergsalat
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Germany
    #5
    2024-08-15, 06:12 AM (This post was last modified: 2024-08-15, 06:20 AM by Eisbergsalat. Edited 1 time in total.)
    Soooooo..
    I..
    - downgraded to version 9 - no difference (went back to :latest)
    - changed the docker daemon.json experimental from true to false - no difference (Dont even know why I did That! Found that thanks to "journalctl -xu docker.service")
    - fixed a DNS Error for the docker resolver - no difference obviously, if docker cant reach the Internet, the containers can still reach it. But the log shouldnt get used as garbage again (Also thanks to "journalctl -xu docker.service")
    - Found out, that Nextcloud doesnt start right away because of Mounting-Problems. But thats soemthing NC tells me in the Windows-client every 5 damn minutes Grinning-face...  WiP but not relevant for this
    - Get a lot of "ShouldRestart failed, container will not be restarted" container=... But that is before shutdown and the other listed containers startup as usally after the reboot.
    - I also changed the chmod so that everyone can run the docker compose. (chmod a+x...)

    I dont know why I cant copy the log from Putty at the moment... If I can, I will post it later.



    Currently I am using a rather unwanted fix:
    I created the "JellyfinStartup.sh" in the same folder as the docker compose file Grinning-face

    Code:
    docker compose down
    sleep 60
    docker compose up -d

    and in crontab -e
    Code:
    45 2 * * * ....JellyfinStartup.Sh...




    At the End of September I will be able to focus more on this, as the deadline of my Uni assignement ist at the beginning of Sep and the corresponding oral exam is at the end of Sep.



    Edit:
    Found out why I couldnt copy, it was an other programm with an invisible error message
    I didnt try out the new .sh fix yet, so I will post the logs tomorrow.
    Hopefully without as much clutter as I had till today Grinning-face
    Eisbergsalat
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Germany
    #6
    2024-08-16, 12:34 PM
    And now with the Log. I copied it from Putty directly with "Copy all to Clipboard". So some lines are cut off.
    I fully copied those, that might point to the problem. If there are some lines that I should post completely please tell me.
    (After I finished, I remebered that I could have just downloaded the whole file... now its to late... Well I only started about 2 years ago with the whole Linux thing)






    Code:
    Aug 16 00:35:33 youngdocker systemd[1]: Stopping Docker Application Container Engine...
    ░░ Subject: A stop job for unit docker.service has begun execution
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ A stop job for unit docker.service has begun execution.
    ░░
    ░░ The job identifier is 4443.
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.252755077Z" level=info msg="Processing signal 'terminated'"
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.486114817Z" level=info msg="ignoring event" container=b4XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.507901907Z" level=info msg="ignoring event" container=d6XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.633672917Z" level=info msg="ignoring event" container=fbXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.634317967Z" level=info msg="ignoring event" container=e5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.651180199Z" level=info msg="ignoring event" container=ffXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.651743968Z" level=info msg="ignoring event" container=d2XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.687667896Z" level=info msg="ignoring event" container=42XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.739226153Z" level=info msg="ignoring event" container=e2XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.750027587Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=d2XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.750224389Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=d6XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.750298545Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=ffXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.752090347Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=fbXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.768063227Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=b4XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.798294628Z" level=info msg="ignoring event" container=51XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.805013223Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=42XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.821763510Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=e5XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.821956706Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=e2XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:33 youngdocker dockerd[92310]: time="2024-08-16T00:35:33.843460524Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=51XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.221585511Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:37131" dns-server="udp:10.1.0.1:53" error="read udp 172.25.0.>
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.221624333Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:53776" dns-server="udp:10.1.0.1:53" error="read udp 172.25.0.>
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.221793978Z" level=warning msg="[resolver] connect failed" error="dial udp [XXXXX___IPv6_local_DNS___XXXXX]:53: connect: network is unreachable"
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.221841097Z" level=warning msg="[resolver] connect failed" error="dial udp [XXXXX___IPv6_local_DNS___XXXXX]:53: connect: network is unreachable"
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.400576594Z" level=info msg="ignoring event" container=b6XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:35 youngdocker dockerd[92310]: time="2024-08-16T00:35:35.420955779Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=b6XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.678719671Z" level=info msg="ignoring event" container=01XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.699809753Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=01XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.719311783Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:41680" dns-server="udp:10.1.0.1:53" error="read udp 172.25.0.>
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.719348323Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:60409" dns-server="udp:10.1.0.1:53" error="read udp 172.25.0.>
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.719992456Z" level=warning msg="[resolver] connect failed" error="dial udp [XXXXX___IPv6_local_DNS___XXXXX]:53: connect: network is unreachable"
    Aug 16 00:35:36 youngdocker dockerd[92310]: time="2024-08-16T00:35:36.720058582Z" level=warning msg="[resolver] connect failed" error="dial udp [XXXXX___IPv6_local_DNS___XXXXX]:53: connect: network is unreachable"
    Aug 16 00:35:37 youngdocker dockerd[92310]: time="2024-08-16T00:35:37.888346938Z" level=info msg="ignoring event" container=41XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:37 youngdocker dockerd[92310]: time="2024-08-16T00:35:37.907650406Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=41XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:40 youngdocker dockerd[92310]: time="2024-08-16T00:35:40.720206362Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:45828" dns-server="udp:8.8.8.8:53" error="read udp 172.25.0.8>
    Aug 16 00:35:40 youngdocker dockerd[92310]: time="2024-08-16T00:35:40.720313848Z" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:172.25.0.8:39034" dns-server="udp:8.8.8.8:53" error="read udp 172.25.0.8>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.365445413Z" level=info msg="Container failed to exit within 10s of signal 3 - using the force" container=b10a8cb22e84c9fa7afff8c8d7ba8c2ab4033b88acff53276114a9ecd11fb>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.403430494Z" level=info msg="ignoring event" container=b1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.424959877Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=b1XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.438649295Z" level=info msg="Container failed to exit within 10s of signal 15 - using the force" container=54fe20ba61330530b815b807afcb94b497157451c09f159dc315372d2871>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.455241168Z" level=info msg="Container failed to exit within 10s of signal 28 - using the force" container=684fac9f01cfbfbf98cb275eb993a11aef28fb6ed5be0a09e39ea2f70559>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.496823495Z" level=info msg="ignoring event" container=68XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/task>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.516984338Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=68XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.576681065Z" level=error msg="stream copy error: reading from a closed fifo"
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.577413462Z" level=error msg="stream copy error: reading from a closed fifo"
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.596544043Z" level=info msg="ignoring event" container=54XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.599755276Z" level=warning msg="Health check for container 54XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX error: OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown"
    Aug 16 00:35:43 youngdocker dockerd[92310]: time="2024-08-16T00:35:43.618617383Z" level=warning msg="ShouldRestart failed, container will not be restarted" container=54XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX daemo>
    Aug 16 00:35:44 youngdocker dockerd[92310]: time="2024-08-16T00:35:44.139449643Z" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
    Aug 16 00:35:44 youngdocker dockerd[92310]: time="2024-08-16T00:35:44.140545155Z" level=info msg="Daemon shutdown complete"
    Aug 16 00:35:44 youngdocker systemd[1]: docker.service: Deactivated successfully.

    ░░ Subject: Unit succeeded
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ The unit docker.service has successfully entered the 'dead' state.
    Aug 16 00:35:44 youngdocker systemd[1]: Stopped Docker Application Container Engine.
    ░░ Subject: A stop job for unit docker.service has finished
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ A stop job for unit docker.service has finished.
    ░░
    ░░ The job identifier is 4443 and the job result is done.
    Aug 16 00:35:44 youngdocker systemd[1]: docker.service: Consumed 5min 58.032s CPU time.
    ░░ Subject: Resources consumed by unit runtime
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ The unit docker.service completed and consumed the indicated resources.
    -- Boot a130f49d66544bdd8708f30066cb6c79 --
    Aug 16 00:37:14 youngdocker systemd[1]: Starting Docker Application Container Engine...
    ░░ Subject: A start job for unit docker.service has begun execution
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ A start job for unit docker.service has begun execution.
    ░░
    ░░ The job identifier is 155.
    Aug 16 00:37:15 youngdocker dockerd[937]: time="2024-08-16T00:37:15.363140146Z" level=info msg="Starting up"
    Aug 16 00:37:15 youngdocker dockerd[937]: time="2024-08-16T00:37:15.794664221Z" level=info msg="[graphdriver] using prior storage driver: overlay2"
    Aug 16 00:37:16 youngdocker dockerd[937]: time="2024-08-16T00:37:16.248067416Z" level=info msg="Loading containers: start."
    Aug 16 00:37:17 youngdocker dockerd[937]: time="2024-08-16T00:37:17.600813350Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
    Aug 16 00:37:18 youngdocker dockerd[937]: time="2024-08-16T00:37:18.520363980Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:18 youngdocker dockerd[937]: time="2024-08-16T00:37:18.663961580Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:18 youngdocker dockerd[937]: time="2024-08-16T00:37:18.716062563Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:18 youngdocker dockerd[937]: time="2024-08-16T00:37:18.898107588Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:19 youngdocker dockerd[937]: time="2024-08-16T00:37:19.026728039Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:19 youngdocker dockerd[937]: time="2024-08-16T00:37:19.164193172Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:19 youngdocker dockerd[937]: time="2024-08-16T00:37:19.219447498Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:19 youngdocker dockerd[937]: time="2024-08-16T00:37:19.339838600Z" level=warning msg="Security options with `:` as a separator are deprecated and will be completely unsupported in 17.04, use `=` instead."
    Aug 16 00:37:22 youngdocker dockerd[937]: time="2024-08-16T00:37:22.358178676Z" level=error msg="stream copy error: reading from a closed fifo"
    Aug 16 00:37:22 youngdocker dockerd[937]: time="2024-08-16T00:37:22.364623813Z" level=error msg="stream copy error: reading from a closed fifo"
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.016881446Z" level=error msg="failed to start container" container=54XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX error="failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting \"/mnt/Medien\" to rootfs at \"/media\": mount /mnt/Medien:/media (via /proc/self/fd/6), flags: 0x5000: no such device: unknown"
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.016983996Z" level=info msg="Loading containers: done."
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.093654436Z" level=info msg="Docker daemon" commit=f9522e5 containerd-snapshotter=false storage-driver=overlay2 version=27.1.2
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.096379873Z" level=info msg="Daemon has completed initialization"
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.270296268Z" level=info msg="API listen on /run/docker.sock"
    Aug 16 00:37:24 youngdocker systemd[1]: Started Docker Application Container Engine.
    ░░ Subject: A start job for unit docker.service has finished successfully
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░
    ░░ A start job for unit docker.service has finished successfully.
    ░░
    ░░ The job identifier is 155.


    Especially this line might be the clue to the perpetrator:
    Code:
    Aug 16 00:37:24 youngdocker dockerd[937]: time="2024-08-16T00:37:24.016881446Z" level=error msg="failed to start container" container=54XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX error="failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting \"/mnt/Medien\" to rootfs at \"/media\": mount /mnt/Medien:/media (via /proc/self/fd/6), flags: 0x5000: no such device: unknown"
    .

    I looked into it and found out, that OMV (extra VM in Proxmox) is restarting at 2:30am and not fully back online until 3:00am.
    In the time until 2:30 Adguard as well as my Router is also restarting interfering with my network.
    It could be, that my Media folder is unreachable during container setup. So I will change the cron to 3:10 and I will also add "sleep 60" to the end (so that the script stays active during "docker compose up -d").
    I think changing the docker compose file to "restart: never" is out of question. As I intend to restart the server sometimes during daytime.


    And again: Tomorrow I will know more Upside-down-face
    Eisbergsalat
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Jul
    Reputation: 0
    Country:Germany
    #7
    2024-09-29, 01:06 PM
    "Tomorrow" I said Woozy-face

    Hey there, I am back.

    I got in some time management conflicts due to uni exams.
    AND then I got a new router and suddenly I had that DS-lite infection .......  Face-with-head-bandage

    BUT that got sorted out and now I am back to report my status in this problem:

    It works! Smiling-face



    What did I do?

    1. Create an JellyfinStartup.sh:
    Code:
    #!/bin/bash
    # Logger aktivieren:
    exec > >(logger -t JellyfinStartup) 2>&1

    # URL des Servers
    SERVER_URL="http://[IP:Port or URL]/" ###########EDIT###########


    # Funktion zum Überprüfen der Erreichbarkeit des Servers
    check_server() {
        status_code=$(curl -s -o /dev/null -w "%{http_code}" $SERVER_URL)
        if [ "$status_code" -eq 200 ] || [ "$status_code" -eq 302 ]; then
            return 0
        else
            return 1
        fi
    }

    # Funktion zum Überprüfen, ob eine Datei existiert
    file_exists() {
        [ -f "$1" ]
    }


    # Hauptlogik
    if check_server; then
        echo "Server ist erreichbar."
        exit 0
    else
        echo "Server ist nicht erreichbar. Neustart von docker-compose.yaml..."
        docker compose -f /path_to_yaml_file/docker-compose.yml down ###########EDIT###########
        sleep 5

    if ! file_exists "/mnt/[any consistent file inside a mounted drive, that is used by the Jellyfin-container. Be aware, that the folder itself wont work, because the folder of the mounted drive exists, even if it is unmounted!]"; then ###########EDIT###########
            umount /mnt/Medien
            sleep 4
            mount -a
            sleep 1
        fi
        sleep 15
        docker compose -f /path_to_yaml_file/docker-compose.yml up -d ###########EDIT###########
        sleep 60

        if check_server; then
            echo "Server ist erreichbar."
            exit 0
        else
            systemctl daemon-reload
            systemctl restart remote-fs.target
            sleep 60  # 1 Minute warten
            docker compose -f /path_to_yaml_file/docker-compose.yml up -d ###########EDIT###########
            sleep 60
            if check_server; then
                echo "Server ist erreichbar."
                exit 0
            else
                echo "Server ist noch nicht erreichbar. Neustart des Systems..."
                sleep 5
                reboot
                sleep 55
                exit 1
            fi
        fi
    fi

    2. Create an crontab -e entry (as root)
    Code:
    @reboot sleep 300 && /path_to_script/JellyfinStartup.sh


    Info:
    I created this script with the help of copilot. (At least a thousand times I had to express my wishes)

    And this script was created in order to reboot Jellyfin, because the linked mounted drive (in my case SMB) is not available during startup.

    If you need this script, dont forget to edit those lines, where I added " ###########EDIT########### " at the end.
    « 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