SOLVED FreeNAS-11.0-U4 (54848d13b) GUI update to 11.1 - "Update server could not be reached"

Status
Not open for further replies.

VictorR

Contributor
Joined
Dec 9, 2015
Messages
143
It's most likely a brainfart on my part, I haven't touched this (or any) FreeNAS system in a long time, except to apply updates via the GUI
No settings have changed since March of 2016(when i had a similar problem).

In System>Update it is set to "Update Server: http://update.ixsystems.com/FreeNAS"
When I do a "Check Now", it returns "Update server could not be reached" (w/ output below)

Here's the network setup. Using OpenDNS servers for name resolving. The default gateway, 192.168.1.1 can be pinged from Shell.

fUocgt7cSPeUhUt-NuR7Bg.png


From a Shell, I can ping "update.ixsystems.com" and get responses.
However, "http://update.ixsystems.com/FreeNAS" returns "ping: cannot resolve update.ixsystems.com/FreeNAS/: Unknown host"
I can ping Google.com, Yahoo.com., etc. So, I don't think it's a DNS setting problem

I have tried switching DNS server to our ISP's (Frontier) 192.168.xxx.xxx DNS IP address, same results. Can ping the primary update address "update.ixsystems.com", but not the FreeNAS directory - "ping: cannot resolve update.ixsystems.com/FreeNAS: Unknown host"

So, either way, it can resolve the primary domain name. But, no sub-directories

I'm at a loss for what's going on here. The update feature has worked without problems several times over the last year
Any pointers in the right direction for solving this would be greatly appreciated

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>
 
Last edited:

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Have you tried a bit later? The CDN can be a little bit wonky at times.
 

VictorR

Contributor
Joined
Dec 9, 2015
Messages
143
It was a recurring DNS problem with Frontier Networks
 
Status
Not open for further replies.
Top