Update server could not be reached

Status
Not open for further replies.

skylinegtr

Cadet
Joined
Jun 10, 2013
Messages
8
After updating 9.3 FreeNAS-9.3-STABLE-201412312006, the "check now" has problem "update sever could not be reached."
Does anyone know this issue?


<urlopen error [Errno 8] hostname nor servname provided, or not known>
Jan 5 19:02:40 nas manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Jan 5 19:02:41 nas manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Jan 5 19:02:41 nas manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/FreeNAS-9.3-STABLE/LATEST: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Jan 5 19:05:10 nas manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Jan 5 19:05:10 nas manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/FreeNAS-9.3-STABLE/LATEST: <urlopen error [Errno 8] hostname nor servname provided, or not known>
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
Yeah, it means that the update server could not be reached.

If you go to the CLI, the command "host update.freenas.org" will fail. If you want updates to be available, the NAS must be able to resolve names on the Internet and also actually be able to reach the Internet. You need to ascertain how your networking is broken and fix it.
 

jlpellet

Patron
Joined
Mar 21, 2012
Messages
286
A prior problem was that the default network interface was not created. In that case, in the GUI, open Network > Interfaces > re0 and ensure DHCP is checked. If re0 does not exist, add it with defaults, esuring DHCP is checked then reboot. If re0 exists and your box can see IP's but not names, as a temporary work around, you can add to lmhosts. Hope this helps.
 

skylinegtr

Cadet
Joined
Jun 10, 2013
Messages
8
A prior problem was that the default network interface was not created. In that case, in the GUI, open Network > Interfaces > re0 and ensure DHCP is checked. If re0 does not exist, add it with defaults, esuring DHCP is checked then reboot. If re0 exists and your box can see IP's but not names, as a temporary work around, you can add to lmhosts. Hope this helps.


Thanks~ it's work~
I remember several days ago, I used DHCP but rsync have problem~ so i give IPv4, then update has problem.
 

anttech

Dabbler
Joined
Dec 30, 2014
Messages
11
I just tried to create a link aggregation but then this issue reappeared any help at all?
 

vonhawkins

Cadet
Joined
Mar 26, 2015
Messages
4
I'm having the same problem. From the freenas box I can resolve names and ping the rest of the internet.
host update.freenas.org shows the IP 64.71.187.3, and that its an alias for beta-update.freenas.org
Ping update.freenas.org shows the IP but returns no reply.

Other boxes (windows) on the same network show similar results. The internet is fully available. update.freenas.org is resolvable but not available.
A browser attempt at the address resolves to update-stats. It appears updates are working for a lot of other folks.

Should we expect ping replies from update.freenas.org?

--thanks,
Von
 

vonhawkins

Cadet
Joined
Mar 26, 2015
Messages
4
I forgot to add:
FreeNAS-9.3-STABLE-201503200528

Installed a few days ago. Just now getting to the setup parts.
 

vonhawkins

Cadet
Joined
Mar 26, 2015
Messages
4
Well that blows my whole "See, it's conclusively broke" argument.
What should I expect it to answer on? port#, protocol, etc? I'm not familiar with freebsd package managers at all yet. Yum just conveniently works on ftp and http, so it's easy to check the repos for basic availability.

Given that it's resolving, what should I check next?
 

Barry

Dabbler
Joined
Dec 23, 2013
Messages
25
Hi, I'm also seeing the "Update server could not be reached" message in the web interface, but on the console, I see SSL errors regarding the update server(s):

upload_2016-6-22_17-5-36.png


This happens with 9.3 and also when trying to switch to the 9.10 train.

Barry
 

meku

Dabbler
Joined
May 4, 2014
Messages
34

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,466

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478

JoshDW19

Community Hall of Fame
Joined
May 16, 2016
Messages
1,077
We're aware of the issue and we're on it! I'll try to get you an update as soon as we find out something.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
This issue is fixed. I'll lock this thread.

Thanks!
 
Status
Not open for further replies.
Top