mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[10.11] Logs filled with extraneous complaints about permissions issues in unused path #7432
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 @Diatrus on GitHub (Oct 20, 2025).
Description of the bug
After upgrading to jellyfin 10.11 and checking logs to ensure the migration went as expected, found a continuous stream of errors populating regarding a systemd temporary directory location that I’ve not configured jellyfin to use.
I’ve ensured the service is setup to not use this systemd-logind feature:
systemctl show jellyfin | grep Private PrivateTmp=no PrivateDevices=no PrivateNetwork=no PrivateUsers=no PrivateMounts=no PrivateIPC=noand my local configuration is set to use the regular system/tmpwhich is populated and functions fine.I’ll also paste the log output here showing the directories used in the configuration, which are being used correctly as far as I can see
[2025-10-20 00:07:08.669 -04:00] [INF] Program data path: "/var/lib/jellyfin" [2025-10-20 00:07:08.669 -04:00] [INF] Log directory path: "/var/log/jellyfin" [2025-10-20 00:07:08.669 -04:00] [INF] Config directory path: "/etc/jellyfin" [2025-10-20 00:07:08.669 -04:00] [INF] Cache path: "/var/cache/jellyfin" [2025-10-20 00:07:08.669 -04:00] [INF] Temp directory path: "/tmp/jellyfin" [2025-10-20 00:07:08.669 -04:00] [INF] Web resources path: "/usr/share/jellyfin/web" [2025-10-20 00:07:08.669 -04:00] [INF] Application directory: "/usr/lib/jellyfin/bin/" [2025-10-20 00:07:08.675 -04:00] [INF] Storage path `"/var/lib/jellyfin/data"` (Fixed) successfully checked with "1.5TB" free which is over the minimum of "2GB". [2025-10-20 00:07:08.676 -04:00] [INF] Storage path `"/var/log/jellyfin"` (Fixed) successfully checked with "1.5TB" free which is over the minimum of "512MB". [2025-10-20 00:07:08.676 -04:00] [INF] Storage path `"/var/cache/jellyfin"` (Fixed) successfully checked with "1.5TB" free which is over the minimum of "2GB". [2025-10-20 00:07:08.676 -04:00] [INF] Storage path `"/var/lib/jellyfin"` (Fixed) successfully checked with "1.5TB" free which is over the minimum of "2GB". [2025-10-20 00:07:08.676 -04:00] [INF] Storage path `"/tmp/jellyfin"` (Ram) successfully checked with "100GB" free which is over the minimum of "2GB". [2025-10-20 00:07:08.677 -04:00] [INF] Setting cache path: "/var/cache/jellyfin" [2025-10-20 00:07:08.719 -04:00] [INF] SQLite connection string: "Data Source=/var/lib/jellyfin/data/jellyfin.db;Cache=Default;Pooling=True"When looking at logs from the 19th (yesterday, version 10.10.7) this message did not appear, and has only started to show after this upgrade.
Reproduction steps
What is the current bug behavior?
These messages continuously populate, making it nearly impossible to get any useful info out of the logs. It does not stop at any point in the server’s operation.
What is the expected correct behavior?
No logs regarding that path.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
10.11.0
Specify the build version
N/A (build version blank)
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
Additional information
The “paths” section of the dashboard also does not populate now, and just continuously shows as loading. This may or may not be related, but I thought it would be worth mentioning. See the screenshot.
@Diatrus commented on GitHub (Oct 20, 2025):
Issue resolved on my end:
In case anyone else encounters this issue in the future and needs it fixed, the resolution was to swap my transcoding directory from
/tmpto/tmp/jellyfin-transcodes.The behavior that previously worked, just transcoding straight to /tmp, broke in 10.11. Specifying the subdirectory resolved it.
@joshuaboniface commented on GitHub (Oct 20, 2025):
The reason is the dashboard space reporting which is now part of 10.11. It needs to scan the contents of the folders that Jellyfin is using for configuration and data storage, including transcoding temporary storage.
/tmpwill contain various files created by other processes that Jellyfin won't be able to read, and hence throw this error.We generally recommend setting a specific path like that, rather than using a system folder, especially since that can have other adverse affects (in this case, the transcoding temp cleanup job would likely be trying to delete files from
/tmp, and failing, previously - might not matter but also might).