Chris Kuethe wrote: > Just wondering what's wrong with the monitor? This morning I had a > look at my graphs and found an ugly 400ms spike in my offset which of > course caused me to go diving for my logs. After checking a couple of > times, I concluded that no, there's nothing wrong with my time server. > Polling a few nearby time servers, I'm well within network error of > being synced to these machines. > > I just checked a few other machines and they all have a big spike > about the same time, and now, like me, they've got an offset of > serveral tens of ms. Did the monitor box get rebooted or something? > Maybe it needs to do a bit more internal health-checking? > > CK
Mine had a similar step: http://www.pool.ntp.org/scores/24.20.30.232 Don't read too much into occasional large offsets on the graph, it happens periodically. The monitoring system isn't perfect. Quote from the Pool website: "The monitoring system works roughly like an SNTP (RFC 2030) client, so it is more susceptible by random network latencies between the server and the monitoring system than a regular ntpd client would be. In other words: Don't be alarmed by the occasional large offset and please don't use the offset as an absolute performance metric." Interesting that they all occurred at similar times though, possibly indicating a network hiccup at the monitoring site(s). Dennis -- Dennis Hilberg, Jr. \ [EMAIL PROTECTED] NTP Server Information: \ http://saturn.dennishilberg.com/ntp.php _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
