Cannot update movie metadata

General Discussions
1

I am running version 1.5.5.3634-995f1dead on Centos 7. I’ve been having an issue over the past few weeks were I cannot update metadata for movies. I can update metadata for TV shows and music though.

I checked the com.plexapp.agents.imdb.log file and noticed these entries:

2017-05-11 17:46:03,563 (7f44fffff700) : DEBUG (networking:166) - Requesting ‘http://127.0.0.1:32400/library/metadata/575566/tree’
2017-05-11 17:46:03,572 (7f44fffff700) : DEBUG (networking:166) - Requesting ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fconfiguration’
2017-05-11 17:46:18,593 (7f44fffff700) : ERROR (networking:219) - Error opening URL ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fconfiguration’
2017-05-11 17:46:18,593 (7f44fffff700) : INFO (init:1454) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fconfiguration
2017-05-11 17:46:18,597 (7f44fffff700) : DEBUG (networking:166) - Requesting ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Den’
2017-05-11 17:46:33,616 (7f44fffff700) : ERROR (networking:219) - Error opening URL ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Den’
2017-05-11 17:46:33,616 (7f44fffff700) : INFO (init:1454) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Den
2017-05-11 17:46:33,621 (7f44fffff700) : DEBUG (networking:166) - Requesting ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D’
2017-05-11 17:46:48,642 (7f44fffff700) : ERROR (networking:219) - Error opening URL ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D’
2017-05-11 17:46:48,643 (7f44fffff700) : INFO (init:1454) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D
2017-05-11 17:46:48,648 (7f44fffff700) : DEBUG (networking:166) - Requesting ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%2Fimages’
2017-05-11 17:47:03,678 (7f44fffff700) : ERROR (networking:219) - Error opening URL ‘http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%2Fimages’
2017-05-11 17:47:03,678 (7f44fffff700) : INFO (init:1454) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0480461%2Fimages
2017-05-11 17:47:03,679 (7f44fffff700) : CRITICAL (agentkit:1078) - Exception in the update function of agent named ‘Plex Movie’, called with guid ‘com.plexapp.agents.imdb://tt0480461?lang=en’ (most recent call last):
File “/usr/lib/plexmediaserver/Resources/Plug-ins-4b377d295/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/api/agentkit.py”, line 1076, in _update
agent.update(obj, media, lang, **kwargs)
File “/usr/lib/plexmediaserver/Resources/Plug-ins-4b377d295/PlexMovie.bundle/Contents/Code/init.py”, line 562, in update
get_tmdb_metadata(guid, lang, metadata)
File “/usr/lib/plexmediaserver/Resources/Plug-ins-4b377d295/PlexMovie.bundle/Contents/Code/init.py”, line 1103, in get_tmdb_metadata
return tmdb_dict_to_movie_metadata_obj(metadata_dict, metadata)
File “/usr/lib/plexmediaserver/Resources/Plug-ins-4b377d295/PlexMovie.bundle/Contents/Code/init.py”, line 1152, in tmdb_dict_to_movie_metadata_obj
try: attr_obj[k] = Proxy.Preview(HTTP.Request(v[0]).content)
TypeError: argument of type ‘NoneType’ is not iterable

Any help would be appreciated.

Thanks!

2

Would you please recreate this for a single item (attempt to pull metadata), and then gather the complete log file set (Settings - Server - Help - Download Logs) and attach here with your next post. I’ll take a look at them and see what’s happening. Clearly there is something in the network configuration it’s not liking. This should be shown in the main PMS log file

3

Here are the logs after attempting to update the metadata for one movie.

Thanks!

4

Thank you for the logs.

Everything in your logs is pointing to network timeouts as the primary problem. There is a secondary issue which is also easily corrected. There are other errors however these appear to be cascaded off the primary. Those are:

  1. Fragmented database . (you’ve added, moved, or removed a lot of new media recently and the butler hasn’t had time to optimize (defragment) the Database.
  2. Networking timeouts (error 28) between Plex’s components occur when one is waiting to get data for another from the database. The initial requester times out waiting for the reply (error 28).
  3. Error 52 is the first indicator of a real network configuration issue. It may still be secondary but should be checked.

Log excerpt for 1 and 2 above

May 08, 2017 21:23:17.805 [0x7f9705bfe700] WARN - SLOW QUERY: It took 260.000000 ms to retrieve 50 items.
May 08, 2017 21:23:22.056 [0x7f9708fff700] ERROR - Error issuing curl_easy_perform(handle): 28
May 08, 2017 21:23:23.041 [0x7f9710bfd700] ERROR - Error issuing curl_easy_perform(handle): 28
May 08, 2017 21:23:38.158 [0x7f970ebf9700] ERROR - Error issuing curl_easy_perform(handle): 28

Log excerpt for #3 above:

May 08, 2017 21:20:09.059 [0x7f9711bff700] ERROR - Error issuing curl_easy_perform(handle): 28
May 08, 2017 21:20:24.096 [0x7f9708fff700] ERROR - Error issuing curl_easy_perform(handle): 28
May 08, 2017 21:20:31.085 [0x7f97113fe700] ERROR - Error issuing curl_easy_perform(handle): 52
May 08, 2017 21:20:31.085 [0x7f97113fe700] WARN - HTTP error requesting GET http://127.0.0.1:35822/:/plugins/com.plexapp.agents.imdb/messaging/function/X0FnZW50S2l0OlVwZGF0ZU1ldGFkYXRh/Y2VyZWFsMQoxCmxpc3QKMApyMAo_

This said, I recommend the following first actions steps:

  1. Hover the mouse in your Libraries section to expose the ellipsis. Click it and then click “Optmize Database”. This will defragment the DB.
  2. Double check your network settings (just to be sure). Make certain the MTU value is 1500 or smaller. Anything larger indicates Jumbo Frames and will cause a profound network slowdown.
  3. After optimizing the database, PMS should be restarted so it comes up cleanly
  4. If you’ve changed any network settings as well, just restart Linux.
5

I optimized the database and restart the plex service but was still having the issue. The mtu was set to 1500.

What fixed it for me was disabling ipv6. After disabling ipv6, I immediately reran the metadata check without restarting plex and it downloaded the metadata.

Thanks!

6

Bravo. That was the next step. I wanted you back to a decent start point first.
Some ISPs handle V6->V4 translation, most don’t.
Now you know