4.3.0.30 How to enable real-time monitor

[Luke 36998]

How do you know they use Inotify?

[Angus2064 1]

After hours of search on Google about inotify problems.  

[Luke 36998]

Has the advice here helped?

[Angus2064 1]

Sorry, but even after followed all advice found here, RealTime monitoring still don't work. After some search on others forum, Inotify on my Synology works correctly. 

When I will have some free time I will uninstall EMBY sever and made a fresh install, hopping to solve this problem. 

[Luke 36998]

Let us know how you get on. Thanks.

[sentience 0]

I just installed Emby 4.4.2.0 for the first time on my nearly-new Synology DS1019+, running DSM 6.2.2. Real-time monitoring is enabled for the one (TV Shows) library I have created, but does not seem to be working.

 

I have applied the recommended fix to set max_user_watches to a larger number (65536, in my case).

kyank@diskstation:/volume1/homes/kyank$ cat /proc/sys/fs/inotify/max_user_watches
65536

With debug logging enabled I am seeing LibraryMonitor start up, and it stops and starts again whenever the scheduled rescan of library folders occurs:

2020-04-10 22:06:59.286 Info App: Starting entry point Emby.Server.Implementations.IO.LibraryMonitorStartup
2020-04-10 22:06:59.600 Debug XmlSerializer: Deserializing file /var/packages/EmbyServer/target/var/root/default/TV shows/options.xml
2020-04-10 22:06:59.728 Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.442423 seconds
…
2020-04-10 22:06:59.762 Info LibraryMonitor: Watching directory /volume1/NAS/iTunes Library/TV Shows
…
2020-04-10 22:11:18.056 Debug TaskManager: IntervalTrigger fired for task: Scan media library
2020-04-10 22:11:18.056 Debug TaskManager: Queueing task RefreshMediaLibraryTask
2020-04-10 22:11:18.056 Debug TaskManager: Executing Scan media library
2020-04-10 22:11:18.061 Info LibraryMonitor: Stopping directory watching for path /volume1/NAS/iTunes Library/TV Shows
…
2020-04-10 22:12:49.665 Debug TaskManager: Scan media library Completed after 1 minute(s) and 31 seconds
2020-04-10 22:12:49.665 Info LibraryMonitor: Watching directory /volume1/NAS/iTunes Library/TV Shows

but adding/deleting/renaming files does not produce any log output from LibraryMonitor.

[Seger 110]

https://emby.media/community/index.php?/topic/79891-43030-how-to-enable-real-time-monitor/page-1&do=findComment&comment=861413 Edited April 11, 2020 by CBers
Amended link to post #17

[sentience 0]

@@Seger did you mean to post that?

[Seger 110]

Yes, go to Post 17

Edited April 11, 2020 by Seger

[sentience 0]

@@Seger all I see in your post is a link that, when I click it, I get an error that I don’t have permission to submit a reputation request…?

[Seger 110]

Post 17 on this topic, please implement once. Restarting the NAS is very important. Please do the same.

[sentience 0]

As I said, I already implemented the fix, and my inotify limit is increased. Like @@Angus2064 above, this has not fixed real-time monitor.

[Seger 110]

@@sentience you write the number 65536, I'll write another one! So I'm asking you if you followed my mail exactly?

[sentience 0]

@@sentience you write the number 65536, I'll write another one! So I'm asking you if you followed my mail exactly?

 

I don't know why one large number would be more effective than another, especially since I'm not getting any errors to do with the inotify watch limit in my logs.

 

Nevertheless, I have now tested with the number 204800 (and yes, I rebooted after updating the scheduled task). The behaviour is unchanged. Real-time monitoring is not working.

[Seger 110]

Can you please create a new folder on the Nas, include it as source and copy a new movie into it.

 

Why the number works better would take too long now.

 

So you placed the job in the task list, right?

 

I just can't figure out what your mistake is. It works for me and a lot of other people.

 

Let's see, we have to keep trying.

[sentience 0]

OK, real-time monitoring does seem to be work in the test folder I added. Adding a new file immediately generates this log output:

2020-04-15 12:31:46.603 Debug LibraryMonitor: New file refresher created for /volume1/NAS/Emby test/Back to the Future.m4v

Emby Server then waits for a minute (which is normal) before processing the new file:

2020-04-15 12:32:47.340 Debug App: Running FFProbeProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:47.340 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/NAS/Emby test/Back to the Future.m4v], Extension = [.m4v], Operating System = [Linux], Executables Available = [True].
2020-04-15 12:32:47.340 Debug App: [LinuxMount] Operating System is [Linux].
2020-04-15 12:32:47.340 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/NAS/Emby test/Back to the Future.m4v], Extension = [.m4v], Operating System = [Linux], Executables Available = [True].
2020-04-15 12:32:47.340 Debug App: [LinuxMount] Executables are available, extension check will return [False].
2020-04-15 12:32:47.340 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/NAS/Emby test/Back to the Future.m4v" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2020-04-15 12:32:47.353 Debug MediaProbeManager: ProcessRun 'ffprobe' Started.
2020-04-15 12:32:47.939 Info HttpServer: HTTP GET http://diskstation.local:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
2020-04-15 12:32:48.282 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0
2020-04-15 12:32:48.294 Debug App: Running MovieNfoProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Debug App: MovieNfoProvider returned no metadata for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Debug App: Running MovieDbProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Info App: MovieDbProvider: Finding id for item: Back to the Future
2020-04-15 12:32:48.294 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/search/movie?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Back+to+the+Future&language=en
2020-04-15 12:32:48.640 Debug App: Running MovieDbImageProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.646 Debug App: Running FanartMovieImageProvider for /volume1/NAS/Emby test/Back to the Future.m4v

