Jump to content

Emby Version 4 real-time monitoring is not working - Synology 2413/15+ and all other


Seger
 Share

Go to solution Solved by Seger,

Recommended Posts

solabc16

Thanks @@Hjlfmir, that is somewhat telling... can you try the following  then run the Send Logs utility again, that way I'll be able to get the complete output.

sudo sh -c '/var/packages/EmbyServer/scripts/utilities/sbin/lsof | grep -i "inotify" > /var/packages/EmbyServer/target/var/logs/inotify.txt'
Best

- James

Edited by solabc16
Link to comment
Share on other sites

Hjlfmir

Please find here the new log : sendlogs_NAS_synology_cedarview_2413+_20190322T125748UTC.tgz   

Link to comment
Share on other sites

Hjlfmir

No problem ! Thank you for your help :)

 

sendlogs_NAS_synology_cedarview_2413+_20190322T131622UTC.tgz 

Link to comment
Share on other sites

solabc16

Thanks @@Hjlfmir, that's better - file attached for reference, that gives us a good starting point.

 

The problem is pretty clear.

 

There's a few things we need to do to move this forward. To start with, as I mentioned earlier, it doesn't make sense to do to much work on the current package as we're about to change the runtime.

 

Now, you could either wait until the next stable or...

 

    a ) I'll build you a custom package using the new runtime for the current stable or

    b ) You can temporarily switch to the beta channel.

 

Let me know your thoughts / preference.

 

Also, can you let me know Emby Server's current memory utilisation, which you should be able to find using Resource Monitor.

 

Best

- James

inotify.txt

Edited by solabc16
Link to comment
Share on other sites

Hjlfmir

Thank you very much for your help :)

 

I can wait for the next release, it's not a huge problem ;)

 

There the memory usage :

 

5c94ec9a1f6a2_Embymemory.png

Link to comment
Share on other sites

solabc16

No problem @@Hjlfmir and thanks the above, the memory looks sane.

 

I'll touch base again once the next stable is released and we'll pickup the thread.

 

Best

- James

Link to comment
Share on other sites

Hjlfmir

For ISO Gad Elmaleh - Sans Tambour (2014).iso :

 

Root : 

 

5c953622301a1_Root.png

 

Inside 0012FA :

 

5c95363dd4e15_Root.png

 

Inside VIDEO_TS :

 

5c95365e4b47e_Root.png

 

AUDIO_TS : empty

Link to comment
Share on other sites

solabc16

Hello @@Hjlfmir

 

Thanks for the above, the contents in the example above look sensible - so that shouldn't be the reason for the failure.

 

I've just tried to recreate this on a test system, and I can.

