[LEAPSECS] leap second festivities?

Wed Jul 1 04:01:26 EDT 2015

After waking this morning and reviewing the data I discovered that the
Azure VMs did in fact leap. The data below was taken from a system that
was set up on purpose to NOT leap. So I had no issues with the NTP
server/clients as far a time goes. As indicated below some systems were
reporting tai=1 in "ntpq -c rv" output after the leap. This appears to
be due to the fact that they no leap second history (no leapsecond file)
and no ref clock. It seems that the current value is not transmitted in
the NTP packets. 

Le 01.07.2015 02:37, mike at lumieresimaginaire.com a écrit : 

> Quick update: The new ntpd smear worked a treat. My FreeBSD, Linux, Windows 7 systems all did the right thing. 
> 
> Two MS Azure Linux VMs didn't. 
> 
> 1 Jul 00:23:32 ntpdate[13601]: step time server 138.91.244.103 offset -1.010117 sec
> mike at bb2:~/src/python$ ntpdate -d 191.238.98.169|grep step
> host found : 191.238.98.169
> 1 Jul 00:24:01 ntpdate[13609]: step time server 191.238.98.169 offset -1.003992 sec 
> 
> All the windows systems are showing tai as 1 rather than 36! Maybe it is expected. 
> 
> And so to bed. 
> 
> Le 30.06.2015 21:40, mike at lumieresimaginaire.com a écrit : 
> 
> No booze.. aargh! Have to make do with monitoring. As one experiment, I have just installed .8p3 on a BBB to see what a smeared LS looks like. Seems to be working. Or at least doing something. 
> 
> mike at bb2:~/src/python$ ntpq -c rv bb1
> associd=0 status=4619 leap_add_sec, sync_ntp, 1 event, leap_armed,
> version="ntpd 4.2.8p3 at 1.3265-o Tue Jun 30 16:13:35 UTC 2015 (1)",
> processor="armv7l", system="Linux/3.8.13-bone47", leap=01, stratum=2,
> precision=-19, rootdelay=0.606, rootdisp=6.423, refid=192.168.1.4,
> reftime=d93d6d9a.0ab325f9 Tue, Jun 30 2015 19:33:46.041,
> clock=d93d6e92.ea82989e Tue, Jun 30 2015 19:37:54.916, peer=51860, tc=6,
> mintc=3, offset=-0.003556, frequency=-30.188, sys_jitter=0.055002,
> clk_jitter=0.017, clk_wander=0.005, tai=35, leapsec=201507010000,
> expire=201512010000, leapsmearinterval=21600, leapsmearoffset=-171.641 
> 
> mike at bb2:~/src/python$ ntpdate -d bb1|grep adjust
> host found : bb1.stratum1.d2g.com
> 30 Jun 19:39:01 ntpdate[9545]: adjust time server 192.168.1.30 offset -0.175234 sec
> 
> We'll see how it goes. 
> 
> Le 30.06.2015 15:51, Poul-Henning Kamp a écrit : 
> 
> --------
> In message <37D91CA5-9BB1-45B5-AECF-5BFC08F28968 at noao.edu>, Rob Seaman writes:
> What are people's plans for the day? 
> 
> I'm setting up as much of my usual data collection as I can get to
> work, in order to have and provide test-data for tests of leap-second
> handling.
> 
> It doesn't look like I'll get my VLF sampler running though.
> 
> Previous leapsecond data:
> 
> http://phk.freebsd.dk/Leap/20081231/ [1]
> 
> http://phk.freebsd.dk/Leap/20051231_HBG/ [2]

_______________________________________________
LEAPSECS mailing list
LEAPSECS at leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs [3]

_______________________________________________
LEAPSECS mailing list
LEAPSECS at leapsecond.com
https://pairlist6.pair.net/mailman/listinfo/leapsecs [3]

Links:
------
[1] http://phk.freebsd.dk/Leap/20081231/
[2] http://phk.freebsd.dk/Leap/20051231_HBG/
[3] https://pairlist6.pair.net/mailman/listinfo/leapsecs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/leapsecs/attachments/20150701/93246e41/attachment.html>