mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
[Issue]: Metadata retrieval from TheMovieDB stalls, and then prevents library scan from completing #5242
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aoberoi on GitHub (Nov 15, 2023).
Please describe your bug
I ran into an issue with the initial scan of my media files in a library with content type "Shows". The scan initializes but then there's no feedback whatsoever, many minutes later I saw one episode, unassociated to a show, that had no metadata. The remaining files (a total of 4) never appeared. The logs didn't give any clear indication of what was happening. After a painful troubleshooting process that took many hours, on a whim, I decided to disable TheMovieDB as a metadata source. This allowed the scan to complete, for the show to appear, its corresponding seasons, and episodes.
Based on this experience, I think there are several changes we could make to Jellyfin, to help users (especially new ones) avoid the roadblock I faced. Here are some ideas:
Jellyfin Version
10.8.z
if other:
10.8.12.0
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@aoberoi commented on GitHub (Nov 15, 2023):
Troubleshooting done in the matrix chat, most of it in this thread: https://matrix.to/#/!YjAUNWwLVbCthyFrkz:bonifacelabs.ca/$TuzlCSN_g20S79pm4LhZQzbo47O7SgJDKbejiIx6Kl8?via=matrix.org&via=t2bot.io&via=bitwrk.de
@aoberoi commented on GitHub (Dec 5, 2023):
I'm having this issue now, but without TheMovieDB. I think this means the issue is generalized other (or maybe all) metadata sources. Here is a recent log:
@cchristchurch commented on GitHub (Dec 20, 2023):
👍 This is by far the biggest issue I'm experiencing with Jellyfin.
I've spent hours and hours trying to get metadata retrieval to work correctly since setting up my server 3 months ago. The main problem is that even when set to DEBUG log level, Jellyfin logs close to zero useful information about the metadata retrieval process.
Adding a few logs here would probably be a fairly easy way to massively improve the admin experience. I'm happy to help but with absolutely no knowledge of C# (or .net or any similar language) it's likely I'd do more harm than good. I think we'd need the following extra logs (in DEBUG level):
Some examples of problems that this would greatly help with:
curl --request GET --url "https://api.themoviedb.org/3/movie/11?api_key=JELLYFIN_API_KEY"on the box and it seems to work fine so it does not seem to be a connectivity issue this time. I suspect the retriever is making more requests with different parameters and maybe some of those are temporarily failing, but again that's very hard to say without logs.@cchristchurch commented on GitHub (Dec 20, 2023):
I suspect this could be where most of the relevant logs could be added.
That would only cover TheMoviedDB though and possibly other retrievers would need the same
@cchristchurch commented on GitHub (Dec 20, 2023):
Also I can confirm I currently see the same behavior as originally reported here by @aoberoi : whatever error is happening is causing the scan to completely stall or fail and then no movies get added to the database ... so no new movie can get added to my library (even without metadata, even if I put the metadata manually in the jellyfin UI).
Given the impact of the bug (essentially making jellyfin completely unusable) it seems really important to at least log something. In the long term I also agree it would be nice to actually handle the error better (and maybe just not make my library unusable if TMDB stops returning data) but I suspect that is significantly more work, so possibly a quicker log-only fix would be preferrable before we start thinking how these rerrors could be handled better and / or exposed through the UI.
@cchristchurch commented on GitHub (Dec 20, 2023):
Final update for the day, I finally figured out what my new issue was (or rather, how to fix it): If I disable the second metadata retriever (The Open Movie Database), things work perfectly again.
I disabled it both as a Metadata Retriever and as an Image Fetcher. Now the metadata and images are successfully retrieved from TheMovieDB and my jellyfin database is updated correctly again when I add a new movie.
So to summarize, quite a few different problems here:
Hope that's useful!
@jellyfin-bot commented on GitHub (Apr 19, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (May 10, 2024):
This issue was closed due to inactivity.
@cchristchurch commented on GitHub (May 10, 2024):
@Bond-009 commented on GitHub (May 18, 2024):
Please check with the latest release, 10.9.2 at this point in time and report back.
@cchristchurch commented on GitHub (May 19, 2024):
Thanks for looking into this @Bond-009
I've just upgraded to
10.9.2+deb12and I attempted to reproduce the issue:During the refresh, I see the following log pattern for every movie:
From the above, I see which retriever gets called for which movie but the logs still seem to be missing information that can be useful to troubleshoot a problem (see previous post for suggestions on potentially useful information to log).
The scan completed and the movies are appearing correctly, however without more information in the logs it's a bit unclear exactly what has been fixed regarding the issues listed here:
In short, it's unclear which issue, if any, have been fixed on the jellyfin side. I think it's worth keeping this open, if only to track the addition of a couple of debug logs.
@jellyfin-bot commented on GitHub (Sep 16, 2024):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Oct 7, 2024):
This issue was closed due to inactivity.