• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Media Scanning & Identification Real time monitoring not working

     
    • 0 Vote(s) - 0 Average

    Real time monitoring not working

    jackysee
    Offline

    Junior Member

    Posts: 1
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    #1
    2025-06-03, 12:21 PM
    I'm migrating my docker jellyfin to another NAS. While jellyfin can list and play my library OK, I find that it can't do real time monitoring now. If I do a manual scan, jellyfin can find the newly added files and add to collection. I check the docker log and find these errors:

    Code:
    [11:57:03] [ERR] [29] Emby.Server.Implementations.IO.LibraryMonitor: Permission error for Directory watcher: /data/TV
    System.UnauthorizedAccessException: Access to the path '/data/TV' is denied.
    ---> System.IO.IOException: Permission denied
      --- End of inner exception stack trace ---
    [11:57:03] [ERR] [27] Emby.Server.Implementations.IO.LibraryMonitor: Permission error for Directory watcher: /data/shows
    System.UnauthorizedAccessException: Access to the path '/data/shows' is denied.
    ---> System.IO.IOException: Permission denied
      --- End of inner exception stack trace ---
    [11:57:03] [ERR] [24] Emby.Server.Implementations.IO.LibraryMonitor: Permission error for Directory watcher: /data/movies
    System.UnauthorizedAccessException: Access to the path '/data/movies' is denied.
    ---> System.IO.IOException: Permission denied
      --- End of inner exception stack trace ---

    So it definitely is a permission error. I have checked all the mapped volumes do have the same user/group as the PUID/PGID I passed into the docker compose. (I'm using linuxserver image) The volumes are directly on the NAS, not network mount. 

    I also tested using PUID/PGID as 0:0 and the exception would go away. But I don't want to give the docker container this access to mess up the permission on disk when it writes nfo/jpg to the folders.

    Is there anything I missed?
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode