Unable to perform update to FreeNAS 9.3

[Sleepy D]

Not sure if I posted in the right group or not. Have been unable to update my frenas box. I recieve the following errors when checking for updates:

Apr 7 21:54:54 freenas ntpd_initres[7661]: host name not found: 2.freebsd.pool.ntp.org
Apr 7 22:11:56 freenas ntpd_initres[7661]: host name not found: 0.freebsd.pool.ntp.org
Apr 7 22:12:56 freenas ntpd_initres[7661]: host name not found: 1.freebsd.pool.ntp.org
Apr 7 22:13:56 freenas ntpd_initres[7661]: host name not found: 2.freebsd.pool.ntp.org
Apr 7 22:15:51 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:15:56 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:16:51 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:16:56 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/FreeNAS-9.3-STABLE/LATEST: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:22:34 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:23:34 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:30:58 freenas ntpd_initres[7661]: host name not found: 0.freebsd.pool.ntp.org
Apr 7 22:31:58 freenas ntpd_initres[7661]: host name not found: 1.freebsd.pool.ntp.org
Apr 7 22:32:58 freenas ntpd_initres[7661]: host name not found: 2.freebsd.pool.ntp.org
Apr 7 22:36:01 freenas notifier: Setting hostname: freenas.davelan.net.
Apr 7 22:37:13 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:37:36 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:38:13 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Apr 7 22:38:36 freenas manage.py: [freenasOS.Configuration:597] Unable to load http://update.freenas.org/FreeNAS/FreeNAS-9.3-STABLE/LATEST: <urlopen error [Errno 8] hostname nor servname provided, or not known>

here is my system Information:

Hostname freenas.davelan.net
Build FreeNAS-9.3-STABLE-201512121950
Platform Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
Memory 16276MB
System Time Thu Apr 07 23:46:28 CDT 2016
Uptime 11:46PM up 48 days, 13:07, 0 users
Load Average 0.00, 0.00, 0.00

Not sure what to try or if anything else would need tobe posted to help resolve. Thank You

 

[dlavigne]

Sounds like a networking error. Do you have a DNS server set in Network -> Global Configuration? Are you able to ping a domain name such as google.com from Shell?

 

[Sleepy D]

Sorry for taking so long to respond, I changed the host name before creating this post as my host name had been changed to freenas.10.0.1.1. I changed it and did not think of the DNS server settings. I checked them and it was set to 10.0.1.1, which is incorrect. I changed to my local DNS server which resides on my firewall, a PFsense box. Now able to update. But this created another issue that when I attempted to update to 9.10 I received a certificate error and was unable to log into FreeNAS via HTTPS. I reverted back to previous 9.3 config and all appears well. I will have to investigate this issue a little further and create a new thread as it involves an issue with updating. Thanks for your assistance.

 

[dlavigne]

IIRC, the HTTPS/certificate thing should be fixed in the next 9.10 SU.

 

[Sleepy D]

May I ask when that may be as to plan on attempting update again?

 

[dlavigne]

One is scheduled for today but sometimes they're a bit late. It'll show up in http://download.freenas.org/9.10/STABLE/ after it's released.

 

[Sleepy D]

I attempted to perform an update to 9.3 Stable to 9.10 Stable with the update release on 14-Apr-2016 and 18-Apr-2016 and still receive the IIRC, the HTTPS/certificate errors.

Could this be the same as the https://bugs.freenas.org/issues/14800 issue?

 

[dlavigne]

Does a fresh install (on another stick) of the latest 9.10 version fix it? Make a backup of your config first.

 

[Sleepy D]

Does a fresh install (on another stick) of the latest 9.10 version fix it? Make a backup of your config first.

I have not tried, as I am afraid of loosing the 5 TB of data stored on it. But will try

 

[dlavigne]

You won't. This is the reason why the OS is separate from the storage disks.

 

[Sleepy D]

You won't. This is the reason why the OS is separate from the storage disks.

I get the same error doing a fresh install. Plex appears to be working fine and my data appears there, but no HTTPS access

 

[dlavigne]

Just to clarify, it installs (or updates fine) but after rebooting you can no longer access the GUI?

 

[Sleepy D]

After the fresh install was completed, I was able to access the GUI via standard HTTP, I uploaded my backup config, which after reboot am being forced to to use HTTPS and can now now longer access via the GUI. I do have access using a keyboard and hooking up a VGA monitor to the box.

 

[danb35]

This post appears to have instructions that will resolve the issue.

 

[Sleepy D]

That appeared to resolve my issue with gaining the GUI back. Will have to work on building a new CA and cert. Thank you all.