<urlopen error timed out>

Status
Not open for further replies.

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
I have a problem where I can not connect to the update server. I haven't changed any settings either to my router or freenas (that I am aware of anyway) and looking through the docs everything seems to be correct (but obviously isn't) I can access the freenas control panel and the files without error.

The traceback is:-

Code:
Traceback (most recent call last):
File "/usr/local/www/freenasUI/../freenasUI/system/views.py", line 1448, in update_check
train=updateobj.get_train(),
File "/usr/local/www/freenasUI/../freenasUI/system/models.py", line 573, in get_train
trains = conf.AvailableTrains() or []
File "/usr/local/lib/freenasOS/Configuration.py", line 891, in AvailableTrains
fileref = self.TryGetNetworkFile(file=TRAIN_FILE, reason="FetchTrains")
File "/usr/local/lib/freenasOS/Configuration.py", line 670, in TryGetNetworkFile
raise url_exc
URLError: <urlopen error timed out>


Freenas 9.10.1-U4

TiA
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
Do you mean this?

screenshot_225.jpg


My router is on 192.168.0.1
 
D

dlavigne

Guest
Yes. Can you resolve a name (eg ping google.com? If not, try using 8.8.8.8 as the nameserver.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
Code:
[root@freenas ~]# ping google.com											   
PING google.com (213.105.64.217): 56 data bytes   
 
D

dlavigne

Guest
It's resolving. Is it also pinging? (your output is truncated after the resolution line)
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
Thats all I am getting, so I assume not

Changed nameserver to 8.8.8.8 and its still erroring when I check for updates

Code:
Traceback (most recent call last):
File "/usr/local/www/freenasUI/../freenasUI/system/views.py", line 1448, in update_check
train=updateobj.get_train(),
File "/usr/local/www/freenasUI/../freenasUI/system/models.py", line 573, in get_train
trains = conf.AvailableTrains() or []
File "/usr/local/lib/freenasOS/Configuration.py", line 952, in AvailableTrains
fileref = self.TryGetNetworkFile(file=TRAIN_FILE, reason="FetchTrains")
File "/usr/local/lib/freenasOS/Configuration.py", line 720, in TryGetNetworkFile
raise url_exc
URLError: <urlopen error [Errno 8] hostname nor servname provided, or not known>
 
D

dlavigne

Guest
If you're not getting ping feedback when using 8.8.8.8, check the settings on the router. Also, check for firewall settings on the router and the client operating system. Something is blocking packets.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
I turned off the router firewall, and there was no difference in the 'ping' results on either nameserver.

What other router settings need to be checked?

I will be away from the PC for the next couple of hours, so any apologies for any deley in getting back to you.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
UPDATE:-

I can ping correctly from the router it self

Code:
PING 172.217.23.14 (172.217.23.14): 64 data bytes
Reply from 172.217.23.14: Bytes 64 Time=18.257 ms
Reply from 172.217.23.14: Bytes 64 Time=19.113 ms
Reply from 172.217.23.14: Bytes 64 Time=21.102 ms
Reply from 172.217.23.14: Bytes 64 Time=19.072 ms
Reply from 172.217.23.14: Bytes 64 Time=20.458 ms
Reply from 172.217.23.14: Bytes 64 Time=21.591 ms
Reply from 172.217.23.14: Bytes 64 Time=19.053 ms
Reply from 172.217.23.14: Bytes 64 Time=18.944 ms
Reply from 172.217.23.14: Bytes 64 Time=20.505 ms
Reply from 172.217.23.14: Bytes 64 Time=20.391 ms

--- 172.217.23.14 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 18.257/19.848/21.591 ms


so something is wrong with the freenas settings, but I haven't a clue what or where.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
Looking around the control panel I have found other errors. eg, there are 'no discs' on the freenas

screenshot_226.jpg


but I can access the discs from the computer without any problem

screenshot_227.jpg


What the *beep* has happened?
 
S

sef

Guest
Looks like you are simply not routing. And with the other confusions, I'm curious how your system got broken.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
Now this is really weirder. I booted up the system this morning, having done nothing to any of the the settings since the screenshots above. The log in page asked me to update my password (never seen that before) and now I can view all of the discs in the freenas control panel and I am currently running the update.

Updated perfectly, I can check for updates without any error and see all of the discs.

I know I am loosing my memory, but freenas shouldn't :confused:

I have no idea why it stopped working (It had been like that for several weeks) and then suddenly started working, so I can give no advice if anyone else has a similar problem.
 

Mr Onion

Dabbler
Joined
Jul 16, 2016
Messages
27
... but now I can't access files on the freenas server, nor can I check/adjust the sharing settings. Reboot of the server makes no difference. I have also manually updated, with no difference noted.

sharing.jpg
 

averyfreeman

Contributor
Joined
Feb 8, 2015
Messages
164
I'm having a similar issue. I just upgraded from 11-U1 to 11-U2 when I was receiving a traceback error trying to update via the web GUI.

I noticed there was a bug fix for update errors like this in U1, so I just updated to 11-U2 (e417d8aa5) using the U2 ISO and now I'm receiving a different error trying to update using Web GUI "Check Now".

I usually have the FreeNAS server connected to a domain controller/DNS server, but have also tried updating from the GUI with DNS set to 8.8.8.8 (google DNS) and either way I get the same error:
Code:
Update server could not be reached

<urlopen error timed out>


Traceback
Traceback (most recent call last):
File "/usr/local/lib/python3.6/urllib/request.py", line 1318, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/usr/local/lib/python3.6/http/client.py", line 1239, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1285, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1234, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1026, in _send_output
self.send(msg)
File "/usr/local/lib/python3.6/http/client.py", line 964, in send
self.connect()
File "/usr/local/lib/python3.6/http/client.py", line 936, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/local/lib/python3.6/socket.py", line 722, in create_connection
raise err
File "/usr/local/lib/python3.6/socket.py", line 713, in create_connection
sock.connect(sa)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "./freenasUI/system/views.py", line 1424, in update_check
train=updateobj.get_train(),
File "./freenasUI/system/models.py", line 616, in get_train
trains = conf.AvailableTrains() or []
File "/usr/local/lib/freenasOS/Configuration.py", line 1064, in AvailableTrains
fileref = self.TryGetNetworkFile(file=TRAIN_FILE, reason="FetchTrains")
File "/usr/local/lib/freenasOS/Configuration.py", line 787, in TryGetNetworkFile
raise url_exc
File "/usr/local/lib/freenasOS/Configuration.py", line 761, in TryGetNetworkFile
furl = opener.open(req, timeout=30)
File "/usr/local/lib/python3.6/urllib/request.py", line 526, in open
response = self._open(req, data)
File "/usr/local/lib/python3.6/urllib/request.py", line 544, in _open
'_open', req)
File "/usr/local/lib/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.6/urllib/request.py", line 1346, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/local/lib/python3.6/urllib/request.py", line 1320, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error timed out>


