I hate to say it, but there really is something wrong with your Internet connection to the Pi.
There is really very little to go on in your log but there are two clues that point towards internet connectivity problems:
-
Start-Date: 1970-01-01 00:06:49
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 -f -y dist-upgrade
Install: rbp2-armmem-osmc:armhf (1.0.0-8, automatic), eject:armhf (2.1.5+deb1+cvs20081104-13.1, automatic)
Upgrade: tzdata:armhf (2015c-1, 2015d-0+deb8u1), fuse:armhf (2.9.3-15+b1, 2.9.3-15+deb8u1), rbp-bootloader-osmc:armhf (1.0.3-0, 1.0.4-0), libfuse2:armhf (2.9.3-15+b1, 2.9.3-15+deb8u1), rbp2-mediacenter-osmc:armhf (14.2.0-15, 14.2.0-16), mediacenter-addon-osmc:armhf (2.9.95, 2.9.991), ntfs-3g:armhf (2014.2.15AR.2-1, 2014.2.15AR.2-1+deb8u2), rbp2-device-osmc:armhf (1.1.0, 1.2.0), diskmount-osmc:armhf (1.2.5, 1.2.9)
End-Date: 1970-01-01 00:10:54
At the time this update was run the date was 1970 - this is the default date when the Pi is turned on as it has no real time clock to keep the time when turned off. So we run an ntp client that automatically tries to set the time as soon as there is a network connection. The fact that the time was incorrect by the time you ran updates means that this ntp connection on UDP port 123 was not successful at all, so that’s your first evidence of partial network connectivity problems.
-
Jun 04 17:34:28 osmc http-time[262]: Unable to set time using HTTP query - no response received from servers.
In a recent update (I don’t recall exactly when or whether it was in before RC3) we added a new boot service called http-time - this is a backup method of setting the time in addition to ntp. We added this because a small percentage of people can’t use ntp because their router (or possibly ISP) blocks UDP packets with a source and destination port of 123, thus they would not get the time set on their system.
So this service attempts to perform a standard HTTP get request to www.google.com, www.apple.com and www.microsoft.com in that order until it gets a connection. You can see the script that does this here:
It’s a relatively straight forward script - it first waits (up to a maximum of 60 seconds) until connman reports that the internet connection is up (which connman itself determines based on contacting a specific server on the internet) and then attempts to make an HTTP query to those three servers in order until it gets a response, with a 4 second timeout for each server.
The entry in your log clearly shows that even though connman was able to connect to its own test server and thus establish that there was some internet connectivity, three different wget attempts to three different well known websites failed.
So I can’t see how it can be anything other than an internet connectivity problem. It’s not a complete lack of connectivity otherwise connman would have never reported that the connection was up, in which case the log would have said “No internet connection was available within 60 seconds, giving up.”.
But there is definitely a problem with your connectivity from everything that I can see, as that http-time script should be very reliable.
PS I would be interested to see what output you get from the following command on your Pi:
LANG=C wget --server-response --timeout=4 --max-redirect 0 --spider www.google.com
Here is what I get, and you can see the Date: field which the script is looking for:
osmc@rpi2:~$ wget --server-response --timeout=4 --max-redirect 0 --spider www.google.com
converted 'http://www.google.com' (ANSI_X3.4-1968) -> 'http://www.google.com' (UTF-8)
Spider mode enabled. Check if remote file exists.
--2015-06-05 09:54:12-- http://www.google.com/
Resolving www.google.com (www.google.com)... 216.239.32.20
Connecting to www.google.com (www.google.com)|216.239.32.20|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.0 302 Moved Temporarily
Cache-Control: private
Content-Type: text/html; charset=UTF-8
Location: http://www.google.co.uk/?gfe_rd=cr&ei=tGNxVYuwMIyCaMrlgcgC
Content-Length: 259
Date: Fri, 05 Jun 2015 08:54:12 GMT
Server: GFE/2.0
X-Cache: MISS from netpilot2.staloysius.local
Connection: keep-alive
Location: http://www.google.co.uk/?gfe_rd=cr&ei=tGNxVYuwMIyCaMrlgcgC [following]
converted 'http://www.google.co.uk/?gfe_rd=cr&ei=tGNxVYuwMIyCaMrlgcgC' (ANSI_X3.4-1968) -> 'http://www.google.co.uk/?gfe_rd=cr&ei=tGNxVYuwMIyCaMrlgcgC' (UTF-8)
0 redirections exceeded.
