"Log file cleanup" task does not work #1080

Closed
opened 2026-02-06 20:28:53 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @therealmelee on GitHub (Nov 25, 2019).

Describe the bug
Across multiple installations through the official Docker, the "Log file cleanup" task has never actually deleted old logs (described by the task as being "Deletes log files that are more than 3 days old."

To Reproduce

  1. Look at your log folder or click "Logs" in the admin dashboard sidebar.
  2. See that there are logs (log_20191125.log) aged far greater than 3 days.
    OR
  3. Go to admin dashboard, "Scheduled Tasks"
  4. Manually run "Log file cleanup"
  5. See that the logs are exactly the same as they were before.

Expected behavior
Logs should be deleted as intended.

System (please complete the following information):

  • OS: x64 official Docker
  • Browser: Chrome
  • Jellyfin Version: 10.4.2

Additional context
Logs folder is default:

Logs:
/config/log

Logs are being written, so the Docker must write access to that folder.

Originally created by @therealmelee on GitHub (Nov 25, 2019). **Describe the bug** Across multiple installations through the official Docker, the "Log file cleanup" task has never actually deleted old logs (described by the task as being "Deletes log files that are more than 3 days old." **To Reproduce** 1. Look at your log folder or click "Logs" in the admin dashboard sidebar. 2. See that there are logs (log_20191125.log) aged far greater than 3 days. OR 3. Go to admin dashboard, "Scheduled Tasks" 4. Manually run "Log file cleanup" 5. See that the logs are exactly the same as they were before. **Expected behavior** Logs should be deleted as intended. **System (please complete the following information):** - OS: x64 official Docker - Browser: Chrome - Jellyfin Version: 10.4.2 **Additional context** Logs folder is default: Logs: /config/log Logs are being written, so the Docker must write access to that folder.
OVERLORD added the bug label 2026-02-06 20:28:53 +03:00
Author
Owner

@excelite commented on GitHub (Nov 28, 2019):

@therealmelee, the old emby log cleanup task explicitly excludes the .log logfiles and states that those are to be managed by semilog.

you can fix this by adding the following line to your /config/logging.json

"retainedFileCountLimit": 3,

below the "rollingInterval" entry:

...
                                "rollingInterval": "Day",
                                "retainedFileCountLimit": 3,
...

after this change, you might need to restart your jellyfin app

@excelite commented on GitHub (Nov 28, 2019): @therealmelee, the old emby log cleanup task explicitly excludes the .log logfiles and states that those are to be managed by semilog. you can fix this by adding the following line to your /config/logging.json `"retainedFileCountLimit": 3,` below the "rollingInterval" entry: ``` ... "rollingInterval": "Day", "retainedFileCountLimit": 3, ... ``` after this change, you might need to restart your jellyfin app
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#1080