Deleting the file likewise generates immediate log output indicating that Emby Server noted the change, followed by processing after a minute.

 

So the question now is, why is real-time monitoring not working on my main library?

 

I have tried disabling real-time monitoring on the library, restarting Emby Server, re-enabling real-time monitoring, and then restarting Emby Server again. This has made no difference.

[Luke 36998]

 

OK, real-time monitoring does seem to be work in the test folder I added. Adding a new file immediately generates this log output:

2020-04-15 12:31:46.603 Debug LibraryMonitor: New file refresher created for /volume1/NAS/Emby test/Back to the Future.m4v

Emby Server then waits for a minute (which is normal) before processing the new file:

2020-04-15 12:32:47.340 Debug App: Running FFProbeProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:47.340 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/NAS/Emby test/Back to the Future.m4v], Extension = [.m4v], Operating System = [Linux], Executables Available = [True].
2020-04-15 12:32:47.340 Debug App: [LinuxMount] Operating System is [Linux].
2020-04-15 12:32:47.340 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/NAS/Emby test/Back to the Future.m4v], Extension = [.m4v], Operating System = [Linux], Executables Available = [True].
2020-04-15 12:32:47.340 Debug App: [LinuxMount] Executables are available, extension check will return [False].
2020-04-15 12:32:47.340 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/NAS/Emby test/Back to the Future.m4v" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2020-04-15 12:32:47.353 Debug MediaProbeManager: ProcessRun 'ffprobe' Started.
2020-04-15 12:32:47.939 Info HttpServer: HTTP GET http://diskstation.local:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
2020-04-15 12:32:48.282 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code 0
2020-04-15 12:32:48.294 Debug App: Running MovieNfoProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Debug App: MovieNfoProvider returned no metadata for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Debug App: Running MovieDbProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.294 Info App: MovieDbProvider: Finding id for item: Back to the Future
2020-04-15 12:32:48.294 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/search/movie?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Back+to+the+Future&language=en
2020-04-15 12:32:48.640 Debug App: Running MovieDbImageProvider for /volume1/NAS/Emby test/Back to the Future.m4v
2020-04-15 12:32:48.646 Debug App: Running FanartMovieImageProvider for /volume1/NAS/Emby test/Back to the Future.m4v

Deleting the file likewise generates immediate log output indicating that Emby Server noted the change, followed by processing after a minute.

 

So the question now is, why is real-time monitoring not working on my main library?

 

I have tried disabling real-time monitoring on the library, restarting Emby Server, re-enabling real-time monitoring, and then restarting Emby Server again. This has made no difference.

 

 

We'd have to go over a specific example with your main library. thanks.

[Seger 110]

@@sentience

 

my guess is that for some reason the folder has inherited custom permissions, which is what happens when you inherit permissions or make them explicit in the synology language. That's why I guess I should create a different folder, because the newly created one automatically inherits clean rights.

 

A pragmatic solution:

 

Please shut down Emby, rename the original folder to "old", create a new empty folder and give this new folder the name of the old one. Then use the DSM interface to copy the content from one folder to the other (cut/paste), this should be fast no matter how much data you have, because it is a cut/paste on the same volume. It is important not to copy, otherwise it will take longer and your disk space could become a problem.

 

Then delete the old folder and start Emby. In the future everything should run clean with the settings I posted.

 

 

best regards,

seger

Edited April 15, 2020 by Seger

[sentience 0]

my guess is that for some reason the folder has inherited custom permissions, which is what happens when you inherit permissions or make them explicit in the synology language. That's why I guess I should create a different folder, because the newly created one automatically inherits clean rights.

 

A pragmatic solution:

 

Thanks for the suggestion, @@Seger! Unfortunately it hasn't made any difference.

 

 

We'd have to go over a specific example with your main library. thanks.

 

@@Luke, I'd be very happy to assist. I posted some logs above. What steps and what information would you like me to take to diagnose a specific example?

Edited April 27, 2020 by sentience

[Luke 36998]

Thanks for the suggestion, @@Seger! Unfortunately it hasn't made any difference.

 

 

 

@@Luke, I'd be very happy to assist. I posted some logs above. What steps and what information would you like me to take to diagnose a specific example?

 

We'd really have to go over an example along with the server log for that example. But again as mentioned above, if INotify doesn't pick up the change, then Emby Server will not be aware of it until you run a library scan.

[Angus2064 1]

On 3/31/2020 at 9:25 PM, Angus2064 said:

Sorry, but even after followed all advice found here, RealTime monitoring still don't work. After some search on others forum, Inotify on my Synology works correctly. 

When I will have some free time I will uninstall EMBY sever and made a fresh install, hopping to solve this problem. 

Hello ! 

I finally find some times to try somethings to fix this RT-Monitoring problem .

After a lot of try and search with Inotify problem and with no result, I decide to comeback to the initial Inotify settings and uninstall Emby server from my Synology and made a fresh install. 

After settings the library and wait for the initial scan, I tried multiple time (over few weeks) to add news movies to my library and the RT-Monitoring now work correctly like before

So the problem came effectively from my last update, I don't know exactly why but something was break into embyserv when this update finish his install ...

Thanks anyway for your advise