[ntp:questions] Synchronizing contrived time

mike cook michael.cook at sfr.fr
Mon Mar 10 13:08:04 UTC 2014


Le 10 mars 2014 à 13:42, Amit Dor-Shifer a écrit :

> Additional attempt. I've replaced openntpd with ntp-4.2.6.p3+dfs on ubuntu
> server (192.168.1.11). server seems to initialize correctly. Yet client
> won't sync:
> 
> <quote>
> # client-side
> $ ntpdate -d 192.168.1.11

  you are using -d option which just tells you what the current offset is but does not set the clock.
  so just use ntpdate 192.168.1.11


  ignore the minpoll maxpoll options. They aren't particularly relevant for your test. See the ntp.org site for man pages. 

hope that helps.
Mike


> 10 Mar 23:29:41 ntpdate[93318]: ntpdate 4.2.6 at 1.2089-o Fri May 28 01:20:57
> UTC 2010 (1)
> #...
> transmit(192.168.1.11)
> receive(192.168.1.11)
> transmit(192.168.1.11)
> receive(192.168.1.11)
> transmit(192.168.1.11)
> receive(192.168.1.11)
> transmit(192.168.1.11)
> receive(192.168.1.11)
> transmit(192.168.1.11)
> 192.168.1.11: Server dropped: strata too high
> server 192.168.1.11, port 123
> stratum 16, precision -23, leap 11, trust 000
> refid [192.168.1.11], delay 0.02829, dispersion 0.00035
> transmitted 4, in filter 4
> reference time:    00000000.00000000  Mon, Jan  1 1900 10:00:00.000
> originate timestamp: d6c7d4f1.0307693c  Mon, Mar 10 2014 17:06:41.011
> transmit timestamp:  d6c82eb5.91f99c38  Mon, Mar 10 2014 23:29:41.570
> filter delay:  0.03349  0.02858  0.02829  0.02834
>         0.00000  0.00000  0.00000  0.00000
> filter offset: -22980.5 -22980.5 -22980.5 -22980.5
>         0.000000 0.000000 0.000000 0.000000
> delay 0.02829, dispersion 0.00035
> offset -22980.560166
> 
> 10 Mar 23:29:41 ntpdate[93318]: no server suitable for synchronization found
> </quote>
> 
> Appreciate if you could point me to the place in the manpage that addresses
> configuring stratum. I can't find it (nor min/maxpoll for that matter).
> Thanks,
> Amit
> 
> 
> 
> 
> On Mon, Mar 10, 2014 at 11:09 PM, Amit Dor-Shifer <amit.dor.shifer at gmail.com
>> wrote:
> 
>> Thanks.
>> Would this then be the reference implementation?
>> 
>> [user at centos test_ntpd]$ rpm -qf $(which ntpd)
>> ntp-4.2.6p5-1.el6.centos.x86_64
>> [user at centos test_ntpd]$ cat ~/test_ntpd/ntp.conf
>> server 127.127.1.0 minpoll 4 maxpoll 4
>> [user at centos test_ntpd]$ ps -ef|grep ntp
>> user     13411 12236  0 22:03 pts/0    00:00:00 grep ntp
>> 
>> # moving clock back some 50 mins
>> 
>> [user at centos test_ntpd]$ sudo tail -f /var/log/messages
>> #...
>> [user at centos test_ntpd]$ sudo ntpd -f ~/test_ntpd/ntp.conf
>> Mar 10 22:04:52  ntpd[13443]: ntpd 4.2.6p5 at 1.2349-o Sat Nov 23 18:21:48
>> UTC 2013 (1)
>> [user at centos test_ntpd]$ Mar 10 22:04:52  ntpd[13444]: proto: precision =
>> 1.260 usec
>> Mar 10 22:04:52  ntpd[13444]: 0.0.0.0 c01d 0d kern kernel time sync enabled
>> Mar 10 22:04:52  ntpd[13444]: format error frequency file
>> /home/user/test_ntpd/ntp.conf
>> Mar 10 22:04:52  ntpd[13444]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP
>> 123
>> Mar 10 22:04:52  ntpd[13444]: Listen and drop on 1 v6wildcard :: UDP 123
>> Mar 10 22:04:52  ntpd[13444]: Listen normally on 2 lo 127.0.0.1 UDP 123
>> Mar 10 22:04:52  ntpd[13444]: Listen normally on 3 eth0 10.250.129.79 UDP
>> 123
>> Mar 10 22:04:52  ntpd[13444]: Listen normally on 4 lo ::1 UDP 123
>> Mar 10 22:04:52  ntpd[13444]: Listen normally on 5 eth0
>> fe80::2000:aff:fefa:814f UDP 123
>> Mar 10 22:04:52  ntpd[13444]: peers refreshed
>> Mar 10 22:04:52  ntpd[13444]: Listening on routing socket on fd #22 for
>> interface updates
>> Mar 10 22:04:52  ntpd[13444]: 0.0.0.0 c016 06 restart
>> Mar 10 22:04:52  ntpd[13444]: 0.0.0.0 c012 02 freq_set kernel -25.992 PPM
>> 
>> [user at centos test_ntpd]$
>> [user at centos test_ntpd]$ Mar 10 22:04:59  ntpd[13444]: 0.0.0.0 c617 07
>> panic_stop +3203 s; set clock manually within 1000 s.
>> 
>> # ntpd terminates :(
>> 
>> ps -ef |grep ntp
>> user     13450 12236  0 22:05 pts/0    00:00:00 grep ntp
>> 
>> 
>> 
>> On Mon, Mar 10, 2014 at 10:47 PM, mike cook <michael.cook at sfr.fr> wrote:
>> 
>>> 
>>> I just checked the openntpd site and see that they do not use the same
>>> format of config file, ntpd.conf.
>>> 
>>>  I am afraid it's an RTFM.
>>> 
>>> You could just take out minpoll, maxpoll  and retry, though you may need
>>> other config info. So check the man page for a minimal legal config.
>>> 
>>> Le 10 mars 2014 à 12:36, mike cook a écrit :
>>> 
>>>> 
>>>> Le 10 mars 2014 à 11:51, Amit Dor-Shifer a écrit :
>>>> 
>>>>> /usr/sbin/openntpd -f ~/test_ntpd/ntp.conf
>>>> 
>>>> I was using a FreeBSD 8.2 ntp 4.2.6p3 server. I don't have experience
>>> with openntp, but I thought the executable was also called ntpd. Maybe the
>>> openntpd is a wrapper. Also if you did a copy/paste from the mail, you may
>>> have picked up ctrl characters that are not recognized.
>>>> _______________________________________________
>>>> questions mailing list
>>>> questions at lists.ntp.org
>>>> http://lists.ntp.org/listinfo/questions
>>> 
>> 
>> 
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions


More information about the questions mailing list