Cannot get Plex to get Movies Metadata with either TMDB or Plex agents

Thanks, I found it immediately.

Did you recently change/adjust anything in the Plex share?

I ask because something changed the permissions such that PMS can’t write to its own metadata storage area.

2018-07-25 22:00:36,451 (7f032b735700) :  INFO (__init__:107) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fconfiguration
2018-07-25 22:00:36,454 (7f032a4fd700) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/library/metadata/93523/tree'
2018-07-25 22:00:36,454 (7f032b735700) :  CRITICAL (storage:89) - Exception writing to /volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.themoviedb/HTTP.system/d1/7f1d2f1427dcf09472b9044738378d2b3dc721_attributes (most recent call last):
  File "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-200287a06/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/storage.py", line 81, in save
    f = open(tempfile, mode)
IOError: [Errno 13] Permission denied: '/volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.themoviedb/HTTP.system/d1/._7f1d2f1427dcf09472b9044738378d2b3dc721_attributes'

Easy to fix

  1. Stop PMS
  2. Open the Plex share in File Station
  3. Right-click Library -> Properties
  4. Make sure plex is showing as the owner
  5. “Apply to this folder, sub-folders, and files” must also be checked
  6. Apply
  7. Be patient while it resets all the permissions on all the files in the Plex share
  8. Start PMS

Yeah I transferred my server from windows to synology today. I had to do it a couple times because it didn’t work right. I’ll try that. Thanks!

Fixed! Thanks, you rock!

1 Like

i’m in the same boat. thetvdb works getting metadata but tmdb doesn’t. disabled ipv6 – it now finds the movie using the manual tmdb search from plex, but it still doesn’t pull the metadata. i need some help here. logs are attached. thanks!

Plex Media Server Logs_2018-10-20_23-42-46.zip (5.5 MB)

@Arauco

Your logs show the TMDB agent is confused. Likely from the IPv6 of earlier…

2018-10-20 23:40:19,935 (700009ed7000) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/library/metadata/156658/tree'
2018-10-20 23:40:19,942 (700009ed7000) :  DEBUG (networking:161) - Fetching 'http://127.0.0.1:32400/services/tmdb?uri=%2Fconfiguration' from the HTTP cache
2018-10-20 23:40:19,945 (700009ed7000) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Dde'
2018-10-20 23:40:22,712 (700009ed7000) :  ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Dde'
2018-10-20 23:40:22,712 (700009ed7000) :  INFO (__init__:107) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Dde
2018-10-20 23:40:22,714 (700009ed7000) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D'
2018-10-20 23:40:25,633 (700009ed7000) :  ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D'
2018-10-20 23:40:25,634 (700009ed7000) :  INFO (__init__:107) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D
2018-10-20 23:40:25,636 (700009ed7000) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%2Fimages'
2018-10-20 23:40:28,391 (700009ed7000) :  ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%2Fimages'
2018-10-20 23:40:28,391 (700009ed7000) :  INFO (__init__:107) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2F9085%2Fimages
2018-10-20 23:40:28,392 (700009ed7000) :  INFO (__init__:568) - TMDb was unable to get any metadata for 9085 (lang = de)

Now it’s time to Manually clear the Caches.

  1. Stop PMS
  2. Open FileStation
  3. Navigate Plex/Library/Application Support/Plex Media Server/Plug-in Support/Caches
  4. Delete everything you find there.
  5. Restart PMS
  6. Go to the section needing full refresh.
  7. Force “Refresh All Metadata”

Thank you @ChuckPa, that did it! Hope this helps others, too.

Hey @ChuckPa - Thanks for spending your time and spilling your wisdom here!

I’ve had a lot of troubles with my Movie metadata as well. I’ve tried reinstalling Plex, clearing caches, doing the dance, disabling IPv6, and a lot of other stuff, including everything mentioned in this thread and others.