2019-03-26 14:44:06.500 Debug App: Running FFProbeProvider for /volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso
2019-03-26 14:44:06.500 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso], Extension = [.iso], Operating System = [Linux], Executables Available = [True].
2019-03-26 14:44:06.500 Debug App: [LinuxMount] Operating System is [Linux].
2019-03-26 14:44:06.500 Debug App: [LinuxMount] Executables are available, extension check will return [True].
2019-03-26 14:44:06.500 Info App: [LinuxMount] Attempting to mount [/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso].
2019-03-26 14:44:06.500 Debug App: [LinuxMount] ISO will be mounted at [/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2].
2019-03-26 14:44:06.500 Debug App: [LinuxMount] Our current UID is [1038], GetUserId() returned [1038].
2019-03-26 14:44:06.500 Debug App: [LinuxMount] Mount command [/var/packages/EmbyServer/scripts/utilities/sbin/sudo], mount arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/mount" "/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"].
2019-03-26 14:44:06.506 Debug App: [LinuxMount] Waiting for process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/mount" "/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] to exit.
2019-03-26 14:44:06.607 Debug App: [LinuxMount] Process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/mount" "/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] has exited, exit code is [0].
2019-03-26 14:44:07.007 Debug App: [LinuxMount] Removed entry for process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/mount" "/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] from the dictionary, the dictionary currently contains [0] key/value pairs.
2019-03-26 14:44:07.007 Debug App: [LinuxMount] Standard output from process is [].
2019-03-26 14:44:07.007 Debug App: [LinuxMount] Standard error from process is [].
2019-03-26 14:44:07.007 Info App: [LinuxMount] ISO mount completed successfully.
2019-03-26 14:44:07.007 Debug MediaEncoder: Ffprobe -i file:"/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-03-26 14:44:07.007 Info MediaEncoder: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data
2019-03-26 14:44:07.011 Info MediaEncoder: ProcessRun 'ffprobe' Started.
2019-03-26 14:44:07.129 Info MediaEncoder: ProcessRun 'ffprobe' Process exited with code 1
2019-03-26 14:44:07.129 Info App: [LinuxMount] Attempting to unmount ISO [/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso] mounted on [/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2].
2019-03-26 14:44:07.130 Debug App: [LinuxMount] Our current UID is [1038], GetUserId() returned [1038].
2019-03-26 14:44:07.130 Debug App: [LinuxMount] Umount command [/var/packages/EmbyServer/scripts/utilities/sbin/sudo], umount arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/umount" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"].
2019-03-26 14:44:07.136 Debug App: [LinuxMount] Waiting for process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/umount" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] to exit.
2019-03-26 14:44:07.238 Debug App: [LinuxMount] Process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/umount" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] has exited, exit code is [0].
2019-03-26 14:44:07.637 Debug App: [LinuxMount] Removed entry for process with arguments ["/var/packages/EmbyServer/scripts/utilities/sbin/umount" "/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2"] from the dictionary, the dictionary currently contains [0] key/value pairs.
2019-03-26 14:44:07.637 Debug App: [LinuxMount] Standard output from process is [].
2019-03-26 14:44:07.637 Debug App: [LinuxMount] Standard error from process is [].
2019-03-26 14:44:07.637 Info App: [LinuxMount] ISO unmount completed successfully.
2019-03-26 14:44:07.642 Error App: Error in ffprobe
    *** Error Report ***
    Version: 4.1.0.16
    Command line: /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121
    Operating system: Unix 3.10.35.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: False
    Mono: 5.18.0.240 (tarball Fri Jan 18 10:51:45 UTC 2019)
    Processor count: 2
    Program data path: /var/packages/EmbyServer/target/var
    Application directory: /volume1/@appstore/EmbyServer/releases/4.1.0.16-beta
    System.Exception: System.Exception: ffprobe failed for file:"/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2" - streams and format are both null:
    {
    
    }
    
    
    ffprobe version 4.0.2-emby_2018_12_09-20181220T000245UTC Copyright (c) 2007-2018 the FFmpeg developers
     built with gcc 7.3.0 (GCC)
     configuration: --prefix=/var/packages/EmbyServer/target/ffmpeg --enable-cross-compile --cross-prefix=x86_64-syno-linux-gnu- --target-os=linux --disable-rpath --enable-pthreads --arch=x86_64 --enable-libzimg --enable-libmfx --enable-vaapi --enable-x86asm --enable-gpl --enable-shared --disable-static --disable-debug --disable-ffplay --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --enable-gnutls --enable-libass --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libfreetype --enable-fontconfig --enable-gray --enable-libfribidi --enable-libvidstab --enable-libzvbi --disable-indev=sndio --disable-outdev=sndio --extra-version=20181220T000245UTC --extra-libs='-luuid -lstdc++'
     libavutil 56. 14.100 / 56. 14.100
     libavcodec 58. 18.100 / 58. 18.100
     libavformat 58. 12.100 / 58. 12.100
     libavdevice 58. 3.100 / 58. 3.100
     libavfilter 7. 16.100 / 7. 16.100
     libswscale 5. 1.100 / 5. 1.100
     libswresample 3. 1.100 / 3. 1.100
     libpostproc 55. 1.100 / 55. 1.100
    file:/tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2: Is a directory
    
    
     at Emby.Server.MediaEncoding.Encoder.MediaEncoder.GetMediaInfoInternal (System.String inputPath, System.String primaryPath, MediaBrowser.Model.MediaInfo.MediaProtocol protocol, System.Boolean extractChapters, System.String probeSizeArgument, System.Boolean isAudio, System.Boolean forceEnableLogging, System.Threading.CancellationToken cancellationToken) [0x001c9] in <8f3ae9eda6134706818ef68288d9fee7>:0
     at MediaBrowser.Providers.MediaInfo.FFProbeVideoInfo.ProbeVideo[T] (T item, MediaBrowser.Controller.Providers.MetadataRefreshOptions options, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions, System.Threading.CancellationToken cancellationToken) [0x00239] in <cfad3312f9b44ad4a92ca15f25556f67>:0
     at MediaBrowser.Providers.Manager.MetadataService`2[TItemType,TIdType].RunCustomProvider (MediaBrowser.Controller.Providers.ICustomMetadataProvider`1[TItemType] provider, TItemType item, System.String logName, MediaBrowser.Controller.Providers.MetadataRefreshOptions options, MediaBrowser.Providers.Manager.RefreshResult refreshResult, System.Threading.CancellationToken cancellationToken) [0x000d9] in <cfad3312f9b44ad4a92ca15f25556f67>:0
    Source: mscorlib
    TargetSite: Void Throw()
