2023-07-03, 07:48 PM
@gamatos
Jellyfins discovery process is a bit complicated and prone to a bit ... moody.
I see a lot of loglines like this:
A refresh is requested by the FileSystemWatcher and then the file cannot be found anymore. Why that is the reason the log does not say. But an educated guess would be twofold:
- Issues with the underlying storage system. If that is a mounted device, it might be faulty
- Jellyfin is known to be a bit unreliable with non englisch character sets in several instances. This could also be an issue with your OS or dotnet.
Renaming thoese files in accordance with the documentation will bring some clarity.
Jellyfins discovery process is a bit complicated and prone to a bit ... moody.
I see a lot of loglines like this:
[2023-07-03 09:05:10.645 +00:00] [INF] [78] Emby.Server.Implementations.IO.LibraryMonitor: "Η παριζιάνα (1969)" ("/media/movies/Η παριζιάνα (1969)") will be refreshed.
[2023-07-03 09:05:11.178 +00:00] [INF] [78] Emby.Server.Implementations.Library.LibraryManager: Removing item, Type: "Movie", Name: "1814_-_Η_ΠΑΡΑΣΤΡΑΤΗΜΕΝΗ", Path: "/media/movies/Η παριζιάνα (1969)/1814_-_Η_ΠΑΡΑΣΤΡΑΤΗΜΕΝΗ_-_1966_-_TVRip_-_720x536.mp4", Id: 619b991e-71e7-1df7-0af0-9e70dfd3a4af
A refresh is requested by the FileSystemWatcher and then the file cannot be found anymore. Why that is the reason the log does not say. But an educated guess would be twofold:
- Issues with the underlying storage system. If that is a mounted device, it might be faulty
- Jellyfin is known to be a bit unreliable with non englisch character sets in several instances. This could also be an issue with your OS or dotnet.
Renaming thoese files in accordance with the documentation will bring some clarity.
typos are finders, keepers.
Next Jellyfin release 10.11.0 will be Soon™
Soon™ is an unregistered trademark of Jellyfin International
Next Jellyfin release 10.11.0 will be Soon™
Soon™ is an unregistered trademark of Jellyfin International