[no subject]

TEst 1 and 2 test to make sure that the timestamps make sense (eg are not the
wsame as an old packet and pairs with the last one sent to that peer) test3 is
that the originate and receive timestamps are non-zero, Test 4 is taht the
delay (round trip time) be reasonable, abc are subsets of that, 5 is
authentication, test 6 irequires peer clock by synchronized and that the
itnerval since the peer clock was last updated is positive and less than
NTP.MAXAGE, test 7 that the host has no lower stratum than the server, and 8
that the header contains reasonable values for rootdelay and rootdispersion.

Ie, if any of the tests are out the server's time is too suspect to use. Your
server is problematic.


> 
> I marked some lines that look suspicious to me. In in the first line, some test seems to fail [110]. In the 2nd line, suddenly
> the offset jumps up to -1.9 seconds.
> For the 3rd line, from the documentation I found this:
> 
> Leap status: ? means the remote computer is not currently synchronised.
> 5678: Tests for maximum delay, maximum delay ratio and maximum delay dev ratio, against defined parameters, and a test for
> synchronisation loop (1=pass, 0=fail) [1111]
> 
> So that would mean that delay ratio and delay dev ratio is bad...not sure what that really means though.

It means that the round trip time is out of spec. And it looks like your
source, whatever that is, went nuts and jumped by 2 sec suddenly. that is why
you should be using at least 3 sources. If one goes mad, the others can
outvote it. If you only use 1, then its time is by definition right, even if
it is out by 40 years.


> 
> 
> I find this very hard to debug, is there any other thing I could do to find out what's exactly going wrong?

Talk to the person who is sysadmin on the server and find out what happened. 
Use more than one server.


> 
> Thanks for your answers in advance,
> 
> Ulrich
> 
>

-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.