ddurdle 75 Posted November 10, 2018 Posted November 10, 2018 Just wondering what triggers this? I noticed Emby 3.5.3 this morning updating all the season.nfo files for my media (not as part of a library scan either). It started about an hour after a scheduled library scan. 2018-11-10 12:19:21.200 Debug LibraryMonitor: New file refresher created for /u01/STRM/tv/top gear/season 17/season.nfo The file contents is the same as before it updates it and I don't see any changed data. Plus there was no updates to the seasons or shows being updated.
Luke 42097 Posted November 10, 2018 Posted November 10, 2018 due to a file system change and you enabled the realtime monitor.
ddurdle 75 Posted November 24, 2018 Author Posted November 24, 2018 It is odd, I'm setting this again today. It happens shortly after a scheduled full scan has complete. I checked the files stats and none of the files or directories were updated. When something changes in the directory, the directory timestamp is updated. In this case it is scanning the entire library. What I also noticed is inbetween scanning, I see the KODI companion performing scan refreshes
Luke 42097 Posted November 24, 2018 Posted November 24, 2018 The server is reacting to file changes on your system. That's really all i can tell you and this doesn't even indicate any kind of problem.
ddurdle 75 Posted November 24, 2018 Author Posted November 24, 2018 (edited) The server is reacting to file changes on your system. That's really all i can tell you and this doesn't even indicate any kind of problem. Could it include changes to files in the emby-cache directory that can trigger scans like this, not just files in the library directory? I have a separate emby-cache folder. My only concern is that it causes high cpu and because it isn't tied to a scheduled job that I could stop, I'm sort of at the mercy of letting it run its course. Edited November 24, 2018 by ddurdle
Luke 42097 Posted November 24, 2018 Posted November 24, 2018 No, the realtime monitor does not watch that. let's just remove this from the server log.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now