> On May 29, 2015, at 11:51 AM, jungle Boogie <jungleboog...@gmail.com> wrote: > > Hello All, > > Running openntpd portable version 5.7 without HTTPS contraint, like I > have been doing for many months now, but upon rebooting, a machine > can't sync:
The ntpdate command is not a part of openntpd. 'ntpctl all' would show information about the state of openntpd and its peers. > % ntpdate -d hank > 29 May 09:37:10 ntpdate[39781]: ntpdate 4.2.4p5-a (1) > transmit(192.168.0.14) > receive(192.168.0.14) > transmit(192.168.0.14) > receive(192.168.0.14) > transmit(192.168.0.14) > receive(192.168.0.14) > transmit(192.168.0.14) > receive(192.168.0.14) > transmit(192.168.0.14) > 192.168.0.14: Server dropped: Leap not in sync > server 192.168.0.14, port 123 > stratum 3, precision -29, leap 11, trust 000 > refid [192.168.0.14], delay 0.02574, dispersion 0.00000 > transmitted 4, in filter 4 > reference time: d91313a4.69eeb7ff Fri, May 29 2015 9:34:44.413 > originate timestamp: d9131436.716697ff Fri, May 29 2015 9:37:10.442 > transmit timestamp: d9131436.712cd40d Fri, May 29 2015 9:37:10.442 > filter delay: 0.02585 0.02576 0.02574 0.02576 > 0.00000 0.00000 0.00000 0.00000 > filter offset: 0.000820 0.000801 0.000802 0.000805 > 0.000000 0.000000 0.000000 0.000000 > delay 0.02574, dispersion 0.00000 > offset 0.000802 > > 29 May 09:37:10 ntpdate[39781]: no server suitable for synchronization found > > Same messages here: > % ntpdate hank > 29 May 09:38:11 ntpdate[39783]: no server suitable for synchronization found > > % ntpdate -u hank > 29 May 09:38:39 ntpdate[39785]: no server suitable for synchronization found > > > On hank, I see this connection: > _ntp ntpd 2021 7 udp4 192.168.0.14:123 *:* > _ntp ntpd 2021 10 udp4 127.0.0.1:123 *:* > _ntp ntpd 2021 14 udp4 192.168.0.14:61375 192.241.209.150:123 > _ntp ntpd 2021 15 udp4 192.168.0.14:19628 108.61.194.85:123 > _ntp ntpd 2021 16 udp4 192.168.0.14:34155 70.35.113.44:123 > _ntp ntpd 2021 17 udp4 192.168.0.14:43924 129.6.15.30:123 > > > ntpd file is nothing special: > % cat /usr/local/etc/ntpd.conf > # sample ntpd configuration file, see ntpd.conf(5) > > # Addresses to listen on (ntpd does not listen by default) > listen on * > > # sync to a single server > #server ntp.example.org > > # use a random selection of NTP Pool Time Servers > # see http://support.ntp.org/bin/view/Servers/NTPPoolServers > server 0.pool.ntp.org > server 1.pool.ntp.org > server 2.pool.ntp.org > server 3.pool.ntp.org > > Even running ntpdate to adjust time fails: > % ntpdate 0.pool.ntp.org > 29 May 09:44:43 ntpdate[2031]: no server suitable for synchronization found > > But when running: > % ntpdate -d 0.pool.ntp.org > > its final output adjusts the time: > 29 May 09:49:23 ntpdate[2041]: adjust time server 192.241.209.150 > offset -0.003387 sec > > > Any ideas what prevents openntpd from syncing? > > > -- > ------- > inum: 883510009027723 > sip: jungleboo...@sip2sip.info > xmpp: jungle-boo...@jit.si
