carre otis dating - Ntp not updating system time
NTPD is running ntpq -pcrv -bash-3.2# ntpq -pcrv remote refid st t when poll reach delay offset jitter ============================================================================== dc3.domai 10.1.1.2 2 u 29 64 377 0.567 -4263.4 10.392 ass ID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart, version="ntpd [email protected] Mon Dec 9 UTC 2013 (1)", processor="i686", system="Linux/3.10.23-xxxx-std-ipv6-32", leap=11, stratum=16, precision=-20, rootdelay=0.000, rootdispersion=2356.905, peer=0, refid=INIT, reftime=00000000.00000000 Thu, Feb 7 2036 .000, poll=6, clock=d81ce655.d5ce975b Mon, Nov 24 2014 .835, state=1, offset=0.000, frequency=-0.140, jitter=0.001, noise=0.001, stability=0.000, tai=0 Something looks to be broken in your time setup.
I would check the 2 other boxes DC1 & 3 to ensure they are getting the correct time. 1 u 40 64 377 9.468 0.209 0.129 -PRIVATE3 18.104.22.168 2 u 12 64 377 6.943 -0.270 0.142 -PRIVATE5 .
Two servers is the "worst possible configuration" according to the NTP authors since it will never know which one is "more" correct.
Please visit this page to clear all LQ-related cookies.
This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
I also heard of Xen VMs clocks misbehaving before, but not like that and nothing that ntpd running wouldn't solve.
Thanks for the idea hwclock gave me an error : As well as in other hardware machines I had.
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.