SOLVED Host name not found

Status
Not open for further replies.

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
so I started getting these errors:

Mar 17 19:48:02 freenas ntpd_initres[4041]: host name not found: 0.freebsd.pool.ntp.org
Mar 17 19:49:02 freenas ntpd_initres[4041]: host name not found: 1.freebsd.pool.ntp.org
Mar 17 19:50:02 freenas ntpd_initres[4041]: host name not found: 2.freebsd.pool.ntp.org

and also when I click on the plugins tab nothing loads.
it says " Unexpected token '<' "

I am new to freeNAS and did a Factory Restore not knowing that it would erase everything. so now all my plug ins are gone and I can't reinstall them.

I'm not sure what caused this, my FreeNAS was working fine, I just did a mother board swap and then I noticed this error and I was trying to get it to go away.

I have the Domain set to my routers IP and the IPV4 default gateway is also set to the same IP along with the Nameserver 1.

The system won't even sent the test email now. give me error Number 8
Mar 17 20:01:06 freenas manage.py: [common.system:210] Failed to send email: [Errno 8] hostname nor servname provided, or not known

clicked on the Update tab to see if it would connect but its not.

Mar 17 20:15:38 freenas manage.py: [freenasOS.Configuration:615] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:15:43 freenas manage.py: [freenasOS.Configuration:615] Unable to load http://update.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:16:10 freenas ntpd_initres[4041]: host name not found: 1.freebsd.pool.ntp.org
Mar 17 20:16:38 freenas manage.py: [freenasOS.Configuration:615] Unable to load http://update-master.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:16:38 freenas manage.py: [freenasOS.Configuration:629] Unable to load ['http://update.freenas.org/FreeNAS/trains.txt', 'http://update-master.freenas.org/FreeNAS/trains.txt']: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:16:43 freenas manage.py: [freenasOS.Configuration:615] Unable to load http://update-master.freenas.org/FreeNAS/trains.txt: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:16:43 freenas manage.py: [freenasOS.Configuration:629] Unable to load ['http://update.freenas.org/FreeNAS/trains.txt', 'http://update-master.freenas.org/FreeNAS/trains.txt']: <urlopen error [Errno 8] hostname nor servname provided, or not known>
Mar 17 20:17:10 freenas ntpd_initres[4041]: host name not found: 2.freebsd.pool.ntp.org
 
Last edited:

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
Either your DNS servers or default gateway is incorrect in your configuration.
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
I'm not sure what caused this, my FreeNAS was working fine, I just did a mother board swap and then I noticed this error and I was trying to get it to go away.

I have the Domain set to my routers IP and the IPV4 default gateway is also set to the same IP along with the Nameserver 1.
If you did a MotherBoard swap and are using the built-in NIC(s); you may have to reconfigure the networking... What MotherBoard did you use?
 

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
I have a asrock rack C2550D4I and it had an issue with one of the marvel SATA controllers. So I exchanged the board for a new one, exact same model.
I've tried removing the old information and re-entering what I had.
And like I said the default gateway and domain nameserver is set to the routers IP of 192.168.0.1
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
And like I said the default gateway and domain nameserver is set to the routers IP of 192.168.0.1
Assuming you set that under [Network] - [Global Configuration]?

Are you using DHCP or a Static?
Are you running LAGG or just a single NIC?
Are you able to access it via the GUI or does it show an IP in the Console?
 

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
Assuming you set that under [Network] - [Global Configuration]?

Are you using DHCP or a Static?
Are you running LAGG or just a single NIC?
Are you able to access it via the GUI or does it show an IP in the Console?
Yes I set that under [Network] - [Global Configuration]
I have a static address configured on the NAS
A single connection to the onboard NIC
I am able to access it via the GUI from my iMac
And all my jails are running and accessible using their individual IP's
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977

bernieTB

Dabbler
Joined
Mar 6, 2016
Messages
19
You could try by adding some 'nameservers' under Network - Global Configuration. I have the Google DNS in there: 8.8.8.8 and 8.8.4.4
 

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
Hmm... Something is amiss...

Are your jails able to get to the internet?
Are you using the correct NetMask?

Sorry for the machine gun questions; multi-tasking right now...
So I just checked and it looks like all jails can access the internet just fine.
and here is a screen shot of the [Network] [Interfaces] I have setup
Screen Shot 2016-03-18 at 3.45.34 PM.png


and here is the [Network] [Global Configuration]
Screen Shot 2016-03-18 at 3.46.01 PM.png


Please describe how you did this.
I did this in the Network Interfaces area.
 

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
Well I may have figure this out... I forgot that I went into my router settings and bound the IP I had set up in the FreeNAS, well with the new mother board I'm assuming the FreeNAS now has a different MAC address and may have been causing the conflict. Fingers crossed, hope un-binding the old MAC address from the IP I'm using fixes the problem.
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
I forgot that I went into my router settings and bound the IP I had set up in the FreeNAS, well with the new mother board I'm assuming the FreeNAS now has a different MAC address and may have been causing the conflict
That sounds like the issue. Just bind it to the new MAC.
 

Amsoil_Jim

Contributor
Joined
Feb 22, 2016
Messages
175
wow, I feel like and idiot. all fixed.
 
Status
Not open for further replies.
Top