Update Server Not Found

[jlpellet]

I have 4 FreeNAS 9.3 servers sitting on a local network, since the last update, 3 of the 4 say they cannot find the update server, with the messages below in the log. 1 finds it without error. Rebooting made no difference. Build is FreeNAS-9.3-STABLE-201412300101.

Any ideas/suggestions?

Thanks!

Dec 30 06:49:05 fn0 manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt:
Dec 30 06:49:05 fn0 manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt:
Dec 30 06:49:06 fn0 manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/trains.txt:
Dec 30 06:49:06 fn0 manage.py: [freenasOS.Configuration:491] Unable to load http://update.freenas.org/FreeNAS/FreeNAS-9.3-STABLE/LATEST:

 

[dlavigne]

Anything different in the network config of the problematic boxes? Are they on a different subnet? Behind a different proxy/router?

 

[archerne]

I have 2 FreeNAS boxes that I just upgraded to FreeNAS-9.3-STABLE-201412300101 as well, and neither of them can find the update server after the update. The Current Trains dropdown is also blank.

 

[dlavigne]

In that case, please create a bug report at bugs.freenas.org and post the issue number here.

 

[archerne]

Issue #7334

 

[jlpellet]

Some additional info as follows.
1. All 4 servers are on same subnet/LAN/etc. Only difference is 1 that remains able to see update server is AMD CPU & MB & other 3 are i3's.

2. Systems w/ problem also failing ntp connection, as sample log below shows.

Dec 30 08:24:02 fn2 ntpd_initres[2087]: host name not found: 0.freebsd.pool.ntp.org
Dec 30 08:24:02 fn2 ntpd_initres[2087]: host name not found: 1.freebsd.pool.ntp.org
Dec 30 08:24:02 fn2 ntpd_initres[2087]: host name not found: 2.freebsd.pool.ntp.org
Dec 30 08:24:02 fn2 ntpd_initres[2087]: host name not found: nist.time.nosc.us

3. Tried reverting to FreeNAS-9.3-STABLE-201412240734 & problem gone. Deleted 1230 boot & reupdated without problem.

4. After reboot to 1230 update on 3 systems w/ problem, update error returned.

 

[jlpellet]

I tried the fix in bug report 7335 & it resolved the issue. Per that bug report, the 1230 update may not create a default network interface so no DNS. For the 3 servers with the issue, I added re0, named it re0, & checked the DHCP box then rebooted. At that point, everything worked. No idea why the update worked on the AMD system except it is a different NIC hardware.