Kodi Community Forum

Full Version: IMDB scraper - movies aren't getting poster images
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've recently been noticing that movie scrapes aren't always populating the movie poster images.  If I manually go into the movie info and force a refresh, it *will* grab the info.  I've tried switching over to the universal scraper but that didn't work either.  Included is a debug log of me switching back to the imdb scraper, and forcing a full re-scan.  Some movies have posters, many do not.  This seems to have started happening within the past two days.  
Running libreelec 9.0 on x86 hardware.

I'm trying to upload the logfile to paste.kodi.tv but all I get is a message saying 'something went wrong!' when trying to save it... is there another preferred place to upload a large (100MB) log file?
100MB is too big. That is a log with a couple million lines. I don't think any paste site will accept a paste that large.

Make sure you restart Kodi, (which creates a fresh log) then create the log which captures the problem.

Even as a zip upload I wouldn't look at it as it would just freeze my machine trying to load it.

Might be of help... https://forum.kodi.tv/showthread.php?tid...pid2665079
100MB *is* a fresh restart that re-creates the problem (scan my entire library)... not sure how to make it any smaller...

update: I've just blown away my entire library, hoping a clean scan will set things straight... not even a little.  Here's the really weird part: I have a source that has 4 different network locations... one of them (animated movies) has no problem getting all the posters (appears to populate the `c08` column in the MyVideos116.movie table), but all the other sources... nada.  Could it be I've hit some limit on the number of items kodi can handle somewhere?
7MB logfile has the same problem... ('something went wrong' in paste.kodi.tv).
The max file size is 1MB for Kodi Paste Site

(2019-02-22, 04:19)isamudaison Wrote: [ -> ]I have a source that has 4 different network locations
Instead of running a full Update Library, go to Videos>Files. Highlight a Source that has problem movies and then call up the Context Menu and select Scan to Library (or similar wording).

You will have to remove movies from the library first so they get re-scraped.

That should create a smaller log.
Boom, here we go: 
http://ix.io/1BIq

This looks suspect ... where is it getting the 'old' stuff, and how do I delete it?:
Quote:18:55:54.353 T:139987648333568 DEBUG: VideoInfoScanner: Skipping dir 'nfs://192.168.1.201/media/raid1/Anime/movie/Ghost in the Shell Collection/Ghost in the Shell (1995)/' due to no change (fasthash) 18:55:54.355 T:139987648333568 DEBUG: CAddonSettings[metadata.themoviedb.org]: loading setting definitions
18:55:54.355 T:139987648333568 DEBUG: CAddonSettings[metadata.themoviedb.org]: trying to load setting definitions from old format...
18:55:54.355 T:139987648333568 DEBUG: CAddonSettings[metadata.themoviedb.org]: loading setting values
(2019-02-22, 04:57)isamudaison Wrote: [ -> ]where is it getting the 'old' stuff, and how do I delete it?:
If you are referring to this... "trying to load setting definitions from old format...", then don't concern yourself with that. It is "normal" and expected. Doesn't affect anything, just some changes to v18 and not all add-ons have caught up with the changes yet.

In that log, which movie did you scrape and no artwork was loaded? I cannot see any movie being scraped.
All the movies that are under `/Anime/movie` were newly added just then.

edit:  maybe this one?  http://ix.io/1BIy
It's tough in libreelec because the paste logfile functionality only seems to work every other time.
You mean these ones for exmple...
18:55:54.215 T:139987648333568   DEBUG: VideoInfoScanner: Skipping dir 'nfs://192.168.1.201/media/raid1/Anime/movie/Appleseed (2004)/' due to no change (fasthash)

18:55:54.219 T:139987648333568 DEBUG: VideoInfoScanner: Skipping dir 'nfs://192.168.1.201/media/raid1/Anime/movie/Appleseed Alpha (2014)/' due to no change (fasthash)

18:55:54.223 T:139987648333568 DEBUG: VideoInfoScanner: Skipping dir 'nfs://192.168.1.201/media/raid1/Anime/movie/Appleseed Saga - Ex Machina (2007)/' due to no change (fasthash)

They don't look like they were added. Can you confirm they were added? Are you sure they weren't already in the library?
Yes, those movies are an example.  All of them get added, sans poster image (and I can confirm by looking at the sql table in my central mysql server).
Well, I am not understanding. The log states they have been skipped. So how are they being added to the library?

