| Re: [chrony-dev] Issue with version 1.25 and GPRS/GSM connections |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Mon, Aug 22, 2011 at 12:25:42PM +0200, Harald Krammer wrote:
> Result 3:
> #########
> Version: Chrony 1.26-git (without test6, with iburst)
>
> It looks interesting. The offset is 6651.414062500s.
> Normally my application monitors the offet with the
> tracking command and if the offset gets to high,
> chrony will be restarted.
> System time : 6651.414062500 seconds fast of NTP time
> Frequency : 73.729 ppm fast
> Residual freq : -0.001 ppm
> Skew : 0.097 ppm
This looks like chrony wasn't configured to step the clock
(initstepslew or makestep). The value should be going down by
0.083 second per second (~22 hours to reach zero).
> Result 4:
> #########
> My "Chrony hang problem" looks to me, that the time server gets
> into state non-synchronizes.
> In 'command sources' a non-synchronizes server entry looks like
> an entry with '?', but all other fields are shown with valid
> entries. Detection of 'timer source unsynchronized' may help.
> What do you think?
Is this the problem that was supposed to be fixed in current git or
something else? Do you have the logs from this test?
--
Miroslav Lichvar
---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.