xpenology> ls -l /tmp/Emby/49509b8b-e89c-47d0-97bc-45bfe0fc3fc2/video_ts/
-r-xr-xr-x    1 root     root         12288 Jun 25  1998 video_ts.bup
-r-xr-xr-x    1 root     root         12288 Jun 25  1998 video_ts.ifo
-r-xr-xr-x    1 root     root      67176448 Jun 25  1998 video_ts.vob
-r-xr-xr-x    1 root     root         79872 Jun 25  1998 vts_01_0.bup
-r-xr-xr-x    1 root     root         79872 Jun 25  1998 vts_01_0.ifo
-r-xr-xr-x    1 root     root       4161536 Jun 25  1998 vts_01_0.vob
-r-xr-xr-x    1 root     root     1073739776 Jun 25  1998 vts_01_1.vob
-r-xr-xr-x    1 root     root     1073739776 Jun 25  1998 vts_01_2.vob
-r-xr-xr-x    1 root     root     1073739776 Jun 25  1998 vts_01_3.vob
-r-xr-xr-x    1 root     root     373321728 Jun 25  1998 vts_01_4.vob
@@Luke, your thoughts? The ISO is mounted successfully, the contents are present but FFprobe is failing. This is a test case for the ISO mounter we've been using for a long time now, so we know this works (or at least used to).
 
Having run through a few scenarios, we probably shouldn't be mounting the ISO at all for the FFprobe discovery and simply be passing the path to the ISO itself, as FFprobe is capable of dealing with this natively.
 
e.g.
/var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -i file:"/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).iso" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data

See attached for output.

 
Best
- James

ffprobe.txt

Edited by solabc16
Link to comment
Share on other sites

I think it's because we don't know what type of iso it is. Try putting .dvd or .bluray in the filename

Link to comment
Share on other sites

solabc16

Hello Luke

 

Changing the filename to...

/volume1/MyEmbyMedia/The Net (1995)/The Net (1995).dvd.iso

...or...

/volume1/MyEmbyMedia/The Net (1995)/The Net (1995)-dvd.iso

...results in the same error as reported in #60.

 

Best

- James

Link to comment
Share on other sites

  • 5 weeks later...
Seger

