Help Troubleshooting Broken Real Time Monitoring

[dropshadow 12]

i have the same problem, RTM seems to stop working after the server has been running for a while (days). a server restart will always solve the problem. i only use network paths for folders.

this is a win server 2019. i have 8 local drives in JBOD configuration and then running stablebit drivepool to present the JBOD array as a single mapped drive to windows, which it does consider local. i did not have any issues for years as well, and in the last year or so, i have started noticing the problem more and more. i can provide log files, but when RTM does not work, the entries just are not there when i add/move files around. please advise how to troubleshoot.

Edited December 3, 2024 by dropshadow

[Luke 42078]

Hi there @dropshadowlet's look at a specific example:

How to Report a Problem

Thanks !

[dropshadow 12]

ok, might need to wait a few days. i just restarted emby service last night. i just tried and RTM did pick up the file. let me see if it will fail over the next few days.

[dropshadow 12]

i think i finally figure it out. i noticed this after recently doing a server restart:

2025-01-28 12:44:53.551 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Animation because the path is currently not available
2025-01-28 12:44:53.556 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Documentary because the path is currently not available
2025-01-28 12:44:53.562 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Home Movies because the path is currently not available
2025-01-28 12:44:53.566 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\International because the path is currently not available
2025-01-28 12:44:53.573 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\ipad photo frame because the path is currently not available

i think that my emby service is starting and my drivepool is not ready. i have 8x8tb pooled into a single drive Z (ZEUS) using stablebit drivepool. i think the pool is not ready when emby starts, library paths not found. it is a 24/7 win server. i am using an NSSM auto start service on server startup. will emby check for these folder monitors again and check the paths?

[Luke 42078]

On 1/28/2025 at 7:43 PM, dropshadow said:

i think i finally figure it out. i noticed this after recently doing a server restart:

2025-01-28 12:44:53.551 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Animation because the path is currently not available
2025-01-28 12:44:53.556 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Documentary because the path is currently not available
2025-01-28 12:44:53.562 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\Home Movies because the path is currently not available
2025-01-28 12:44:53.566 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\International because the path is currently not available
2025-01-28 12:44:53.573 Info LibraryMonitor: Skipping realtime monitor for \\omega.wangfei.com\ZEUS\Media\ipad photo frame because the path is currently not available

i think that my emby service is starting and my drivepool is not ready. i have 8x8tb pooled into a single drive Z (ZEUS) using stablebit drivepool. i think the pool is not ready when emby starts, library paths not found. it is a 24/7 win server. i am using an NSSM auto start service on server startup. will emby check for these folder monitors again and check the paths?

Hi, it does not periodically recheck them, no. Only when first starting up the server.

[dropshadow 12]

16 minutes ago, Luke said:

Hi, it does not periodically recheck them, no. Only when first starting up the server.

what would you suggest here then? if it never checks again, my emby instance is running without folder monitoring. i can perhaps code a delay in NSSM or something or just manually run the emby service at server restart, but a long term solution that doesnt involve my touchpoint would be ideal.

[Clackdor 109]

57 minutes ago, dropshadow said:

what would you suggest here then? if it never checks again, my emby instance is running without folder monitoring. i can perhaps code a delay in NSSM or something or just manually run the emby service at server restart, but a long term solution that doesnt involve my touchpoint would be ideal.

Under services what are the startup types for the Drivepool service and the emby service created by NSSM? Also just to clarify, emby and Drivepool are running on the same server right?

I'm also using Drivepool and have Emby running as a service with NSSM. On my server the Drivepool service is set to Automatic and the Emby service is set to Automatic(Delayed Start). I never have any issues with this config.

Try setting the Emby service to Automatic(Delayed Start) and that should resolve your problem. If for whatever reason it doesn't you can add a dependency for the Drivepool service to the Emby service in NSSM. This will ensure that Drivepool is running prior to emby starting.

Edited January 30, 2025 by Clackdor
Asking for additional info

[dropshadow 12]

6 minutes ago, Clackdor said:

Try setting the Emby service to Automatic(Delayed Start) and that should resolve your problem. If for whatever reason it doesn't you can add a dependency for the Drivepool service to the Emby service in NSSM. This will ensure that Drivepool is running prior to emby starting.

wow, exact same use case. everything is automatic right now, i will try and set emby/NSSM to automatic-delayed start. thanks for the tip and will monitor!

[Clackdor 109]

2 minutes ago, dropshadow said:

wow, exact same use case. everything is automatic right now, i will try and set emby/NSSM to automatic-delayed start. thanks for the tip and will monitor!

No problem! Report back at some point and let me know whether or not that fixes it for you.

[dropshadow 12]

On 1/29/2025 at 9:08 PM, Clackdor said:

No problem! Report back at some point and let me know whether or not that fixes it for you.

 

everything has been working great once i set the service to auto delayed. i have done several reboots and have not seen the issue again. thanks!