I keep getting: “Error issuing curl_easy_perform(handle): 28”, which from this thread I understand is a timeout, however, I can’t seem to figure out which response is timing out. I can ping both IMDB and TheMovieDB - however with a bit higher ping times, peaking at 510 ms, averaging around 200-250ms, but I don’t suppose that should be a problem.

Initially all movies were matched perfectly, with all posters correct, but new movies won’t update posters. XML files seems to indicate a match with imdb.

A few movies has lost their posters again, after having them initially (with no manual interaction).

I might suspect my router not behaving, but I had no issues with the same files running on my MacBook Pro. Router is a Sagemcom FAST 3890.

The server runs on a Synology DS918+, Plex 1.13.4.5271

I don’t get this at all.

I hope someone can shed some light on the subject. This is quite annoying :smiley:

Woops - forgot to add logs:
Plex Media Server Logs_2018-11-19_01-46-33.zip (4.6 MB)

I’m not happy about the 500 ms ping but ok if it works.

I can’t find the curl errors.

Can you point them out to me? File name / Line number ?

Or recreate them?

I’m not either, but I live in Denmark, and that might be why. I have a 100/15 Mbps connection, which is usually pretty swift. Today however, the peak was 356ms averaging at 204 ms.

The curl errors are in the Plex Media Server.log (and the numbered ones as well). There are hundreds of them, so they should be rather easy to spot. There are also one or two curl_easy_perform 7 and 6 errors in there. Most are 28.

I also woke up to a weird console, seeming to both download posters and sending login-information to plex. I for instance discovered a link to a poster to one of the movies without a poster. Quite weird, seeing it in the console, but not saving the link, so the movie keeps the poster. Not sure how to describe it, but I’ll find the logs again, if you need me to.

Restarted the server, it began in the console a few hundred lines down with this:

QueryParser: Invalid field ‘onlyTransient’ found, ignoring.

It’s in Danish - “Fejl” means “Error”.

Nov 19, 2018 11:13:08.792 [0x7f767a26b700] Debug-niveau — Auth: authenticated user 1 as TNE26
Nov 19, 2018 11:13:08.805 [0x7f767b111700] Debug-niveau — Auth: authenticated user 1 as TNE26
Nov 19, 2018 11:13:08.858 [0x7f767b111700] Debug-niveau — Computed media url for item 10720: https://image.tmdb.org/t/p/w154/d4uHTIIxuhChFoLkg34CbTMvIyo.jpg
Nov 19, 2018 11:13:08.858 [0x7f767b111700] Debug-niveau — Calling back into ourselves for photo to transcode, optimizing the process (status: 302)
Nov 19, 2018 11:13:08.860 [0x7f767a26b700] Debug-niveau — Computed media url for item 10785: https://image.tmdb.org/t/p/w154/hOrV2fCw2kmSiS4ZMGFPfXqr3lt.jpg
Nov 19, 2018 11:13:08.860 [0x7f767a26b700] Debug-niveau — Calling back into ourselves for photo to transcode, optimizing the process (status: 302)
Nov 19, 2018 11:13:08.894 [0x7f767b111700] Debug-niveau — HTTP requesting GET https://image.tmdb.org/t/p/w154/d4uHTIIxuhChFoLkg34CbTMvIyo.jpg
Nov 19, 2018 11:13:08.894 [0x7f767a26b700] Debug-niveau — HTTP requesting GET https://image.tmdb.org/t/p/w154/hOrV2fCw2kmSiS4ZMGFPfXqr3lt.jpg
Nov 19, 2018 11:13:08.913 [0x7f767c735700] Debug-niveau — HubCache: Computed '1/home.movies.recent/hubs/da/count=16&excludeFields=summary&excludePlaylists=1&includeEmpty=1&includeExternalMetadata=1&includeFeaturedTags=1&includeStations=1&onlyTransient=1' in 152 ms.
Nov 19, 2018 11:13:08.913 [0x7f767c735700] Debug-niveau — HubCache: Adding '1/home.television.recent/hubs/da/count=16&excludeFields=summary&excludePlaylists=1&includeEmpty=1&includeExternalMetadata=1&includeFeaturedTags=1&includeStations=1&onlyTransient=1' to the cache (1/home.television.recent/hubs/da/count=16&excludeFields=summary&excludePlaylists=1&includeEmpty=1&includeExternalMetadata=1&includeFeaturedTags=1&includeStations=1&onlyTransient=1).
Nov 19, 2018 11:13:08.915 [0x7f767c735700] Fejl — QueryParser: Invalid field 'onlyTransient' found, ignoring.
Nov 19, 2018 11:13:08.935 [0x7f767c735700] Debug-niveau — It took 10.000000 ms to retrieve 200 items.
Nov 19, 2018 11:13:08.936 [0x7f767c735700] Fejl — QueryParser: Invalid field 'onlyTransient' found, ignoring.
Nov 19, 2018 11:13:08.946 [0x7f767ab35700] Advarsel — SLOW QUERY: It took 210.000000 ms to retrieve 80 items.
Nov 19, 2018 11:13:08.954 [0x7f767c735700] Debug-niveau — It took 30.000000 ms to retrieve 410 items.
Nov 19, 2018 11:13:08.954 [0x7f767c735700] Fejl — QueryParser: Invalid field 'onlyTransient' found, ignoring.
Nov 19, 2018 11:13:08.989 [0x7f767c735700] Debug-niveau — It took 40.000000 ms to retrieve 632 items.
Nov 19, 2018 11:13:09.044 [0x7f7679f7d700] Debug-niveau — HTTP 200 response from POST http://127.0.0.1:32600/devices/discover
Nov 19, 2018 11:13:09.175 [0x7f767ab35700] Debug-niveau — Setting container serialization range to [16, 50] (total=-1)
Nov 19, 2018 11:13:09.177 [0x7f767c735700] Debug-niveau — HubCache: Computed

