Lately I’ve run into issues where items are added to my Plex library before relevant metadata is available at The TVDB. Since there is no way (that I can tell) to automatically refresh all metadata periodically, I have to manually trigger the refresh. But triggering it for a single item does not work. Once I click it, the status info pops up at the bottom of the screen, but no metadata appears after it finishes. However, if I refresh all metadata for my entire TV library, metadata will populate properly.
Obviously, I don’t want to have to refresh all metadata for my entire TV library every time I need get the metadata for a single episode. Anyone have suggestions? Right now it looks like my best option, short of manually copying/pasting the metadata, is write a simple cron script that’ll use the Plex command line to refresh all metadata while I’m sleeping.
When you refresh the entire library, we don’t cache that much, so it is very likely, the cache has removed the info for that new item by the time it gets to it so it has to gather new info.
That didn’t seem to work. Following the tip on that page, I deleted all of the caches, then restarted Plex Media Server. When I refreshed metadata, it definitely seemed to be doing something, but after a significantly-longer-than-normal wait, no new metadata was downloaded. I checked The TVDB manually, and it definitely has information there.
I verified that my TV library is set to use TheTVDB as its agent. I also checked the agent settings, and Shows > TheTVDB has “Local Media Assets” as the first priority, followed immediately by “TheTVDB”. So the agent shouldn’t be the issue either.
Logs attached. This time, I was trying to update metadata for the newest episode of Tosh.0. It also happens frequently with Last Week Tonight, though I don’t have an example of that at the moment. Please let me know if you need anything else.Plex Media Server Logs_2018-09-20_17-53-45.zip (2.7 MB)
According to your log, PMS gathered new data. It’s possible that TheTVDB hasn’t updated their info. What you see on their website does not always match the data that gets downloaded. There can be a delay. I’ve seen upto 2 weeks.
I should note that I noticed there was an update available while troubleshooting, so I am now running 1.13.7.5369. The logs I provided were downloaded after upgrading and retrying.
I see that the item was added, but something caused it to update 6 hours later. However, the time is much earlier than the time in the log I mentioned above. So the update didn’t seem to actually update the data. I’m not sure what is going on. I was able to gather the correct data so it’s definitely there. Your logs indicate it got data and updated the info appropriately, so I’m not sure where the problem is.
Earlier when I said to clear the cache, can you provide me a screenshot and show me what you deleted, just to make sure you did delete the right one.
Sure thing, see attached. I’m running FreeBSD (via FreeNAS), so it’s just a screenshot of the terminal. I then did “rm -r *” to delete all of them at once.
Sorry for not responding back earlier. I still don’t know of any reason for the issues you were having. We’ve had a few PMS updates since then. Are you still having this issue?
Please provide the entire log. 1 line isn’t going to tell us much.
Your PMS is pulling data from cached info, so it’s possible your cache is not updated. Please follow the steps I posted above about clearing the cache.
I still think something with your cache isn’t getting cleared properly. Can you try again and then check those directories to see that the files were actually removed? I’m not a linux person but I know there are permission issues so maybe the user you used for the terminal didn’t have the correct rights, so nothing got erased.
I have tried clearing the cache and it made no difference. After clearing the cache i added a new TV Series (Luther). Only partial metadata retrieved successfully… Some seasons are complete and some seasons are missing metadata for a few episodes. I’ll attach another log file when i can. From a quick glance the error message is the same as in the previous log file.
