NTP Server not Reached

Status
Not open for further replies.

msrhedges

Cadet
Joined
Jun 26, 2013
Messages
4
I have been using standard RAID 5 on my Dell 2950 III 16Gb RAM server for years without problem.

Recently I decided that I wanted to go the NAS route and move all my files over to ZFS and run my ESXi virtual machines on the NAS via ISCSI. Up to this point my file server was simply a virtualised machine backed up with Syncback to two remote Synology boxes. After looking at what was available I tested Nexenta both with CIFS and ISCSI. Nexenta was fairly easy to setup and I have had the box running for about three weeks now.

I have also decided to also try FreeNAS and have this running with the following configuration.
2950 III server with RAID 1 mirror two 32Gb SSD's on Dell 6i for FreeNAS in PCie x8 port and six 1Tb drives in ZFS RAIDz2 on a Dell 6ir controller in MPT mode. 16Gb RAM is availiable.

My issue it that I either don't understand the NTP model being used or I am missing some configuration. I have a Cisco switch acting as a NTP server for my network and have no problems with any other device or Nexenta getting time synchronisation from it. I cannot get FreeNAS to connect to it either by IPv4 address or by DNS name. In both cases I get "Server could not be reached. Check "Force" to continue regardless." in both cases I can ping the NTP server from the FreeNAS console...

[root@freenas ~]# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: icmp_seq=0 ttl=128 time=0.180 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=128 time=0.174 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=128 time=0.175 ms
^Z
[4]+ Stopped ping 10.0.0.2
[root@freenas ~]# ping 3550_ser_12t.the######.com
PING 3550_ser_12t.the######.com (10.0.0.92): 56 data bytes
64 bytes from 10.0.0.92: icmp_seq=0 ttl=255 time=0.572 ms
64 bytes from 10.0.0.92: icmp_seq=1 ttl=255 time=0.579 ms
^Z
[5]+ Stopped ping 3550_ser_12t.the######.com

### domain name obscured..


I get the same message if I try to connect to an external time server by IPv4 address.

I have removed all of the pre-assigned NTP servers and left 10.0.0.92 and 3550_ser_12t. As below...
Running cat /etc/ntp.conf from the freenas console gives me the configuration that I expect.

[root@freenas ~]# cat /etc/ntp.conf
server 10.0.0.92 iburst maxpoll 10 minpoll 6
server 3550_ser_12t.the-hedges.com iburst maxpoll 10 minpoll 6
# XXX: this doesn't work as documented
#restrict default ignore
restrict 127.0.0.1
restrict -6 ::1

Running ntp -q results in what looks like a working connection. I am very new to freeBSD so confess to being a NEWB this error of Server could not be reached. Check "Force" to continue regardless threw me for quite a while.

[root@freenas ~]# ntpq -p

remote refid st t when poll reach delay offset jitter
==============================================================================

*3550_ser_12t.th 130.236.254.17 2 u 3 64 377 0.682 0.135 0.063
[root@freenas ~]#

runnning ntpdate shows the socket in use I don't know what to expect here.

[root@freenas ~]# ntpdate 3550_ser_12t.the-hedges.com
26 Jun 16:33:55 ntpdate[8153]: the NTP socket is in use, exiting
[root@freenas ~]#

I also noted that under the CIFS connection that Time Server for Domain was checked I have unchecked this as I don't want the FreeNAS system acting as my main time server. CIFS is in workgroup mode for now.

Could someone please update me on what is happening with regard to server could not being reached. I had to force it but had no idea at this stage that it was working. It was only after running shell commands that I realised all was probably OK. It also looks to me that it would not work at all if using a straight IPv4 address. Note I have a local DNS server with A records for key equipment including the tome server switch.

Thank you.
 

msrhedges

Cadet
Joined
Jun 26, 2013
Messages
4
Thank you for replying.

ntpdate -d says no servers can be used but ntpq -p shows that the system appears to be connected to my local ntp server.

Running ntpdate -d results in...

[root@freenas ~]# ntpdate -d
27 Jun 23:01:44 ntpdate[3139]: ntpdate 4.2.4p5-a (1)
27 Jun 23:01:44 ntpdate[3139]: no servers can be used, exiting
[root@freenas ~]#

