[mythtv-users] metadata chaos

[jam]

> On 1 Sep 2020, at 1:08 am, Roland Ernst <rcrernst at gmail.com> wrote:
> 
> 
> On Sun, Aug 30, 2020 at 10:51 AM Blue <jam at tigger.ws> wrote:
> Hi
> 
> After a resent scan a whole number of Movies with metadata had the metadata, both description and coverart disapear.
> 
> menu->i->Change Video Details->retrieve data winds for a while then says FAILED
> 
> menu->i->Change Video Details->reset details
> menu->i->Change Video Details->retrieve details does works
> 
> Some Movies eg Blue Planet II imediately populate the movie
> 
> others eg Bladerunner
> reset detail
> retrieve details
> 
> Do retrive data and art
> <selecting> does nothing except say something to the db. Art and description are blank
> retrieve (again) fails
> reset
> retrieve fetches the details again
> 
> others
> <selection> does nothing
> retrieve for another movie (may or maynot work
> First movie is populated
> 
> Can anybody cast light on what is happening?
> Running the graber by hand does get data and art,
> 
> Thanks
> James
> 
>  
> It is important to know that the movie grabber 'tmdb3.py'
> limits each action to 30 seconds.
> But MythTV internally limits a grabber session to 60 secs.
> Additionally, the tmdb3 grabber uses an internal cache.
> The cache is located at ' $HOME/.mythtv/cache/pytmdb3.cache'
> or defined by the 'MYTHCONFDIR' environment.
> That might explain your observation, that the second call
> from the terminal succeeds, if the calls are done by the
> same user on the same PC.
> 
> Please try the following steps:
> - delete the cache
> - from mythfrontend, run a single update/fetch command
>   that failed previously
> - delete the cache again
> - run the tmdb3 command logged by mythmetadatalookup
>   from the terminal again (as the same user)
> - post the output
> 
> If that fails as well, try to increase the timeout for tmdb3
> to 60 seconds. See
> https://forum.mythtv.org/viewtopic.php?f=36&t=3630
> how to change the timeout.
> 
> On the other hand, it is of interest, if the second call
> from the terminal returns *all* the content, or if it
> returns the truncated content from the cache, only.

Roland
Thanks so, so much is explained, but oh so little documentation exists

In fact, as per myth’s coding standatds, a 10 line explation would be so useful!
if you run the grabber within the frontend nothing is logged and mythmetadata is not run.
But your wise words will help troubleshoot. (run the frontend in a terminal to view the detail)
James