Skipping dir 'nfs://192.168.1.201/media/raid1/Anime/movie/Appleseed (2004)/' due to no change (fasthash)

I don't think you are removing them from the library. But you are using MySQL, so there is probably something else happening I am not familiar with. I don't use MySQL, only local databases.

You will have to wait for someone with more knowledge on the MySQL process to help.
Oh. My. Gawd.  Apparently my Emby install is generating .nfo files inside the media directories... and Kodi is reading those!  How do I stop Kodi from doing that?
Edit:  For anyone else seeing this, here's a log entry I found, showing the finding of an .nfo, and the subsequent insertion of empty data to the DB:
Quote:19:40:59.534 T:140130690004736   DEBUG: VideoInfoScanner: Found matching full NFO file: nfs://192.168.1.201/media/raid1/Anime/movie/Afro Samurai (2007)/Afro.Samurai.2007.bluray.720p.nfo
19:40:59.536 T:140130690004736   DEBUG: VideoInfoScanner: Adding new item to movies:nfs://192.168.1.201/media/raid1/Anime/movie/Afro Samurai (2007)/Afro.Samurai.2007.bluray.720p.mkv
19:40:59.537 T:140130690004736   DEBUG: Mysql Start transaction
19:40:59.541 T:140130690004736   DEBUG: Mysql execute: UPDATE files SET dateAdded='2019-02-21 19:40:59' WHERE idFile=51555
19:40:59.542 T:140130690004736   DEBUG: Mysql execute: insert into movie (idMovie, idFile) values (NULL, 51555)
19:40:59.543 T:140130690004736   DEBUG: Mysql execute: UPDATE files SET dateAdded='2008-05-08 08:58:16' WHERE idFile=51555
19:40:59.545 T:140130690004736   DEBUG: Mysql Start transaction
19:40:59.545 T:140130690004736   DEBUG: Mysql execute: DELETE FROM streamdetails WHERE idFile = 51555
19:40:59.546 T:140130690004736   DEBUG: Mysql execute: INSERT INTO streamdetails (idFile, iStreamType, strVideoCodec, fVideoAspect, iVideoWidth, iVideoHeight, iVideoDuration, strStereoMode, strVideoLanguage) VALUES (51555,0,'h264',16.000000,1280,720,6728,'','eng')
19:40:59.546 T:140130690004736   DEBUG: Mysql execute: INSERT INTO streamdetails (idFile, iStreamType, strAudioCodec, iAudioChannels, strAudioLanguage) VALUES (51555,1,'dts',6,'eng')
19:40:59.546 T:140130690004736   DEBUG: Mysql execute: update movie set c11=6728 where idFile=51555 and c11=''
19:40:59.547 T:140130690004736   DEBUG: Mysql execute: update episode set c09=6728 where idFile=51555 and c09=''
19:40:59.548 T:140130690004736   DEBUG: Mysql execute: update musicvideo set c04=6728 where idFile=51555 and c04=''
19:40:59.549 T:140130690004736   DEBUG: Mysql commit transaction
19:40:59.552 T:140130690004736   DEBUG: Mysql execute: INSERT INTO art(media_id, media_type, type, url) VALUES (24648, 'movie', 'thumb', '')
19:40:59.553 T:140130690004736   DEBUG: This query part contains a like, we will double backslash in the next field: 'WHERE movie.premiered LIKE '
19:40:59.554 T:140130690004736   DEBUG: Mysql execute: UPDATE movie SET c00='Afro.Samurai',c01='',c02='',c03='',c05='-1',c06='',c08='',c09='-1',c10='',c11='6720',c12='',c13='0',c14='',c15='',c16='',c17='',c18='',c19='',c20='',c21='',c22='nfs://192.168.1.201/media/raid1/Anime/movie/Afro Samurai (2007)/',c23='18104', idSet = NULL, userrating = NULL, premiered 
= '2007' where idMovie=24648
(2019-02-22, 06:06)isamudaison Wrote: [ -> ]How do I stop Kodi from doing that?
You can't. Local Information has priority over any other source of information. The only way to prevent it is to move/hide/delete the nfo files.
Those entries are not in the log you gave me. Did you run another log?
That was the log that libreelec *didn't* post up, I had to ssh into the box to see it... ironically the most difficult part about trouble-shooting this was getting the right logfile outta libre.