| Re: [chrony-users] chrony switch to low stratum very slow |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Wed, Aug 21, 2019 at 12:11:15PM -0700, chuang213 wrote:
> the local clock is the fallback in case none of the source is not available
> so that the server could continue to provide time service to local network.
For that the "local stratum" line is enough. Specifying 127.127.1.0 as
a server will cause chronyd to poll itself over NTP and create a
synchronization loop when selected (until stratum reaches 16). If it
becomes unsynchronized for any reason, this source will be
unsychronized too. You should remove that source. It's only causing
problems.
In ntpd it is different. Addresses in the 127.127.0.0/16 range specify
refclocks. There are no NTP packets exchanged. 127.127.1.0 is a LOCAL
driver, which simulates a reference clock based on the local clock.
It's a hack that has problems and it was deprecated when ntpd got its
own local reference mode (orphan mode).
> > 2019-08-20 23:41:52 PPS 9.088e-06 -9.657e-06 4.871e-06
> > -2.323e-07 6.526e-07 1.0e-01 7 0 4 0.00
> > 2019-08-20 23:42:03 127.127.1.0 5.293e-06 1.146e-05 3.293e-06
> > -1.253e-08 1.335e-07 3.7e-01 7 0 5 -0.50
Here it looks like it considered itself to be significantly more
stable than the PPS refclock. That's likely why it briefly reselected.
We would need to see the debug output to confirm that.
--
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.