Chris asks: > 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?
Did you get kicked out of the pool as a result? There are obvious occasional network latency issues that come up not just for individual servers but for the monitor too... and I think that unless you were previously borderline, a single 400ms assymetric latency during a check probably didn't get you kicked out of the pool. If this gets bad enough such that all servers get kicked out of the pool and there's nobody left, then there's a problem to be fixed. All IMHO. Tim. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
