NTPsec leap second experience

[Matthew Selsky]

On Sat, Jan 07, 2017 at 05:36:14PM -0500, Jason Azze wrote:
> 
> Dec 31 18:59:59 harbormaster kernel: [14461.150782] Clock: inserting
> leap second 23:59:60 UTC
> Dec 31 18:59:59 harbormaster systemd[1]: Time has been changed
> Dec 31 18:59:59 harbormaster systemd[2163]: Time has been changed
> Dec 31 18:59:59 harbormaster systemd[1]: snapd.refresh.timer: Adding
> 1h 27min 14.876839s random time.
> Dec 31 18:59:59 harbormaster systemd[1]: apt-daily.timer: Adding 10h
> 37min 25.745ms random time.
> Dec 31 18:59:59 harbormaster systemd[1459]: Time has been changed
> Dec 31 18:59:59 harbormaster ntpd[6653]: SHM: stale/bad receive time, delay=-1s
> Dec 31 19:00:47 harbormaster ntpd[6653]: kernel reports leap second has occurred
> Dec 31 19:00:47 harbormaster ntpd[6653]: kernel reports leap second has occurred

Jason,

Do you know the source of the SHM error message in your logs?

My classic ntpd stratum-1 clocks reported the "kernel reports leap second..." line twice (maybe a bug?), but there were no SHM errors.

Thanks,
-Matt