Help Troubleshooting Broken Real Time Monitoring

[mrsmithb 11]

58 minutes ago, Carlo said:

There's the answer. Realtime update depends on the OS making a notification that programs can respond to.
The OS only sends this notification for files on disk that it manages. This doesn't work for network attached storage.

Well the thing is....it worked, flawlessly. For YEARS. Then I started having problems. And it still works SOMETIMES, but it doesn't seem to last long.

[TMCsw 249]

3 hours ago, mrsmithb said:

Well the thing is....it worked, flawlessly. For YEARS. Then I started having problems. And it still works SOMETIMES, but it doesn't seem to last long.

Perhaps, you disabled/changed the schedule for this? at some time in those YEARS? 

Edited November 7, 2024 by TMCsw
added in

[mrsmithb 11]

9 hours ago, TMCsw said:

Perhaps, you disabled/changed the schedule for this? at some time in those YEARS? 

Confused as to what you mean by this. I have changed the SCHEDULED media library scan, but that's because I want Real Time Monitoring to do the work, so that a scheduled scan is not necessary. RTM should be completely independent of this setting??

[mrsmithb 11]

As a test, I have created a new library that mirrors my existing Local Movies library. But using the network address for the file folder instead of the mapped network drive address.

\\NAS3EF1C9\L Drive Mirror\Videos\Movies

instead of 

L:\Videos\Movies

I made sure debugging was on, did a server reboot, and have been periodically adding new media. So far, RTM has picked up all changes immediately, on both libraries. This isn't shocking considering past tests show RTM works (for a while) after a server reboot. This new test should reveal how long it takes after server reboot for RTM to break, and HOPEFULLY RTM will continue to work on the new mirror library (we will see).

[mrsmithb 11]

Added several new movies yesterday throughout the day, every one of them instantly picked up by real time monitoring, on both libraries. This morning at 06:00, added a new movie. Two hours later, RTM failed to pick it up, on either library. A manual scan on each library and the movie was added.

Back to square one I guess.

[Luke 42078]

Thanks for the update. I would still suggest using the original network location rather than a mapped drive.

[mrsmithb 11]

I did manage to mitigate some of the problem by enabling connections between radarr/sonarr and emby, having it trigger a library scan when those applications add new content. I had never needed this before when RTM worked. It solves most of my issues, unless I am manually adding content outside of the *arrs.

[Carlo 4561]

Before when it was working, was your media on a local drive?
RTM doesn't work on network drives without a relay mechanism as this is an OS notification to programs/services running on the host where the media is located.

Carlo

[mrsmithb 11]

6 minutes ago, Carlo said:

Before when it was working, was your media on a local drive?
RTM doesn't work on network drives without a relay mechanism as this is an OS notification to programs/services running on the host where the media is located.

Carlo

No, my media has been on a network drive for many many years now. And like I mentioned, RTM still works after a server restart, but it seems to fail within 24 hours or so...

[Luke 42078]

Did you try what I suggested?

[mrsmithb 11]

36 minutes ago, Luke said:

Did you try what I suggested?

I did...instead of reverting to the original library, I deleted it and kept the mirror library (with the network address instead of mapped drive), and made mirrors of the other libraries using the same format. I haven't done any further testing, as the Radarr/Sonarr connections have been working perfectly.