ntpq -p results in..

[root@freenas ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
3550_ser_12t.th 81.94.123.17 2 u 32 64 77 0.697 1132.94 7.090
[root@freenas ~]#
 
D

dlavigne

Guest
The server is definitely unreachable. This is usually due to an invalid hostname or DNS not working. Starting with plain reachability, can you ping the NTP server's IP address from the FreeNAS system?
 

msrhedges

Cadet
Joined
Jun 26, 2013
Messages
4
From the shell console I can ping the ntp server by IP and by name..I can also ping bbc.co.uk a remote site.

I can also ping the freenas server from the NTP server using IP address and name.

It is interesting that the NTP status ref of 199.165.76.11 is the same for both the NTP server and the freenas server. See end of post.

My DNS server is 10.0.0.1.
freenas is 10.0.0.60
NTP server is 10.0.0.92

[root@freenas ~]# ping 10.0.0.92
PING 10.0.0.92 (10.0.0.92): 56 data bytes
64 bytes from 10.0.0.92: icmp_seq=0 ttl=255 time=0.562 ms
64 bytes from 10.0.0.92: icmp_seq=1 ttl=255 time=0.558 ms
64 bytes from 10.0.0.92: icmp_seq=2 ttl=255 time=0.559 ms
^C
--- 10.0.0.92 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.558/0.560/0.562/0.002 ms


[root@freenas ~]# ping 3550_ser_12t
PING 3550_ser_12t.#########.com (10.0.0.92): 56 data bytes
64 bytes from 10.0.0.92: icmp_seq=0 ttl=255 time=0.583 ms
64 bytes from 10.0.0.92: icmp_seq=1 ttl=255 time=0.555 ms
^C
--- 3550_ser_12t.##########.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.555/0.569/0.583/0.014 ms
[root@freenas ~]#

[root@freenas ~]# ping bbc.co.uk
PING bbc.co.uk (212.58.253.67): 56 data bytes
64 bytes from 212.58.253.67: icmp_seq=0 ttl=119 time=21.092 ms
64 bytes from 212.58.253.67: icmp_seq=1 ttl=119 time=19.598 ms
64 bytes from 212.58.253.67: icmp_seq=2 ttl=119 time=19.004 ms
^C
--- bbc.co.uk ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 19.004/19.898/21.092/0.878 ms
[root@freenas ~]#

FROM NTP SERVER
-------------------------

3550_SER_12T#ping freenas
Translating "freenas"...domain server (10.0.0.1) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.60, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
3550_SER_12T#

3550_SER_12T#ping 10.0.0.60

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.60, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
3550_SER_12T#

CLOCK REF on both NTP server and freenas
------------------------------------------------------

3550_SER_12T#sh ntp status
Clock is synchronized, stratum 2, reference is 199.165.76.11
nominal freq is 250.0000 Hz, actual freq is 249.9898 Hz, precision is 2**18
reference time is D5774AF6.C5BA087E (00:36:22.772 BST Fri Jun 28 2013)
clock offset is -8.8563 msec, root delay is 200.21 msec
root dispersion is 10.82 msec, peer dispersion is 3.74 msec
3550_SER_12T#


[root@freenas ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*3550_ser_12t.th 199.165.76.11 2 u 9 64 377 0.691 23.470 4.053
[root@freenas ~]#
 
D

dlavigne

Guest
Can you check to see if a similar bug report already exists at support.freenas.org and create one if it does not?
 

Jason

Cadet
Joined
Jul 10, 2013
Messages
1
I had the same problem and I had to make sure that ntpd was listening on the correct interface.

I ran 2 ntpd commands (not sure if you need both)

ntpd -4 (forces ntp to use IPv4)
ntpd -I bce0 (change bce0 with whatever interface your server is using)
 

msrhedges

Cadet
Joined
Jun 26, 2013
Messages
4
I moved over from (FreeNAS-8.3.1-RELEASE-p2-x64) to (FreeNAS-9.1.1-RELEASE-x64) when it came out and the problem did not exist for me at least. I was able to connect to my NTP server without problem. I should have updated this post but I assumed that the powers that be had fixed it.
 
Status
Not open for further replies.
Top