The “Error” is meaningless. Engineering will clean that up.

Nov 19, 2018 11:13:08.946 [0x7f767ab35700] Advarsel — SLOW QUERY: It took 210.000000 ms to retrieve 80 items.

is actually the more important issue.

PMS cannot communicate with itself quickly enough.

Notice how it is slow here. Immediately below, it is quick enough to retrieve 410 items as well as 632 items. Something else on the system is utilizing a lot of CPU

That is weird… It’s a brand new machine, not much on it, and it runs almost idle, except for Plex. 4 brand new 8TB WD Red Pro harddrives in RAID 5 - shouldn’t be slow, but all queries to TMDB seems dreadfully slow. Matching items takes forever, as well as refreshing metadata (even though it doesn’t work anymore).

What can you say about the curl 28 errors - any idea of the cause? And if they are the cause of the poster-problem? I know too little of the engineering behind plex to fully understand how it works and to troubleshoot.

Movies, music and TV plays perfectly fine without any peaks in system usage, both from local and from a remote location.

Your logs show me the last actual queries were made on 14 Nov to TMDB.

Can you perform a full Plex Dance of a few titles?

(move out, scan files, empty trash, clean bundles, move back, scan files) = Dance

I just did. It scans fine, and fast, but no metadata. The console shows more “Error issuing curl_easy_perform(handle): 28” errors…

Where in the logs can you see the last actual query? And is there an indication on why it hasn’t done one since? Or is that where the errors started?

Get the entire ZIP.

Open it.

Look in the TMDB log

Ah I see it now.

Thanks for your time!

Do you have any ideas for me to work with? Should I try reinstalling the server from scratch again? It seemed to work every second time…

I unfortunately do not have time today. It is now 18.00h here.

Fair enough - if you get some time in the near future, please let me know! I would really appreciate your assistance! Have a great night! :slight_smile:

@ChuckPa - I read a different thread, where you also replied. I think my issue might come down to me using BTRFS instead of ext4… I didn’t know it would be such a performance-killer. I just ordered an external drive, to empty my NAS onto, and will reformat to ext4. It seems like that will fix the problem. Will update when done!