[Issue]: One library keeps refreshing, despite nothing happening to the files. #3391

Closed
opened 2026-02-06 23:13:12 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @Akirainblack on GitHub (Nov 22, 2021).

Please describe your bug

My film library keeps refreshing.

[14:07:18] [INF] [5] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.,
[14:07:22] [INF] [26] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.,
[14:07:24] [INF] [45] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.
Can be seen repeatedly in the logs despite no obvious changes to files.
Is there any way to see what's triggering it? My logs are already set to debug but I don't see

Jellyfin Version

10.7.7

if other:

No response

Environment

- OS:Synology NAS
- Virtualization: docker
- Clients:N/A
- Browser:N/A
- FFmpeg Version:N/A
- Playback Method:N/A
- Hardware Acceleration:N/A
- Plugins:TMDBboxsets
- Reverse Proxy:N/A
- Base URL:N/A
- Networking:N/A
- Storage:RAID5

Jellyfin logs

[14:07:18] [INF] [5] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.,
[14:07:22] [INF] [26] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.,
[14:07:24] [INF] [45] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed.

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @Akirainblack on GitHub (Nov 22, 2021). ### Please describe your bug My film library keeps refreshing. [14:07:18] [INF] [5] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed., [14:07:22] [INF] [26] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed., [14:07:24] [INF] [45] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed. Can be seen repeatedly in the logs despite no obvious changes to files. Is there any way to see what's triggering it? My logs are already set to debug but I don't see ### Jellyfin Version 10.7.7 ### if other: _No response_ ### Environment ```markdown - OS:Synology NAS - Virtualization: docker - Clients:N/A - Browser:N/A - FFmpeg Version:N/A - Playback Method:N/A - Hardware Acceleration:N/A - Plugins:TMDBboxsets - Reverse Proxy:N/A - Base URL:N/A - Networking:N/A - Storage:RAID5 ``` ### Jellyfin logs ```shell [14:07:18] [INF] [5] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed., [14:07:22] [INF] [26] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed., [14:07:24] [INF] [45] Emby.Server.Implementations.IO.LibraryMonitor: Films (/Films) will be refreshed. ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bugstale labels 2026-02-06 23:13:12 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Mar 23, 2022):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Mar 23, 2022): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#3391