Jellyfin Forum
Error in Directory watcher - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Error in Directory watcher (/t-error-in-directory-watcher)



Error in Directory watcher - jamestk - 2024-11-11

Hello All

I am hoping that one of you can assist with a minor issue i have with an error appearing in the JellyFin logs:

[2024-11-11 18:06:15.927 +00:00] [INF] [8] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "W:\"
[2024-11-11 18:06:15.927 +00:00] [INF] [12] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "T:\"
[2024-11-11 18:06:15.927 +00:00] [ERR] [9] Emby.Server.Implementations.IO.LibraryMonitor: Error in Directory watcher for: "W:\" System.ComponentModel.Win32Exception (5): Access is denied.
[2024-11-11 18:06:15.928 +00:00] [ERR] [14] Emby.Server.Implementations.IO.LibraryMonitor: Error in Directory watcher for: "T:\" System.ComponentModel.Win32Exception (5): Access is denied.
[2024-11-11 18:06:15.928 +00:00] [INF] [6] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "X:\"
[2024-11-11 18:06:15.928 +00:00] [INF] [15] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "Y:\"
[2024-11-11 18:06:15.928 +00:00] [INF] [1] Emby.Server.Implementations.ApplicationHost: Running startup tasks
[2024-11-11 18:06:15.929 +00:00] [ERR] [16] Emby.Server.Implementations.IO.LibraryMonitor: Error in Directory watcher for: "X:\" System.ComponentModel.Win32Exception (5): Access is denied.
[2024-11-11 18:06:15.929 +00:00] [ERR] [17] Emby.Server.Implementations.IO.LibraryMonitor: Error in Directory watcher for: "Y:\" System.ComponentModel.Win32Exception (5): Access is denied.
[2024-11-11 18:06:15.929 +00:00] [INF] [18] Emby.Server.Implementations.IO.LibraryMonitor: Watching directory "Z:\"
[2024-11-11 18:06:15.937 +00:00] [INF] [9] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "W:\"
[2024-11-11 18:06:15.941 +00:00] [INF] [14] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "T:\"
[2024-11-11 18:06:15.950 +00:00] [INF] [16] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "X:\"
[2024-11-11 18:06:15.952 +00:00] [INF] [17] Emby.Server.Implementations.IO.LibraryMonitor: Stopping directory watching for path "Y:\"

Operating system: "Microsoft Windows 10.0.19045" (windows 10)
Architecture: X64
Jellyfin version: "10.10.0"
Windows user logged in is member of local admin
JellyFin is running as an app not as a service
Media is on a NAS connected to the same local network as the JellyFin PC
Nas connected to windows via a mappedĀ drive
The account used to map the drives is a local admin on the NAS

Looking at the error as it appears in the logs, it would suggest that there is an access issue but if i access the JellyFin portal from any other PC on my netwok and click the "refresh metadata" in one of the librarys, it will pick up the new media and everything works fine.

Would greatly appreciate any suggestions.

Kind Regards

James


RE: Error in Directory watcher - TheDreadPirate - 2024-11-11

Is the user running Jellyfin different than the use that mapped the drive?


RE: Error in Directory watcher - jamestk - 2024-11-11

Hello

Yes, the mapped drive is mapped with a different username but that user has full read/write access to the shares.

Regards
James


RE: Error in Directory watcher - TheDreadPirate - 2024-11-11

But jellyfin is not running as the user that mapped the drive. Access is being denied locally instead of remotely. I am pretty sure that the user that Jellyfin is running as needs to map the drive.


RE: Error in Directory watcher - jamestk - 2024-11-11

Hi

Okay, I'll try changing the user and drive mapping so that they are all the same user, thank you for your assitance.

Regards

James


RE: Error in Directory watcher - jamestk - 2024-11-11

Thank you TheDreadPirate, that does appear to have resolved the issue.