-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] causing ubuntu to stop responding. #278
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
If you have jellyfin running and don't watch media, does the same thing happen? |
yes, the only issue I can see on the Syslog file is the below memory issue, this has only started after installing the Jellyfin container. 2025-01-19T02:33:54.437916+00:00 matt-S3420GP kernel: systemd-journald[392]: Under memory pressure, flushing caches. |
I would run a memtest on your host. |
I have run memtest+ and have no reported issues. Just so you know, this memory crash error only started after started Jellyfin if I keep the container stopped the PC will not crash. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
docker is running on linux x86_64 Ubuntu 24.04.1 LTS 6.8.0-51-generic with an Nvidia Quadro P2000 GPU, after installing Jellyfin and setting up the user profile and media folder location, I then installed the JellyFin client on my LG TV and after playing a movie for a short time by Linux PC would stop responding.
I cannot get any log files as I believe Jellyfin is causing a memory issue, and Ubuntu has stopped responding.
Expected Behavior
not to cause ubuntu to crash
Steps To Reproduce
after about 10 minutes it will cause Ubuntu to stop responding.
This will happen when the docker container is left running.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: