Re: Update interval larger than maxpoll

On Sun, Apr 28, 2024 at 09:40:27AM +0000, Henning Svane wrote:
> 2 questions
> The green line: Is it correct that the time is only 0,03ms off from the reference time.

We don't know that. The root delay and dispersion are in
milliseconds. You would need a much more accurate time source (e.g.
reference clock or close stratum 1 server) to be able to measure the
error of the clock in microseconds.

> The red line I cannot understand why I get and update period over 128s.

That might be due to measurements failing some NTP tests. Check
ntpdata or the measurements log. See also this answer to a similar
question:

https://chrony-project.org/faq.html#_does_selected_source_drop_new_measurements

> From the config file.
> server mmo1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
> 
> odin@swntp01:/var/log/zabbix$ chronyc tracking
> Reference ID    : C23ACCC4 (mmo1-ts.nts.netnod.se)
> Stratum         : 2
> Ref time (UTC)  : Sat Apr 27 09:46:46 2024
> System time     : 0.000013121 seconds slow of NTP time
> Last offset     : -0.000007295 seconds
> RMS offset      : 0.000003989 seconds
> Frequency       : 51.591 ppm fast
> Residual freq   : -0.000 ppm
> Skew            : 0.010 ppm
> Root delay      : 0.002788649 seconds
> Root dispersion : 0.005857296 seconds
> Update interval : 8004.5 seconds
> Leap status     : Normal
> 
> Regards
> Henning-

-- 
Miroslav Lichvar


-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]