‘Time out error’

[imzy82]

I actually ran 'opkg update' from putty and then did a full reboot.
Don't know if that made a difference

I did exactly that, not made any difference.

 

[imzy82]

Plugins

 

[Manno]

Happend to me yesterday, updating the software.
There has been a 'Timeouterror' please try again later. If the this issue persists
Please check openvix.co.uk or world-of-satellite.com

VU+ Zero 4K Image 6.8.009

 

[birdman]

Following from log shows only response and ping on Wlan3

11:07:54.5376 [About] ifreq:{'ifname': 'eth0', 'addr': '192.168.1.60', 'brdaddr': '192.168.1.255', 'hwaddr': '00:17:9A:25:42:9E', 'netmask': '255.255.255.0'}
11:07:54.5473 [About] getIfConfig Ex: [Errno 19] No such device
11:07:54.5481 [About] ifreq:{'ifname': 'eth1'}
11:07:54.5567 [About] getIfConfig Ex: [Errno 19] No such device
11:07:54.5574 [About] ifreq:{'ifname': 'ra0'}
11:07:54.5664 [About] getIfConfig Ex: [Errno 19] No such device
11:07:54.5672 [About] ifreq:{'ifname': 'wlan0'}
11:07:54.5762 [About] getIfConfig Ex: [Errno 19] No such device
11:07:54.5770 [About] ifreq:{'ifname': 'wlan3'}
...
11:07:54.6929 [Console] finished: /usr/sbin/ethtool
11:07:54.6949 [Console] command: ('/bin/ping', '/bin/ping', '-c', '1', 'www.microsoft.com')
11:07:54.6958 [eConsoleAppContainer] Starting /bin/ping
11:07:54.7015 [Console] command: ('/bin/ping', '/bin/ping', '-c', '1', 'www.google.com')
11:07:54.7025 [eConsoleAppContainer] Starting /bin/ping
11:07:54.7166 [Console] finished: ('/bin/ping', '/bin/ping', '-c', '1', 'www.google.com')@0xaf3b1c10
11:07:54.7195 [Console] finished: /bin/ping

About.py prints the "[About] getIfConfig Ex:" line before the "[About] ifreq" line for an interface.

So the only working network interface found was etrh0.

 

[ACWhitehouse]

Happend to me yesterday, updating the software.
There has been a 'Timeouterror' please try again later. If the this issue persists
Please check openvix.co.uk or world-of-satellite.com

VU+ Zero 4K Image 6.8.009

Same on mine SF8008 6.8.009

 

[kingy]

I did the reboot still comes up with that message. So it’s just not me then.

I also have the same problem and tried the various fixes but the problem persists. I am using 6.8.09 and it was working OK the problem arose a few day’s ago days ago, I am considering rolling back to previous image.

 

[imzy82]

The 6.9.001 has been released, however still the same issue ‘time out error’

 

[imzy82]

UPDATE, working now after opkg update via putty.

 

[Huevos]

# from onlineUpdateCheck.py

                if SystemInfo["imagetype"] == "release" and officialReleaseFeedsUri in SystemInfo["feedsurl"]:  # we know the network is good now so only do this check on release images where the release domain applies
                    try:
                        print("[OnlineUpdateCheck][getFeedStatus] checking feeds state")
                        req = Request("http://openvix.co.uk/TrafficLightState.php")
                        d = urlopen(req, timeout=3)
                        trafficLight = d.read().decode()
                        if trafficLight == "stable":
                            status = 0
                        print("trafficLight", trafficLight)
                    except Exception as err:
                        print("[OnlineUpdateCheck][getFeedStatus] ERROR:", err)
                        if hasattr(err, "code"):
                            trafficLight = err.code
                        else:
                            trafficLight = type(err).__name__

In particular:

                        req = Request("http://openvix.co.uk/TrafficLightState.php")
                        d = urlopen(req, timeout=3)

The timeout occurs there. Running that URL in a web browser seems slow so the timeout is reached.

 

[kingy]

UPDATE, working now after opkg update via putty.

Yes everything working on 6.9.001 just a reboot after installing 6.9.001

 

[Huevos]

I think it is a network issue.

 

[imzy82]

I think it is a network issue.

I thought the same but it’s not.

 

[Manno]

It's working again...

 

[Sicilian]

Any one having issues please to a tracert from a PC.

Open a CMD prompt:

tracert www.openvix.co.uk

Then post the output.

 

[Willo3092]

I haven't had the problem since I posted, but this is my tracert output:

Tracing route to www.openvix.co.uk [176.31.181.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 7 ms 10.53.37.113
3 8 ms 10 ms 11 ms nott-core-2a-ae71-650.network.virginmedia.net [80.255.196.204]
4 * * * Request timed out.
5 * * * Request timed out.
6 14 ms 15 ms 14 ms 80.255.204.81
7 18 ms 17 ms 15 ms 80.255.204.101
8 24 ms 26 ms 24 ms 176.52.248.130
9 26 ms 25 ms 23 ms par-pa3-pb1-nc5.fr.eu [54.36.50.220]
10 * * * Request timed out.
11 * * * Request timed out.
12 26 ms 27 ms 25 ms par-th2-sbb1-nc5.fr.eu [54.36.50.226]
13 28 ms 27 ms 27 ms be102.lil1-rbx8-sbb1-nc5.fr.eu [54.36.50.241]
14 30 ms 27 ms 26 ms 37.59.16.20
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 29 ms 28 ms 24 ms ns3324542.ip-176-31-181.eu [176.31.181.161]

Trace complete.

 

[birdman]

Oddly, if I trace a traceroute (with -n) from mt et8000, my laptop and my router the laptop is considerably quicker to finish.
Even though it has to run through the router, which is running its traceroute at the same time.

They do all get there, but the et8000 and router can take an age.