mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Jellyfin docker shutting down everyday around same time #6066
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @poizarts on GitHub (Jun 27, 2024).
Please describe your bug
For the past 2 days my jellyfin docker has shut down around the same time. Trickplay generation is the only task running as it takes days to generate all the files. Nothing as far as im aware has changed with the docker itself. My dockers get backed up at 3am every morning with the exception of jellyfin as i didnt want it being shut down when someone is watching something so it does not get backed up. No other apps seem to be shutting down at the same time only jelyfin. Have attached logs for jellyfin aswell as the unraid logs at time of shutdown
UnraidLogsJellyfinShutdown.txt
JellyfinLogAtShutdown.txt
Reproduction Steps
Jellyfin Version
10.9.0
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@jellyfin-bot commented on GitHub (Jun 27, 2024):
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
@BrianCArnold commented on GitHub (Jul 3, 2024):
Your given Linux kernel version is incorrect, by the way, the current mainline version in development is is 6.10.rc6, there is no 6.12.x. I would recommend checking that again.
@BrianCArnold commented on GitHub (Jul 3, 2024):
Stream of consciousness here for a moment...
So, looking at your logs here, and it looks like your websockets are getting closed between the client and the server, but it may simply be that Kestrel is shutting down or crashing for unrelated reasons, which is what's actually causing the websocket to be interrupted by the docker container being disconnected from the docker network layer, so I'm guessing it's a red herring.
Your Unraid logs also start at the time that the crash has already happened, are there any logs in the seconds leading up to the crash?
@poizarts commented on GitHub (Jul 3, 2024):
No sorry that's all that was relevant in the unraid logs, the stuff before that was hours before hand for a different application so didn't upload that section. Sorry must've got confused with unraid version and Linux version. I have no clue where to look for the Linux kernal version on unraid
@BrianCArnold commented on GitHub (Jul 3, 2024):
I'm looking through the issues list, I think this is the same as 12090
Duplicate of #12090
@BrianCArnold commented on GitHub (Jul 3, 2024):
(or at least the crash message is the same)
@maru801 commented on GitHub (Jul 3, 2024):
Jellyfin does keep its logs. You're just relying on Unraid to show you the system logs, while Jellyfin is actively saving them.
By default, logs should be stored in the Jellyfin config folder ("config > log").
You can also open logs directly by going to your dashboard and into the logs section. There, you just click on a log entry and a browser will open the logs in a new window.
All you need is to open any of the logs from just before any unintended shutdown.
Jellyfin does have a configurable cleanup task that deletes logs older than 3 days by default, so keep that in mind.
@jellyfin-bot commented on GitHub (Nov 1, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Nov 23, 2024):
This issue was closed due to inactivity.