starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[10.11.x] Jellyfin requires 512MB of free space in logdir #7638

New Issue
Closed
opened 2026-02-07 05:16:44 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-07 05:16:44 +03:00
Owner
Copy Link

Originally created by @nonplusnl on GitHub (Oct 29, 2025).

Description of the bug

After upgrading from 10.10 to 10.11.1, Jellyfin startup fails with following text:

Image

I run my logdir on a RAMdrive, which does not have this space. It appears to me that a requirement for 512MB of logging space is a bit overdone?

Reproduction steps

Startup Jellyfin, provide option for logging dir that has less than 512MB available

What is the current bug behavior?

Unhandled exception

What is the expected correct behavior?

Jellyfin accepting lower space on logdir; perhaps instead providing alert in GUI

Jellyfin Server version

10.11.1

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.11.1

Specify the build version

current

Environment

- OS: Ubuntu 24.04
- Virtualization: No, bare-bones

Jellyfin logs

-

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @nonplusnl on GitHub (Oct 29, 2025). ### Description of the bug After upgrading from 10.10 to 10.11.1, Jellyfin startup fails with following text: <img width="1263" height="252" alt="Image" src="https://github.com/user-attachments/assets/adbee3a2-58da-4bf8-b154-b64165cc5aac" /> I run my logdir on a RAMdrive, which does not have this space. It appears to me that a requirement for 512MB of logging space is a bit overdone? ### Reproduction steps Startup Jellyfin, provide option for logging dir that has less than 512MB available ### What is the current _bug_ behavior? Unhandled exception ### What is the expected _correct_ behavior? Jellyfin accepting lower space on logdir; perhaps instead providing alert in GUI ### Jellyfin Server version 10.11.1 ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.11.1 ### Specify the build version current ### Environment ```markdown - OS: Ubuntu 24.04 - Virtualization: No, bare-bones ``` ### Jellyfin logs ```shell - ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bug label 2026-02-07 05:16:44 +03:00
OVERLORD commented 2026-02-07 05:16:46 +03:00
Author
Owner
Copy Link

@oddstr13 commented on GitHub (Oct 30, 2025):

👀

$ du -h /var/log/jellyfin/
3.0G	/var/log/jellyfin/

Just don't enable debug logging.

Closely related to #15036

@oddstr13 commented on GitHub (Oct 30, 2025): 👀 ``` $ du -h /var/log/jellyfin/ 3.0G /var/log/jellyfin/ ``` Just don't enable debug logging. --- Closely related to #15036
OVERLORD commented 2026-02-07 05:16:48 +03:00
Author
Owner
Copy Link

@nonplusnl commented on GitHub (Oct 30, 2025):

Just don't enable debug logging.

Thanks for the suggestion, but debug logging is disabled, my logging is set to fatal.

And again, I run logging on a RAMdrive. 512MB free space requirement for logging, with debug disabled, seems a bit high?

@nonplusnl commented on GitHub (Oct 30, 2025): > Just don't enable debug logging. Thanks for the suggestion, but debug logging is disabled, my logging is set to fatal. And again, I run logging on a RAMdrive. 512MB free space requirement for logging, with debug disabled, seems a bit high?
OVERLORD commented 2026-02-07 05:16:50 +03:00
Author
Owner
Copy Link

@Turbine1991 commented on GitHub (Oct 30, 2025):

👀

$ du -h /var/log/jellyfin/
3.0G	/var/log/jellyfin/

Just don't enable debug logging.

Closely related to #15036

I think this is a really bad default, it should be a warning - not fatal.

After installing as well on Armbian, I experienced this. As logs are on a ramdisk.

@Turbine1991 commented on GitHub (Oct 30, 2025): > 👀 > > ``` > $ du -h /var/log/jellyfin/ > 3.0G /var/log/jellyfin/ > ``` > > Just don't enable debug logging. > > Closely related to [#15036](https://github.com/jellyfin/jellyfin/issues/15036) I think this is a really bad default, it should be a warning - not fatal. After installing as well on Armbian, I experienced this. As logs are on a ramdisk.
OVERLORD commented 2026-02-07 05:16:51 +03:00
Author
Owner
Copy Link

@poddmo commented on GitHub (Nov 4, 2025):

An arbitrary hard limit does not seem in the open spirit. Especially when the config of /etc/jellyfin/logging.json should limit logs to ten 10MB files (100MB total).

                                "path": "%JELLYFIN_LOG_DIR%//jellyfin.log",
                                "fileSizeLimitBytes": 10485700,
                                "rollOnFileSizeLimit": true,
                                "retainedFileCountLimit": 10,

Why have a hard requirement beyond what we have configured the limit to be?
(retainedFileCountLimit * fileSizeLimitBytes) should be the amount of storage required.

@poddmo commented on GitHub (Nov 4, 2025): An arbitrary hard limit does not seem in the open spirit. Especially when the config of /etc/jellyfin/logging.json should limit logs to ten 10MB files (100MB total). ``` "path": "%JELLYFIN_LOG_DIR%//jellyfin.log", "fileSizeLimitBytes": 10485700, "rollOnFileSizeLimit": true, "retainedFileCountLimit": 10, ``` Why have a hard requirement beyond what we have configured the limit to be? **(retainedFileCountLimit * fileSizeLimitBytes) should be the amount of storage required.**
OVERLORD commented 2026-02-07 05:16:52 +03:00
Author
Owner
Copy Link

@dpieski commented on GitHub (Nov 18, 2025):

Is this fixed with #15390 in 10.11.3?

@dpieski commented on GitHub (Nov 18, 2025): Is this fixed with #15390 in 10.11.3?
OVERLORD commented 2026-02-07 05:16:53 +03:00
Author
Owner
Copy Link

@nmaas87 commented on GitHub (Nov 18, 2025):

@dpieski Yes, can confirm, the /var/log issue is not a problem anymore / does work on Armbian with 50 MB ZRAM / tmpfs on /var/log.

@nmaas87 commented on GitHub (Nov 18, 2025): @dpieski Yes, can confirm, the /var/log issue is not a problem anymore / does work on Armbian with 50 MB ZRAM / tmpfs on /var/log.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug
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/jellyfin#7638
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?