starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Jellyfin LXC gets clogged by chatty logs #371

New Issue
Closed
opened 2026-02-04 18:16:07 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 18:16:07 +03:00
Owner
Copy Link

Originally created by @ProgUnlimited on GitHub (Jan 23, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Jellyfin Media Server LXC

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyfin.sh)"

📝 Provide a clear and concise description of the issue.

The standard disk space allotted to the LXC is 8GB. Since Jellyfin is extremely verbose in the logs, the space is quickly filled (up to 4GB) by log entries even in standard operation. The issue has been reported on the Jellyfin side, and the workaround/fix is to increase the minimum message priority in the jellyfin config from "Informational" (standard) to a higher level ("Warning" or even "Error".

This leads to the alotted space filling up quickly and a crash of the server (which apart from that is working perfectly until the issue arises).

I recommend to have the script changed in such a way that this change to /etc/jellyfin/logging.json is applied in the standard install or the journal size is limited for the container in the system journal settings

See https://github.com/jellyfin/jellyfin/issues/578

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Standard install, scan a sizeable amount of items in teh databse, use the server.
Observe the log filling up quickly (multiple GBs)
Once the log reaches the limits of disk space, server crashes

❌ Paste the full error output (if available).

not available

🖼️ Additional context (optional).

https://github.com/jellyfin/jellyfin/issues/578
https://zedt.eu/tech/linux/how-to-stop-jellyfin-from-logging-to-system-log/

Originally created by @ProgUnlimited on GitHub (Jan 23, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Jellyfin Media Server LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/jellyfin.sh)" ### 📝 Provide a clear and concise description of the issue. The standard disk space allotted to the LXC is 8GB. Since Jellyfin is extremely verbose in the logs, the space is quickly filled (up to 4GB) by log entries even in standard operation. The issue has been reported on the Jellyfin side, and the workaround/fix is to increase the minimum message priority in the jellyfin config from "Informational" (standard) to a higher level ("Warning" or even "Error". This leads to the alotted space filling up quickly and a crash of the server (which apart from that is working perfectly until the issue arises). I recommend to have the script changed in such a way that this change to /etc/jellyfin/logging.json is applied in the standard install or the journal size is limited for the container in the system journal settings See [https://github.com/jellyfin/jellyfin/issues/578](https://github.com/jellyfin/jellyfin/issues/578) ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Standard install, scan a sizeable amount of items in teh databse, use the server. Observe the log filling up quickly (multiple GBs) Once the log reaches the limits of disk space, server crashes ### ❌ Paste the full error output (if available). not available ### 🖼️ Additional context (optional). https://github.com/jellyfin/jellyfin/issues/578 https://zedt.eu/tech/linux/how-to-stop-jellyfin-from-logging-to-system-log/
OVERLORD commented 2026-02-04 18:16:10 +03:00
Author
Owner
Copy Link

@pearfire575 commented on GitHub (Jan 24, 2025):

I can confirm, my server crashed by filling up with logs the 8GB default disk space. Unfortunately it crashes the SQL DB badly and won't start again. Had to wipe the LXC and start from scratch.

The problem happened after a week of install and no more than 3 movies viewed.

@pearfire575 commented on GitHub (Jan 24, 2025): I can confirm, my server crashed by filling up with logs the 8GB default disk space. Unfortunately it crashes the SQL DB badly and won't start again. Had to wipe the LXC and start from scratch. The problem happened after a week of install and no more than 3 movies viewed.
OVERLORD commented 2026-02-04 18:16:30 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 24, 2025):

and where need to optimize this?

@MickLesk commented on GitHub (Jan 24, 2025): and where need to optimize this?
OVERLORD commented 2026-02-04 18:16:37 +03:00
Author
Owner
Copy Link

@ProgUnlimited commented on GitHub (Jan 24, 2025):

Well, the solution on the Jellyfin side is to adapt the error level. If this could be implemented in the setup script e.g. along the lines of

sed -i 's/"MinimumLevel": "Informational"/"MinimumLevel": "Error"/g' /etc/jellyfin//loggin.json

this would make the server run sustainably within the 8GB standard disk space alotted (which otherwise is perfectly fine). Otherwise, the server crashes essentially inevitably rather sooner than later due to the extremely chatty logging in the standard setup, even during perfectly normal usage

@ProgUnlimited commented on GitHub (Jan 24, 2025): Well, the solution on the Jellyfin side is to adapt the error level. If this could be implemented in the setup script e.g. along the lines of sed -i 's/"MinimumLevel": "Informational"/"MinimumLevel": "Error"/g' /etc/jellyfin//loggin.json this would make the server run sustainably within the 8GB standard disk space alotted (which otherwise is perfectly fine). Otherwise, the server crashes essentially inevitably rather sooner than later due to the extremely chatty logging in the standard setup, even during perfectly normal usage
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#371
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?