Real-time monitoring cannot be triggered

[ZhaoZhuang 1]

Big brother, can you answer my question, the device is Fusion n1 brush armbian, emby is docker installation, clouddrive2 is apt installation, clouddrive2 binding 115 network disk and then mounted to the local, the first time scanning everything is normal, the local posters wall what can be read and recognized to the wall, the media library set up real-time monitoring and download!nfo to the media in the same directory is also open, but after 115 dump rename movie name year, transferred to the media library folder, real-time monitoring is not triggered, after manually refreshing the media library can be scraped to the information, but did not download the nfo, there is no what troubleshooting and solution, online search, there is a saying that can not monitor the network shared folder, is that so?

[darkassassin07 652]

38 minutes ago, ZhaoZhuang said:

network disk

Many remotely mounted filesystems don't support inotify, and can't use real-time monitoring.

 

You'll just have to set a schedule and/or have other software trigger library scans via api calls. (radarr/sonarr for example)

[ZhaoZhuang 1]

20 minutes ago, darkassassin07 said:

Many remotely mounted filesystems don't support inotify, and can't use real-time monitoring.

 

You'll just have to set a schedule and/or have other software trigger library scans via api calls. (radarr/sonarr for example)

May I ask if you have heard of auto_Symlink and nginx? If I use auto_Symlink to map media files in the cloud storage to strm, can I bypass this restriction? Also, if I use this method to play videos on my local area network using Emby, do I need to use nginx to restore the original link

 

[darkassassin07 652]

I'm not familiar with auto_Symlink, no; but if you can set up a system to create working .strm files on the local filesystem, emby should be able to see those in real time.