I apologize if I’m overlooking something easy, but I’m brand new to this.
I just installed OSMC on my old Apple TV. Everything was pretty straightforward and I am running the default Kodi skin. But, I can’t complete the last step of scraping my movies and having them show up in the Movies section of the Kodi interface. I have an external drive that contains my movies and I created a path to the folder that contains the movies.
When I go to ‘Movies’ in the Kodi menu, it says my library is empty and to enter “Files” section to configure it. When I click on “Enter Files Section”, I see my folder that contains my movies and when I click on that, all my movies are there. When I try to update the library to get the artwork from TMDB, I get an error that says, “Couldn’t download information” - “Unable to connect to remove server. Would you like to continue searching”.
Any idea why these movies won’t scrap and also not show up in the move section of Kodi?
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Thank you for the help. I will try and get that soon.
20:13:17.945 T:2862562112 ERROR: CCurlFile::FillBuffer - Failed: Couldn’t resolve host name(6)
Check DNS.
Not sure what that means, but I’m connected wirelessly and my network status is “Connected”. I have a valid IP and Primary DNS addresses. What do I need to look for?
SSH into your ATV, and see if you can ping api.tmdb.org.
And before you ask:
Details regarding how to access the command line interface can be found here on our Wiki: Accessing the command line - General - OSMC
Here’s what I just got:
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Nov 21 21:20:45 2017 from 10.0.1.15
osmc@osmc:~$ ping api.tmdb.org
PING api.tmdb.org (104.16.60.155): 56 data bytes
64 bytes from 104.16.60.155: seq=0 ttl=57 time=356.568 ms
64 bytes from 104.16.60.155: seq=1 ttl=57 time=61.464 ms
64 bytes from 104.16.60.155: seq=2 ttl=57 time=463.158 ms
64 bytes from 104.16.60.155: seq=3 ttl=57 time=286.828 ms
64 bytes from 104.16.60.155: seq=4 ttl=57 time=45.784 ms
64 bytes from 104.16.60.155: seq=6 ttl=57 time=34.921 ms
64 bytes from 104.16.60.155: seq=7 ttl=57 time=82.543 ms
64 bytes from 104.16.60.155: seq=9 ttl=57 time=64.645 ms
64 bytes from 104.16.60.155: seq=10 ttl=57 time=190.163 ms
64 bytes from 104.16.60.155: seq=11 ttl=57 time=57.357 ms
64 bytes from 104.16.60.155: seq=12 ttl=57 time=28.444 ms
64 bytes from 104.16.60.155: seq=13 ttl=57 time=19.333 ms
64 bytes from 104.16.60.155: seq=14 ttl=57 time=57.375 ms
64 bytes from 104.16.60.155: seq=15 ttl=57 time=56.660 ms
64 bytes from 104.16.60.155: seq=16 ttl=57 time=31.928 ms
64 bytes from 104.16.60.155: seq=17 ttl=57 time=28.964 ms
64 bytes from 104.16.60.155: seq=18 ttl=57 time=35.641 ms
64 bytes from 104.16.60.155: seq=19 ttl=57 time=54.425 ms
64 bytes from 104.16.60.155: seq=20 ttl=57 time=15.192 ms
64 bytes from 104.16.60.155: seq=21 ttl=57 time=25.240 ms
64 bytes from 104.16.60.155: seq=22 ttl=57 time=16.834 ms
64 bytes from 104.16.60.155: seq=23 ttl=57 time=24.876 ms
64 bytes from 104.16.60.155: seq=24 ttl=57 time=17.869 ms
64 bytes from 104.16.60.155: seq=25 ttl=57 time=13.786 ms
64 bytes from 104.16.60.155: seq=26 ttl=57 time=24.616 ms
64 bytes from 104.16.60.155: seq=28 ttl=57 time=19.752 ms
64 bytes from 104.16.60.155: seq=29 ttl=57 time=13.516 ms
64 bytes from 104.16.60.155: seq=30 ttl=57 time=13.361 ms
64 bytes from 104.16.60.155: seq=31 ttl=57 time=25.061 ms
64 bytes from 104.16.60.155: seq=32 ttl=57 time=14.389 ms
64 bytes from 104.16.60.155: seq=33 ttl=57 time=17.221 ms
64 bytes from 104.16.60.155: seq=34 ttl=57 time=17.339 ms
64 bytes from 104.16.60.155: seq=36 ttl=57 time=49.827 ms
64 bytes from 104.16.60.155: seq=37 ttl=57 time=26.776 ms
64 bytes from 104.16.60.155: seq=38 ttl=57 time=18.031 ms
64 bytes from 104.16.60.155: seq=39 ttl=57 time=11.778 ms
64 bytes from 104.16.60.155: seq=40 ttl=57 time=47.625 ms
64 bytes from 104.16.60.155: seq=41 ttl=57 time=42.359 ms
64 bytes from 104.16.60.155: seq=43 ttl=57 time=56.718 ms
64 bytes from 104.16.60.155: seq=44 ttl=57 time=31.011 ms
64 bytes from 104.16.60.155: seq=45 ttl=57 time=54.489 ms
64 bytes from 104.16.60.155: seq=46 ttl=57 time=16.636 ms
64 bytes from 104.16.60.155: seq=47 ttl=57 time=18.543 ms
64 bytes from 104.16.60.155: seq=49 ttl=57 time=41.091 ms
64 bytes from 104.16.60.155: seq=50 ttl=57 time=16.049 ms
64 bytes from 104.16.60.155: seq=51 ttl=57 time=14.641 ms
64 bytes from 104.16.60.155: seq=52 ttl=57 time=27.167 ms
64 bytes from 104.16.60.155: seq=53 ttl=57 time=21.780 ms
^C
— api.tmdb.org ping statistics —
54 packets transmitted, 48 packets received, 11% packet loss
round-trip min/avg/max = 11.778/56.453/463.158 ms
Opps, I think I see the problem. the 401 error is Unauthorized. From that, I’d guess that the scraper is out of date, as TMDB changed their API recently. Unfortunately, I’m not sure how you can upgrade the scraper, as the ATV is no longer supported with OSMC.
Darn. Thanks to both of you for the help.
If you have another more up to data system with Kodi, you could always setup a shared MySQL library, and use the other system to do the scraping.
I’ve always found it more reliable to use an app like Tiny Media Manager or Media Elch (both free) to scrape movie metadata and save .info files and images/fanart in the respective movie folders. Then set Kodi to use local info only when importing to the library. This has the added advantage of making setting up a new Kodi device much quicker and you don’t lose all your metadata if your Kodi installation goes south for some reason.