:-( 

 

Log Attach.

 

Replying to Emby Version 4 real-time monitoring is not working

 

 

---------------------

 

2019-04-26 17:19:50.555 Error LibraryMonitor: Error in Directory watcher for: /volume1/DiskStation/- Filme
    *** Error Report ***
    Version: 4.1.0.26
    Command line: /volume2/@appstore/EmbyServer/releases/4.1.0.26/EmbyServer.dll -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121
    Operating system: Unix 3.10.105.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///volume2/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll
    Processor count: 4
    Program data path: /var/packages/EmbyServer/target/var
    Application directory: /volume2/@appstore/EmbyServer/releases/4.1.0.26
    System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.
    Source:
    TargetSite:
    No Stack Trace Available
    
2019-04-26 17:19:50.555 Error LibraryMonitor: Error in Directory watcher for: /volume1/DiskStation/- Serien
    *** Error Report ***
    Version: 4.1.0.26
    Command line: /volume2/@appstore/EmbyServer/releases/4.1.0.26/EmbyServer.dll -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121
    Operating system: Unix 3.10.105.0
    64-Bit OS: True
    64-Bit Process: True
    User Interactive: True
    Runtime: file:///volume2/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll
    Processor count: 4
    Program data path: /var/packages/EmbyServer/target/var
    Application directory: /volume2/@appstore/EmbyServer/releases/4.1.0.26
    System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.
    Source:
    TargetSite:
    No Stack Trace Available

Edited by Seger
Link to comment
Share on other sites

Seger

@@Luke

@@solabc16

 

I have exhibited all my libraries and only started films myself. The feature has been disabled since Synology's Official 4.xx. In the beta time, the whole thing was still. Since the last update no improvement. It was put on the good database, but I think it could be something else. In the new log is not visible. Only when I give the impulse manually, the new film is found. Can you look at it please again, is already a very important feature.
 
2019-04-29 17:03:55.289 Error LibraryMonitor: Error in Directory watcher for: /var/packages/EmbyServer/target/var/data/collections
*** Error Report ***
Version: 4.1.0.26
Command line: /volume2/@appstore/EmbyServer/releases/4.1.0.26/EmbyServer.dll -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121
Operating system: Unix 3.10.105.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Runtime: file:///volume2/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll
Processor count: 4
Program data path: /var/packages/EmbyServer/target/var
Application directory: /volume2/@appstore/EmbyServer/releases/4.1.0.26
System.IO.IOException: System.IO.IOException: The configured user limit (8192) on the number of inotify watches has been reached.
Source: 
TargetSite: 
No Stack Trace Available
 
2019-04-29 17:03:55.289 Info LibraryMonitor: Stopping directory watching for path /var/packages/EmbyServer/target/var/data/collections
2019-04-29 17:03:55.290 Info TaskManager: ExecuteQueuedTasks
2019-04-29 17:03:55.791 Info LibraryMonitor: Watching directory /var/packages/EmbyServer/target/var/data/collections
2019-04-29 17:03:55.798 Error LibraryMonitor: Error watching path: /volume1/DiskStation/- Filme
*** Error Report ***
Version: 4.1.0.26
Command line: /volume2/@appstore/EmbyServer/releases/4.1.0.26/EmbyServer.dll -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121
Operating system: Unix 3.10.105.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Runtime: file:///volume2/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll
Processor count: 4
Program data path: /var/packages/EmbyServer/target/var
Application directory: /volume2/@appstore/EmbyServer/releases/4.1.0.26
System.IO.IOException: System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached.
   at System.IO.FileSystemWatcher.StartRaisingEvents() in /source/corefx/src/System.IO.FileSystem.Watcher/src/System/IO/FileSystemWatcher.Linux.cs:line 53
   at Emby.Server.Implementations.IO.LibraryMonitor.<>c__DisplayClass37_0.<StartWatchingPath>b__0()
Source: System.IO.FileSystem.Watcher
TargetSite: Void StartRaisingEvents()
 
 
 
Many Greetings,
Seger
Link to comment
Share on other sites

Seger

unfortunately it still does not work! Unfortunately, there is no real-time monitoring in the Synology universe since the final version 4.xx! Even the current version brings no improvement. the topic already has 1500 views, do you already have solutions? before 4.xx or in the beta phase of 4.xx everything went well.

Thanks and best regards
seger

Edited by Seger
Link to comment
Share on other sites

  • 1 month later...
Seger

@@Luke

@@solabc16

 

Hello everybody,

 

I wanted to highlight the issue again and ask if you could already reconstruct or fix the problem for version 4.2? If not, please tell me what to do, I would upload logs again if it does. unfortunately you did not see anything during the last logs. so simply stated, the real-time monitoring does not work at Synology since the 4.0 stable version anymore.

 

please give me a feedback, thank you guys!

 

many Greetings seger

Link to comment
Share on other sites

djhifi

Chiming in after Seger PM to me.

I do not have this problem mate. Only on one specific HDD actually. But even there, the content gets scanned, just not shown as notification on my browser (whenever I'm adding stuff to that disk and using the browser to navigate the server).

 

Have you checked file permissions on Synology? I remember sometimes having issues with that.

 

PS: The "inotify" dumps in the logs, as far as I remember has been there since several versions ago. Not actually messing up with realtime-monitoring.

Edited by djhifi
Link to comment
Share on other sites

  • Solution
Seger
@

 

@

 

 

@

 

 

 

 

 

 

 

 
 
I suppose my movie database is too big or that was a problem ...
 
 
 
But I think I have found a possible solution now:
 
 
   
 
 
 
After the changes, the automatic detection runs again. Is there a way to include this information in the next update, or do you need to pin this information to multiple Linux systems?
 
 
 
Many Greetings,
 
Seger
 
 
 
 
 
 
 
 
 
Edit / Tip: Just log in with WinSCP over root and edit the inputs via SSH. Remember that sudo -i is already root and you need to omit the sudo commands. I would edit the file of WinSCP in your place, since the nano-text editor is not installed by default. if you want to change the file (synology) via ssh you have to use the vi:
 
 
 
step 3
 
vi /etc/sysctl.conf
 
(As I said, I would just do it through the WinSCP interface.)

 

 

Edited by Seger
  • Like 2
Link to comment
Share on other sites

Seger
Please first read the post about it: then this little update:

 

 

 

 

Just added "Bloodline" and it worked very clean again. One thing has happened, the Emby server is once again restarted for unexplainable reasons. Upload the two related logs to the transparency (first Log.Log and then Log1.Log - are very small and clean):

 

 

 

 

 

Edited by Seger
Link to comment
Share on other sites

Killerpretzel

Hey guys!

 

I have been following this thread for a while now.

 

From what I have gathered, this problem is related to the inote watch limit of the inotify OS-service.

 

On synology systems, this limit is typicially set to 8192, which is rather low (for instance, on a Suse Linux Enterprise Server installation that I have also checked, the value was set to 65536). Unfortunately, it is impossible to change the setting via the webinterface. You could modify it by using ssh, but this is not retained across reboots and OS-updates.

 

The trick is to create a triggered task with the task scheduler and have it run after a (re-)boot.

 

I have found a thread describing how to do this in the 'syncthing' forum: https://forum.syncthing.net/t/setting-inotify-limit-permanently-on-synology-diskstation/12221/3

 

Following the instructions of the last post from user 'Ben', I was able to set the limit to a higher value in a reliable fashion.

 

I have several TBs of media across multiple libraries, after applying this 'hotfix', the real-time monotoring seems to be working again for me.

 

Give it a try.

 

Regards,

KP

Edited by Killerpretzel
Link to comment
Share on other sites

Seger

@@Killerpretzel

 

did not you see my post?
 
Here (Post 69):
 
I describe the problem after all and show the appropriate solution. In the link you will find all the steps that also take into account the corresponding restart. In step 3 it is described where the new line must be saved, with me the attitude survives a restart ;-).
 
The new value is in my example in the rest: 1048576
 
@@Luke, from the German Kodinerdsforum is also reported that it worked under an unRaid server.
 
FYI
 
Many Greetings,
Seger
Link to comment
Share on other sites

I've been using Emby for Windows for a while, but just got a Synology and decided to see how it worked with Emby. Everything works well (so far) except this real-time scanning issue for me as well. Everything works correctly as soon as I "Scan All Libraries" manually, but I can let something sit for a while and it won't show up. Just wanted to throw this out there because a completely new Emby install (Version 4.1.1.0) with only 2 movies (for testing) still has the issue, so it can't be because of library size.

 

Only found this thread because I was trying to figure out why it wasn't updating.

Edited by jpm
Link to comment
Share on other sites

Seger

I've been using Emby for Windows for a while, but just got a Synology and decided to see how it worked with Emby. Everything works well (so far) except this real-time scanning issue for me as well. Everything works correctly as soon as I "Scan All Libraries" manually, but I can let something sit for a while and it won't show up. Just wanted to throw this out there because a completely new Emby install (Version 4.1.1.0) with only 2 movies (for testing) still has the issue, so it can't be because of library size.

 

Only found this thread because I was trying to figure out why it wasn't updating.

yes, the size is not, but after the change as described above it works again. until now had only a small hook in it, but after a manual scan on scheduled tasks, the function real-time monitoring was back in tact

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...