On Oct 29, 1:08 am, David Woolley <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > The output from ntpq -c"rv": > > I asked you to do ntpq -c"rv nnnnn" > where nnnnn is the number given by ntpq -c"assoc" > for the relevant server. > > However, this output does indicate that you are synchronised to > something other than the local clock. You need to run the command > when the system is broken. > That is really help, at the time sync is successful,
>ntpq -c"assoc" ind assID status conf reach auth condition last_event cnt =========================================================== 1 46864 9614 yes yes none sys.peer reachable 1 After the sync is broken >ntpq -c"assoc" ind assID status conf reach auth condition last_event cnt =========================================================== 1 46864 9014 yes yes none reject reachable 1 condition change from sys.peer to reject, status also changed >ntpq -c"rv 46864" assID=46864 status=9014 reach, conf, 1 event, event_reach, srcadr=10.200.98.51, srcport=123, dstadr=10.200.98.110, dstport=123, leap=00, stratum=5, precision=-20, rootdelay=0.000, rootdispersion=1175.797, refid=127.0.0.1, reach=377, unreach=0, hmode=3, pmode=4, hpoll=8, ppoll=8, flash=400 peer_dist, keyid=0, ttl=0, offset=-24.021, delay=0.294, dispersion=6.001, jitter=1.199, reftime=00000000.00000000 Wed, Feb 6 2036 22:28:16.000, org=ccb35db7.959d8613 Wed, Oct 29 2008 15:09:59.584, rec=ccb35db7.9bf0592f Wed, Oct 29 2008 15:09:59.609, xmt=ccb35db7.9bda87ad Wed, Oct 29 2008 15:09:59.608, filtdelay= 0.31 0.29 0.32 0.33 0.32 0.31 0.40 0.30, filtoffset= -24.55 -24.02 -23.49 -23.01 -22.56 -22.15 -21.85 -21.38, filtdisp= 0.00 3.84 7.71 11.54 15.41 19.28 23.10 26.96 If I start the ntpd client with -d option, it print out auth_agekeys: at 5xxx keys 1 expired 0 looks like the sync break relate to authentication. But it is not enabled. Does this mean ntp4 need it in default? > > assID=0 status=0644 leap_none, sync_ntp, 4 events, event_peer/ > > strat_chg, > > version="ntpd [EMAIL PROTECTED] Sep 01 9:15:56 (UTC+02:00) 2008 > > (10)", > > processor="unknown", system="WINDOWS/NT", leap=00, stratum=6, > > precision=-20, rootdelay=0.304, rootdispersion=58.322, peer=46864, > > refid=10.200.98.51, > > reftime=ccb22e3c.45338a42 Tue, Oct 28 2008 17:35:08.270, poll=6, > > clock=ccb22eb8.2242d2bb Tue, Oct 28 2008 17:37:12.133, state=4, > > offset=-33.131, frequency=-47.242, jitter=10.226, noise=21.119, > > stability=0.104, tai=0 > > >> If you have any w32time servers upstream of you, please note that > >> w32time doesn't honour the maximum distance heuristic, so will report a > >> low stratum number even when the root dispersion is impossibly high, > >> because the server hasn't been synchronised for many days, e.g we have > >> one in the office that is reporting stratum three, even though it has > >> not been synchronised for so long that the time is almost 7 seconds out. > > > w32time has been disabled on all windows based computer, no matter > > server or client. I have tested ntpd in pure linux environment before, > > both server/client are linux, and have no internet connection. It > > seems clients can find the server has untrusted time and refuse to > > sync with it after running a period of time(about 1 day). > >>> server, I did not know which time the client followed. So add > >>> 127.127.1.0, just make sure the client sync to its own clock. At > >> Clients are ALWAYS synchronised to their own clock (for NTPv4)! _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
