David Dyer-Bennet
Patron
- Joined
- Jul 13, 2013
- Messages
- 286
I noticed my clock was off; turns out ntpd isn't able to connect.
I can't find *any* NTP config in FreeNAS, so I don't see that I could have altered it stupidly, and it's been working for years.
Clearly it's NOT able to reach the servers:
But there doesn't seem to be any low-level networking disconnect:
If I stop ntpd, ntpdate still can't reach that server I pinged
(If I don't stop ntpd I get an error that the NTP port is still in use).
ssh-ing to that server also works -- that is, I get the message about the server key not being known. I don't have an account there, so I can't log in, but that shows ssh is able to make a tcp connection there. I did the ping and ssh tests from the shell window in the FreeNAS web GUI, so it should be going through exactly the same networking infrastructure as ntpd itself is.
Any thoughts? (Oh, restarting ntpd and rebooting the system haven't helped, either; the system reboot was for something else, but it didn't help this.)
This is also FreeNAS 9.10, which is now not current (but no way in hell am I upgrading two weeks before Minicon, with two big projects hoping desperately to be ready by then).
Here's what's in /etc/ntp.conf:
I don't remember ever changing it by hand, and the file date matches the latest reboot, so it's whatever was in the config database.
I can't find *any* NTP config in FreeNAS, so I don't see that I could have altered it stupidly, and it's been working for years.
Clearly it's NOT able to reach the servers:
[root@fsfs ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
optimize3.exact .INIT. 16 u - 64 0 0.000 0.000 0.000
mdnworldwide.co .INIT. 16 u - 64 0 0.000 0.000 0.000
ntp1.wiktel.com .INIT. 16 u - 64 0 0.000 0.000 0.000
But there doesn't seem to be any low-level networking disconnect:
[root@fsfs ~]# ping ntp1.wiktel.com
PING ntp1.wiktel.com (69.89.207.99): 56 data bytes
64 bytes from 69.89.207.99: icmp_seq=0 ttl=57 time=10.321 ms
64 bytes from 69.89.207.99: icmp_seq=1 ttl=57 time=10.308 ms
64 bytes from 69.89.207.99: icmp_seq=2 ttl=57 time=10.334 ms
If I stop ntpd, ntpdate still can't reach that server I pinged
[root@fsfs ~]# service ntpd stop
Stopping ntpd.
Waiting for PIDS: 93359, 93359.
[root@fsfs ~]# ntpdate ntp1.wiktel.com
16 Mar 19:04:18 ntpdate[94664]: no server suitable for synchronization found
[root@fsfs ~]#
(If I don't stop ntpd I get an error that the NTP port is still in use).
ssh-ing to that server also works -- that is, I get the message about the server key not being known. I don't have an account there, so I can't log in, but that shows ssh is able to make a tcp connection there. I did the ping and ssh tests from the shell window in the FreeNAS web GUI, so it should be going through exactly the same networking infrastructure as ntpd itself is.
Any thoughts? (Oh, restarting ntpd and rebooting the system haven't helped, either; the system reboot was for something else, but it didn't help this.)
This is also FreeNAS 9.10, which is now not current (but no way in hell am I upgrading two weeks before Minicon, with two big projects hoping desperately to be ready by then).
Here's what's in /etc/ntp.conf:
[root@fsfs ~]# cat /etc/ntp.conf
server 0.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
server 1.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
server 2.freebsd.pool.ntp.org iburst maxpoll 10 minpoll 6
restrict default limited kod nomodify notrap nopeer noquery
restrict -6 default limited kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
restrict 127.127.1.0
I don't remember ever changing it by hand, and the file date matches the latest reboot, so it's whatever was in the config database.
