I have been receiving the error “unable to connect to remote server would you like to continue scanning” during library updates. When I click yes the scan continues, though I do get the same error 2-3 times in a row. I have checked my network shares and they all work fine. Any suggestions on what could be causing this?
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.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
-
enable debug logging at settings->system->logging
-
reboot the OSMC device twice(!)
-
reproduce the issue
-
upload the log set (all configs and logs!) either using the
Log Uploader
method within the My OSMC menu in the GUI or thessh
method invoking commandgrab-logs -A
-
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
Thank you for any help you can provide. I have linked the log. I usually get the error message three times in a row. Everytime I click yes and it finishes scanning. My library does seem to update. Just trying to get this annoying message to stop.
Again, thank you for any help. I truly appreciate it.
Which scraper(s) are you using? Is it the same for all sources?
For Movies I am using The Movie Database(TMDB Movie Scraper) version 5.2.5, For TV Shows I am using The TVDB, version 3.2.8.
The TMDB TV Show Scraper version 3.5.11 is also enabled for TV Shows but the content is set to the TVDB scraper on TV Shows.
Again, thank you for any help you can provide.
I’d recommend getting rid of TVDB, because it’s going to be a paid service from March.
I will give that a try
So I did change scrappers for both Movies and TV Shows. I changed TV to The Movie Data version 3,5.11 first and I still received the error message. I then changed the movie scrapper to the Universal Movie Scrapper and the error message stopped. So it seems the issue is The Movie Dstabase scrapper version 5.2.5.
It could be a temporary issue. If the issue persists after a day or so I’d consider posting on their forums or checking if others are experiencing the problem.
This is not related to your issue but you should set your UI resolution to 1080p 60hz as running it in 4K as you have it set now is problematic.
I also noticed this in your advancedsettings.xml
<cache>
<memorysize>0</memorysize>
<curlclienttimeout>45</curlclienttimeout>
</cache>
Setting memorysize to zero is problematic. If you want to return it to defaults replace that line with just…
<memorysize/>
and as for the timeout you put that in wrong. It won’t work inside cache tags and it should be…
<network>
<curlclienttimeout>45</curlclienttimeout>
</network>
I also spotted this error in the file…
<videoscanners>
<ignoreerrors>true</ignoreerrors>
</videoscanners>
should be a singular videoscanner such as
<videoscanner>
<ignoreerrors>true</ignoreerrors>
</videoscanner>
<nofliptimeout>0</nofliptimeout>
is not supported in Kodi anymore
Still probably not related but…
MYSQL: Connected to version 5.5.62
Current versions of Kodi seem to be less compatible with MySQL versions older than 5.7 then it once was. Upgrading to a newer version if possible would be a good idea.
CServiceAddonManager: starting script.xbmc.unpausejumpback
I forget the details but there exists issues with this add-on.
I’m not sure what’s up with the errors in scanning and I got crossed eyed before finding any of them. If you fix the errors I outlined above in your advancedsettings.xml file the message should get suppressed like you wanting though.
This morning I loaded the latest osmc update after refusing it for a few days. Then, every time I tried to Update Library I got the “Unable to connect to remote server” on the first film. I tried restarting everything, and tried waiting 12 hours, but it was a solid fault. Internet OK.
So I did the change above, and library updates are now working.
It may have been a coincidence. It was my first library update in 8 weeks.