>> Also check the ntpd is locked to your PPS during the events. > Is there a way to check that retroactively?
Turn on protostats and/or the flags that lots of stuff into ntp.log logconfig =syncall +clockall +peerall +sysall 18 Nov 12:32:20 ntpd[140066]: PROTO: 192.168.1.32 f4da 8a sys_peer 18 Nov 12:37:25 ntpd[140066]: PROTO: 192.168.1.33 f4ea 8a sys_peer 18 Nov 12:39:31 ntpd[140066]: PROTO: 192.168.1.32 f4ea 8a sys_peer 58807 783.327 192.168.1.33 f4ba 8a sys_peer 58807 4230.355 192.168.1.33 f4ca 8a sys_peer 58807 5652.166 192.168.1.33 f4da 8a sys_peer 58807 7646.165 192.168.1.33 f4ea 8a sys_peer 58807 10788.166 192.168.1.33 f4fa 8a sys_peer 58807 25980.162 192.168.1.50 b01d 8d popcorn 0.000262 s 58807 44765.161 192.168.1.38 b01d 8d popcorn 0.000039 s 58807 55698.165 51.89.151.183 e013 83 unreachable 58807 60530.162 192.168.1.50 b02d 8d popcorn 0.000238 s 58807 61267.161 192.168.1.82 f01d 8d popcorn 0.000077 s 58807 64180.617 54.39.23.64 e014 84 reachable 58807 67425.161 192.168.1.48 b01d 8d popcorn 0.000039 s If something does happen, we'll have to figure out what the log info is trying to tell us. If nothing gets logged around that time we can be pretty sure that nothing interesting happened. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
