| Re: [chrony-users] Time synchronisation over a high-latency packet radio network |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, May 07, 2019 at 05:54:04PM +1000, Stuart Longland wrote:
> http://static.vk4msl.id.au/wicen/rfid/chrony/measurements.log
> http://static.vk4msl.id.au/wicen/rfid/chrony/statistics.log
> http://static.vk4msl.id.au/wicen/rfid/chrony/tracking.log
It's not very clear to me which parts of the logs correspond to the
non-working situation, but the tracking log shows there were some
updates of the clock, even with a large initial offset, and the
measurements log shows that the distance is quite close to the default
maximum (3 seconds).
I'd suggest to set maxdistance to 5 or 10 to make sure it's not a
problem with selecting the source. Try to reproduce the problem and
post the output from the chronyc ntpdata, sources, sourcestats and
tracking commands.
--
Miroslav Lichvar
--
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.