Metadata lookup failing for one set of files (others are working fine)

[ChrisJ60 13]

Having a problem getting Emby to find the metadata for The Mandalorian Season 3. We have Season 1 and 2 already and the automatic metadata lookup worked fine for those. We added Season 3 (files are same type and have the same naming conventions as S1/S2 etc.) but the queries to TheTVDB seem to not find a nothing (as far as I can discern from the debug log). Yet if I go to TheTVDB site the series is there.

We're able to add other show series/episodes and the metadata lookup works just fine. Only The Mandalorian Season 3 seems to have an issue. It's perplexing.

Debug log attached (issue is near the end). 

Anyone have any ideas?

Thanks!

embyserver_bad.txt

[Junglejim 385]

Yep that is strange, have you tried deleting season 3 from emby, run library scan then add it back again and rescan?

It all looks good as far as naming goes, I see a few IO exceptions referencing jpg's etc. maybe a permissions issue?

Is season 3 just media files? (mkv/mp4) or do you have extra garbage (nfo/jpg/txt), they could be hidden..

[ChrisJ60 13]

We tried that but it made no difference. I think the exceptions might be because Emby still had soem references to those files (the automatic cleanup when we removed the files maybe hadn't finished at that point). The Season 3 folder only contains the .mkv files, nothing else (hidden or otherwise).

[GregMo 24]

I would try removing the chapter numbers as a test.  I have seen some things that I would have never thought would have broken the scraping that stopped it till I changed it.

[Junglejim 385]

3 minutes ago, ChrisJ60 said:

We tried that but it made no difference. I think the exceptions might be because Emby still had soem references to those files (the automatic cleanup when we removed the files maybe hadn't finished at that point). The Season 3 folder only contains the .mkv files, nothing else (hidden or otherwise).

OK, that is strange, I added season 3 of Mando no problem and your naming is right.

 

3 minutes ago, GregMo said:

I would try removing the chapter numbers as a test.  I have seen some things that I would have never thought would have broken the scraping that stopped it till I changed it.

mmm, not sure about that, this is how "Auto Organize" named mine (The Mandalorian - 3x01 - Chapter 17 The Apostate) and that works.

[ChrisJ60 13]

Removing the 'Chapter 17' from the filename made no difference (S1 and S2 have 'Chapter N' in their filenames and it happily found all the metadata for those when they were originally added). Changing the filename to be 'The Mandalorian - 3x01 - Chapter 17 The Apostate.mkv' also made no difference (I removed the file via Emby each time before re-adding it). It just can't find the metadata for some reason.

 

 

[GregMo 24]

13 minutes ago, Junglejim said:

mmm, not sure about that, this is how "Auto Organize" named mine (The Mandalorian - 3x01 - Chapter 17 The Apostate) and that works.

Yeah.  I just created "The Mandalorian\Season 3\The Mandalorian s03e01 - Chapter 17 The Apostate.strm" as a test and it picked it up fine.

System.IO.DirectoryNotFoundException: System.IO.DirectoryNotFoundException: Could not find a part of the path '/volume6/NAS/Media Library/Video/TV/The Mandalorian/Season 3/The Mandalorian - s03e01 - Chapter 17 The Apostate-thumb.jpg'.

This error here indicates that Emby can't access the path correctly.  Searching on "Could not find a part of the path" reveals a couple of things that might be wrong.  We know it's not a length in /path/to/file so next I would check permissions and special characters in directory and file names.

[Junglejim 385]

3 minutes ago, ChrisJ60 said:

Removing the 'Chapter 17' from the filename made no difference (S1 and S2 have 'Chapter N' in their filenames and it happily found all the metadata for those when they were originally added). Changing the filename to be 'The Mandalorian - 3x01 - Chapter 17 The Apostate.mkv' also made no difference (I removed the file via Emby each time before re-adding it). It just can't find the metadata for some reason.

 

 

The naming you had was totally ok (SxxExx)! Can you ping the meta providers? maybe a ISP problem.

[ChrisJ60 13]

Those messages are old and represent Emby trying to delete files that had already been removed external to Emby. Attached is a new debug log - look at the entries from '2023-04-21 13:43:21.525'. Everything looks fairly normal other than that the metadata lookups return 'no metadata found'. Emby quite happily reads the file (the various ffprobe commands succeed) and writes extracted artwork and an NFO file, so no permissions issues.

embyserver.txt

[ChrisJ60 13]

Yes, I can go to their web-sites without any issues. My Internet connection is fully functional (I have multiple automated tests that run very frequently - I get to know of any significant issues within minutes). This morning we added several other files to Emby  and it got the metadata for those without any issues at all. It isn't a general issue, it seems  specific to these files (but why!).

 

Edited April 21, 2023 by ChrisJ60

[Junglejim 385]

Holy Moley mate.. lol.. I've run out of ideas, this is totally weird.

I must admit I'm not the best at reading log files but I didn't see anything that jumped out.

[rbjtech 5284]

Hmm - very odd - emby itself is picking up the files fine, but it's reporting the Providers cannot identify it.

Do you have an NFO's etc - worth deleting ALL files except for the video files.

I would also remove, run scan library and scan metadata (in schedule), trim/vaccum the db, restart and then try and add again.

[Junglejim 385]

20 minutes ago, rbjtech said:

Hmm - very odd - emby itself is picking up the files fine, but it's reporting the Providers cannot identify it.

Do you have an NFO's etc - worth deleting ALL files except for the video files.

I would also remove, run scan library and scan metadata (in schedule), trim/vaccum the db, restart and then try and add again.

Yeah it is very odd, I think @ChrisJ60would of tried/confirmed most of this, he seems to have tried everything..

Restart your server? who knows..   what is it? Mine is OMV.

Edited April 21, 2023 by Junglejim

[GregMo 24]

28 minutes ago, rbjtech said:

Hmm - very odd - emby itself is picking up the files fine, but it's reporting the Providers cannot identify it.

That's a very slick looking viewer you're using.  What is it?

[rbjtech 5284]

4 hours ago, GregMo said:

That's a very slick looking viewer you're using.  What is it?

Emby Official Support Tools ...  but there are many alternatives that I use - Advanced Log Viewer with an emby log parser is actually much more powerful, but the Emby Support Tools are integrated with the forums to auto download the log files - making it all very quick ..

The good news is the logs are a pretty generic 'standard' so most log viewers can likely read (and filter) them live.