Is there a problem with the FreeNAS update server, or is this yet another bug?

Thanks,
Avery
 
S

sef

Guest
When in doubt, run freenas-update -v check from the shell. If that fails, then you can try doing fetch http://update-master.ixsystems.com/FreeNAS/`manifest_util train`/LATEST and see how that does.

We had a problem, which was fixed a week or two ago, that resulted in the non-CDN server being the only one with the updates, and then it was timing out due to the load.
 

averyfreeman

Contributor
Joined
Feb 8, 2015
Messages
164
When in doubt, run freenas-update -v check from the shell. If that fails, then you can try doing fetch http://update-master.ixsystems.com/FreeNAS/`manifest_util train`/LATEST and see how that does.

Tried both these and both timed out -- the first one with the urlopen error timed out error and the 2nd one with "Operation timed out"

Tried both of these using local DNS and Google DNS.

Thanks for the recommendations though.
 
Joined
Jul 18, 2017
Messages
9
I'm having this problem too... webGUI check for updates causes the following error:

Code:
Update server could not be reached

<urlopen error timed out>


Traceback
Traceback (most recent call last):
File "/usr/local/lib/python3.6/urllib/request.py", line 1318, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/usr/local/lib/python3.6/http/client.py", line 1239, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1285, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1234, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.6/http/client.py", line 1026, in _send_output
self.send(msg)
File "/usr/local/lib/python3.6/http/client.py", line 964, in send
self.connect()
File "/usr/local/lib/python3.6/http/client.py", line 936, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/local/lib/python3.6/socket.py", line 722, in create_connection
raise err
File "/usr/local/lib/python3.6/socket.py", line 713, in create_connection
sock.connect(sa)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "./freenasUI/system/views.py", line 1424, in update_check
train=updateobj.get_train(),
File "./freenasUI/system/models.py", line 625, in get_train
trains = conf.AvailableTrains() or []
File "/usr/local/lib/freenasOS/Configuration.py", line 1064, in AvailableTrains
fileref = self.TryGetNetworkFile(file=TRAIN_FILE, reason="FetchTrains")
File "/usr/local/lib/freenasOS/Configuration.py", line 787, in TryGetNetworkFile
raise url_exc
File "/usr/local/lib/freenasOS/Configuration.py", line 761, in TryGetNetworkFile
furl = opener.open(req, timeout=30)
File "/usr/local/lib/python3.6/urllib/request.py", line 526, in open
response = self._open(req, data)
File "/usr/local/lib/python3.6/urllib/request.py", line 544, in _open
'_open', req)
File "/usr/local/lib/python3.6/urllib/request.py", line 504, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.6/urllib/request.py", line 1346, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/local/lib/python3.6/urllib/request.py", line 1320, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error timed out>



I tried upgrading from Freenas-11-U2 to Freenas-11-U3 via the cli command "freenas-update -v update" and then restarted and the update went smoothly. Still getting this problem. I don't seem to have problems with dns resolution from the CLI, but I can't figure out what the heck is causing this. Also can't view the available plugins via the webGUI, where I note this error:

Code:
September 22 18:44:23 freenas.local collectd[8054]: aggregation plugin: Unable to read the current rate of "freenas.local/cpu-2/cpu-system".
September 22 18:44:23 freenas.local collectd[8054]: utils_vl_lookup: The user object callback failed with status 2.


My gut says they're related, but I have no idea what the problem is. Any ideas?
 

averyfreeman

Contributor
Joined
Feb 8, 2015
Messages
164
I've been having all sorts of issues with U3, I wish I had stayed at U2. My guess is the developers are focusing all their resources on the new GUI in the 11.1 release... can't say I blame them. Hope this stuff gets more reliable along with it.
 
Status
Not open for further replies.
Top