• 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 Jellyfin LXC failure

    Pages (2): « Previous 1 2

     
    • 0 Vote(s) - 0 Average

    Jellyfin LXC failure

    drindor83
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    Country:Austria
    #11
    2025-02-26, 09:55 PM
    (2025-02-26, 09:35 PM)TheDreadPirate Wrote: Try disabling it anyway.  Real time monitoring of SMB shares doesn't work the same as it would on a local disk.

    Ok, will try that
    drindor83
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    Country:Austria
    #12
    2025-03-02, 10:58 AM (This post was last modified: 2025-03-02, 11:16 AM by drindor83. Edited 1 time in total.)
    Have to report, the problem is ongoing, today at 09:35 it crashed again Confused-face

    I had found this in my ubuntu log:

    Code:
    Mär 02 09:34:47 Jellyfin systemd[1]: jellyfin.service: A process of this unit has been killed by the OOM killer.
    Mär 02 09:34:47 Jellyfin systemd[1]: jellyfin.service: Main process exited, code=killed, status=9/KILL
    Mär 02 09:34:47 Jellyfin systemd[1]: jellyfin.service: Failed with result 'oom-kill'.
    Mär 02 09:34:47 Jellyfin systemd[1]: jellyfin.service: Consumed 16h 18min 28.251s CPU time.
    Mär 02 09:34:47 Jellyfin systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 1.
    Mär 02 09:34:47 Jellyfin systemd[1]: Started jellyfin.service - Jellyfin Media Server.
    Mär 02 09:34:47 Jellyfin (jellyfin)[38670]: jellyfin.service: Referenced but unset environment variable evaluates to an empty string: JELLYFIN_NOWEBAPP_OPT, JELLYFIN_SERVICE_OPT

    It seems there is a memory leak ongoing , I found a post on github, from a user which has a similar problem with the jellyfin version after 10.9.x .

    My LXC has enough memory, 8GB, so thats not the probleme here, because it uses barely 3-4GB in use.

    In the jellfin log file I found that:

    Code:
    [2025-03-02 08:59:34.988 +00:00] [WRN] As of "03/02/2025 08:59:34 +00:00", the heartbeat has been running for "00:00:01.3583598" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 08:59:39.194 +00:00] [WRN] As of "03/02/2025 08:59:39 +00:00", the heartbeat has been running for "00:00:01.2016099" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:00:08.625 +00:00] [WRN] As of "03/02/2025 09:00:08 +00:00", the heartbeat has been running for "00:00:01.2362687" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:00:22.189 +00:00] [WRN] As of "03/02/2025 09:00:22 +00:00", the heartbeat has been running for "00:00:01.1743263" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:00:22.724 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:00:22.821 +00:00] [INF] Validating media library
    [2025-03-02 09:00:24.051 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:01:27.041 +00:00] [WRN] As of "03/02/2025 09:01:26 +00:00", the heartbeat has been running for "00:00:01.3563147" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:01:32.244 +00:00] [WRN] As of "03/02/2025 09:01:32 +00:00", the heartbeat has been running for "00:00:01.0570985" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:01:50.253 +00:00] [WRN] As of "03/02/2025 09:01:50 +00:00", the heartbeat has been running for "00:00:01.5344288" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:01:54.224 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:01:55.965 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:03:27.143 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:03:27.251 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:04:16.367 +00:00] [WRN] As of "03/02/2025 09:04:16 +00:00", the heartbeat has been running for "00:00:01.3968746" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:04:59.085 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:04:59.315 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:05:17.894 +00:00] [WRN] As of "03/02/2025 09:05:17 +00:00", the heartbeat has been running for "00:00:01.6244114" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:05:48.374 +00:00] [WRN] As of "03/02/2025 09:05:48 +00:00", the heartbeat has been running for "00:00:02.3567002" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:06:03.463 +00:00] [WRN] As of "03/02/2025 09:06:01 +00:00", the heartbeat has been running for "00:00:02.3253890" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:06:24.238 +00:00] [WRN] As of "03/02/2025 09:06:24 +00:00", the heartbeat has been running for "00:00:02.3457148" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:06:30.201 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:06:31.134 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:08:01.383 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:08:02.261 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:08:13.942 +00:00] [WRN] As of "03/02/2025 09:08:13 +00:00", the heartbeat has been running for "00:00:01.5037062" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:09:33.236 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:09:33.377 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:10:37.889 +00:00] [WRN] As of "03/02/2025 09:10:37 +00:00", the heartbeat has been running for "00:00:01.9281627" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:10:57.311 +00:00] [WRN] As of "03/02/2025 09:10:57 +00:00", the heartbeat has been running for "00:00:04.4894598" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:11:05.252 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:11:05.398 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:12:36.555 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:12:36.706 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:14:08.106 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:14:08.263 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:14:55.477 +00:00] [INF] "Scanne Medien-Bibliothek" Completed after 14 minute(s) and 32 seconds
    [2025-03-02 09:15:26.212 +00:00] [WRN] As of "03/02/2025 09:15:26 +00:00", the heartbeat has been running for "00:00:02.7899049" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:15:39.866 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:15:40.868 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:15:56.188 +00:00] [WRN] As of "03/02/2025 09:15:56 +00:00", the heartbeat has been running for "00:00:03.0573846" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:16:10.843 +00:00] [WRN] As of "03/02/2025 09:16:10 +00:00", the heartbeat has been running for "00:00:04.5726877" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:16:23.203 +00:00] [WRN] As of "03/02/2025 09:16:23 +00:00", the heartbeat has been running for "00:00:02.5071470" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:16:24.462 +00:00] [INF] Validating media library
    [2025-03-02 09:16:35.051 +00:00] [WRN] As of "03/02/2025 09:16:35 +00:00", the heartbeat has been running for "00:00:01.2383806" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:16:47.851 +00:00] [WRN] As of "03/02/2025 09:16:47 +00:00", the heartbeat has been running for "00:00:01.0386192" which is longer than "00:00:01". This could be caused by thread pool starvation.
    [2025-03-02 09:17:11.011 +00:00] [INF] "Webhook Item Deleted Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:17:11.925 +00:00] [INF] "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
    [2025-03-02 09:17:24.365 +00:00] [INF] Sending ForceKeepAlive message to 1 inactive WebSockets.
    [2025-03-02 09:17:35.672 +00:00] [INF] Lost 1 WebSockets.
    [2025-03-02 09:17:47.320 +00:00] [INF] Sending ForceKeepAlive message to 2 inactive WebSockets.
    [2025-03-02 09:17:59.820 +00:00] [INF] Lost 2 WebSockets.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #13
    2025-03-02, 04:48 PM
    The current theory is some sort of database corruption causing Jellyfin's memory to balloon. But we haven't been able to reproduce the conditions ourselves so we don't know how to "fix" the issue....besides starting over. Not ideal, obviously.
    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]
    Pages (2): « Previous 1 2

    « 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