Todd wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thought people may find this of interest. I mentioned before I used the > prefer keyword on my server and then add 4 other pool addresses. Well I > start getting loghcheck messags saying the PPM was over 512 or > something. So I quickly did a check (edited for space) > > remote refid st t when poll reach delay offset jitter > ==================================================================== > +66.218.191.215 [..] 2 u 34 64 377 0.314 275.345 60.958 > +66.36.239.104 [..] 2 u 19 64 377 24.400 215.636 61.105 > *130.236.254.17 [..] 1 u 39 64 377 125.250 227.845 59.225 > - -66.226.73.89 [..] 2 u 37 64 377 73.314 306.056 77.870 > > My server, 66.218.191.215, even with the prefer tag was still overridden > by a st1 server that was obviously not very accurate IMO. Seems like it > would want to go with the server that has a .314 delay (it's located in > the same rack) and has the prefer tag set on it. Also thought it was > interesting it only picked 3 other servers. Here's the area of the > /etc/ntp.conf: > > server rikku.vrillusions.com iburst prefer > server 0.debian.pool.ntp.org iburst > server 1.debian.pool.ntp.org iburst > server 2.debian.pool.ntp.org iburst > server 3.debian.pool.ntp.org iburst > > I just added my server to the top of the current default config. > Perhaps one of those aliases aren't live? If I think about it I'll post > the top section to the newsgroup as that's a more generic ntp > observation that I thought people here may find interesting. > > I think you've got something else going on - notice that the offset is high for all the servers and in the same direction - your clock has drifted a long way for some reason. It's probably picking the 130. server because it has the lowest jitter and a higher stratum however the jitter numbers are very odd all round - a server 0.315 away should not have 60ms of jitter making me think you've got other problems. I've seen similar issues on machines where net cards or hdd's are failing and the system gets hung up in a critical region of the OS and is not processing interrupts.
For reference a machine 0.354 away on my net shows a jitter of 0.039 John _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
