Did your systems survive the leap second?
Yet again, signs of insanity in the ntp department:
remote local st poll reach delay offset disp
=======================================================================
=127.127.1.0 127.0.0.1 10 64 0 0.00000 0.000000 3.99217
=69.64.72.238 10.3.1.111 2 256 377 0.03653 1.004648 0.11946
*108.59.14.130 10.3.1.111 2 256 377 0.09084 0.005996 0.10413
=216.129.110.22 10.3.1.111 2 256 377 0.08861 -0.008799 0.07570
Check out that offset on the second entry! Yep. A peer used by one of my ntp instances decided to go rogue or otherwise decided it was time for a stroll in the weeds. Fortunately, this is just a testing laptop I grabbed for this afternoon's "event" and it isn't doing anything meaningful.
It looks like things are fine here, at least.
Jun 30 16:59:59 oasis kernel: Clock: inserting leap second 23:59:60 UTC
How'd your systems do? It seems some people had a bad time with this whole thing.