Metadata providers not running?

[Protected 86]

This is a little embarrassing, but vanilla (bundled) metadata providers like moviedb, thetvdb, etc. don't seem to be functioning in my setup and I have no idea why.

During my initial testing they were working properly. Lately I spent several days working on my setup based on the home video and photo library type. Today, I wanted to run some tests with other library types, but to my surprise when I create additional libraries with other types such as movies, tv shows or mixed content, refreshing the metadata doesn't seem to trigger any functionality on the moviedb, etc. metadata providers, and no metadata is added to the media items. Does anyone have any inkling of what obvious thing I might have broken, and how?

I'm testing on two setups, windows and linux. I'm not getting metadata on either setup.

The metadata provider plugins log as present on the server logs. However, refreshing the metadata only logs (even in debug mode) stuff from VideoNfoProvider, MediaProbeManager, and the metadata providers from my own plugins.

The metadata providers are active in the library settings.

Removing my own plugins from the server - or in other words, putting the server in a fully vanilla state - and restarting it does not solve the problem.

When manually requesting metadata, I'm setting the replacement mode to replace everything, but that doesn't help.

[Protected 86]

I created a test library (new hard drive location) for generating a log to attach here and the metadata providers work on that. I'm running further tests, but maybe there was database corruption or something?

Edited August 7, 2024 by Protected

[Luke 42079]

Hi there, let's look at a specific example:

How to Report a Problem

Thanks.

[Protected 86]

My preliminary conclusion is that Emby doesn't like it when library folders overlap. It's not clear from the UI, since libraries are displayed separately in the metadata manager, and there is no indication of priority in the list of libraries, but whichever library is oldest will apparently own the folder. The settings of any additional libraries that contain that folder will only apply if all libraries older than them are removed before metadata is refreshed. Mystery solved?

[pwhodges 2012]

14 minutes ago, Protected said:

My preliminary conclusion is that Emby doesn't like it when library folders overlap.

This is not supported, and a range of strange issues will result.

Why are you doing this?  There may be another way to get the result you want within the rules.

Paul

[Happy2Play 9781]

15 minutes ago, Protected said:

Mystery solved?

To a point yes, but now overlapping libraries will/can eliminate the library showing no content and possibly create database issues that are not correctable.

Yes there needs to be some method via the UI giving a warning of overlapping libraries or just make it not possible to add overlapping libraries.

But overall reason for this setup would need to be known.