TurkeyMan 17 Posted October 28, 2023 Posted October 28, 2023 I just added some new media today, and it's fetching the title and cover image from IMDB instead of TVDB as it normally does. It's not fetching the season images, and it's not populating the episodes with titles and text. I thought it might be an identification quirk, so I chose "Identify" and entered the TVDB ID, which it resolved, showed in the list (with proper images), it accepted and then sat for 5 minutes while appearing like it was repopulating the metadata, but when it complete, it failed. I checked this against a couple other shows, same behaviour. Anyone else seen this, or anything like this?
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 Hi there, let's look at an example. Please attach the information requested in How to Report a Problem.
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 (edited) The logs contain a flood of errors like: Error App: Error in TheTVDB ... MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Unauthorized ... Error ProviderManager: TvdbSeasonImageProvider failed in GetImageInfos for type Season ... MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Unauthorized ... etc. Is it just me? Edited October 28, 2023 by TurkeyMan
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 1 hour ago, TurkeyMan said: Is it just me? It likely is, else we'd be seeing a lot more reports like yours. Post complete server log.
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 Unless they just changed their policy like, in the last 5 minutes and I'm the first to post Try it, see if you can re-scan metadata just now?
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 Are they known to have any rate limiting stuff? Maybe they've decided my IP has scanned too much?
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 1 hour ago, TurkeyMan said: Unless they just changed their policy like, in the last 5 minutes and I'm the first to post That's always a possibility. 1 hour ago, TurkeyMan said: Try it, see if you can re-scan metadata just now? I would if I could, but I'm in the middle of the Red Sea currently, my installation is offline. Out of curiosity, have you tried rebooting your server machine (is that a NAS)?
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 Just now, GrimReaper said: Out of curiosity, have you tried rebooting your server machine (is that a NAS)? Fair call.... I mean, it fetches stuff though; it fetches from IMDB instead, but IMDB data is not comprehensive.
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 1 hour ago, TurkeyMan said: it fetches from IMDB instead, but IMDB data is not comprehensive Nah, Emby doesn't get anything from IMDB (cost-prohibitive), it's either TMDB or OMDB. Maybe it's just affecting TVDB API. I'd still give it a try.
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 (edited) Okay, I restarted, and the problem resolved. Pretty weird problem with surprising symptoms! A message like "MediaBrowser.Model.Net.HttpException: Unauthorized" doesn't seem like a local problem, and it wasn't a networking problem, since it fetched images and titles from IMDB [somewhere else] as fallback. Edited October 28, 2023 by TurkeyMan
TurkeyMan 17 Posted October 28, 2023 Author Posted October 28, 2023 2 minutes ago, GrimReaper said: Nah, Emby doesn't get anything from IMDB (cost-prohibitive), it's either TMDB or OMDB. Maybe it's just affecting TVDB API. I'd still give it a try. Hmm, well it fetched the cover image that I see on IMDB, and not any image present on TVDB, so I just assumed.
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 1 hour ago, TurkeyMan said: Hmm, well it fetched the cover image that I see on IMDB, and not any image present on TVDB, so I just assumed. Fair assumption, but it's just likely that one of the other two providers have a same image. Hence the stuff from above: How to report a problem: example, log, etc..
GrimReaper 4744 Posted October 28, 2023 Posted October 28, 2023 1 hour ago, TurkeyMan said: Okay, I restarted, and the problem resolved. Ah, haven't seen this. Nice, glad we got you sorted.
trifleneurotic 63 Posted October 28, 2023 Posted October 28, 2023 Hello everybody! Just wanted to drop in to say the exact same thing happened to me this morning! Restarting the Emby Server process from the CLI of the operating system where Emby resides had no effect. However, restarting it from the UI (Dashboard) got me back to where I needed to be. Weird..... 1
flashls82 4 Posted October 29, 2023 Posted October 29, 2023 I’ll add just to note it was not just the OP. Same experience: no metadata was fetching properly, rebooting Emby server from the UI fixed it (I’m on a Synology NAS). 1
fraenhawk 61 Posted October 31, 2023 Posted October 31, 2023 Just came here searching for this problem and the endless TargetSite: Void messages being logged when refreshing metadata. Restarting from the dashboard and then refreshing metadata worked for me as well.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now