SV: Update interval larger than maxpoll

Henning Svane <hsv-i2u8QauLV39aa/[email protected]>
Newsgroups gmane.comp.time.chrony.user
Message-ID <[email protected]>
Hi Miroslav

Thanks for your answer.

Sorry I was not clear in my question.
My first question was more to what extend do offset say anything about the precision or how to understand it?

I tried to run ntpdata and that made even more confused as the Ref time (UTC) for tracking and ntpdata even that they have been executed with a second between says 20 minutes. And the time for ntpdata is the correct one. Why do tracking think that the time is 20 minutes behind?
It now says:
From tracking>> Update interval : 7113.7 seconds
From ntpdata>> NTP tests       : 111 111 1101
So there should be connection to the time source, and if not I have multiple time sources in the config file.
server time.dfm.dk nts iburst  minpoll 6 maxpoll 7
server gbg1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server gbg2.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server lul1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server lul2.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server mmo1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server mmo2.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server sth1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server sth2.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server svl1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server svl2.nts.netnod.se nts iburst minpoll 6 maxpoll 7
server ptbtime1.ptb.de nts iburst minpoll 6 maxpoll 7
server ptbtime2.ptb.de nts iburst minpoll 6 maxpoll 7
server ptbtime3.ptb.de nts iburst minpoll 6 maxpoll 7


swntp01:~$ chronyc tracking
Reference ID    : C23ACCC4 (mmo1-ts.nts.netnod.se)
Stratum         : 2
Ref time (UTC)  : Wed May 01 09:28:58 2024
System time     : 0.000064759 seconds slow of NTP time
Last offset     : -0.000051572 seconds
RMS offset      : 0.000062700 seconds
Frequency       : 51.482 ppm fast
Residual freq   : -0.000 ppm
Skew            : 0.011 ppm
Root delay      : 0.003480395 seconds
Root dispersion : 0.001774998 seconds
Update interval : 7113.7 seconds
Leap status     : Normal
swntp01:~$ sudo chronyc ntpdata mmo1-ts.nts.netnod.se
Remote address  : 194.58.204.196 (C23ACCC4)
Remote port     : 4123
Local address   : 10.40.20.11 (0A28140B)
Leap status     : Normal
Version         : 4
Mode            : Server
Stratum         : 1
Poll interval   : 7 (128 seconds)
Precision       : -24 (0.000000060 seconds)
Root delay      : 0.000000 seconds
Root dispersion : 0.000000 seconds
Reference ID    : 50505300 (PPS)
Reference time  : Wed May 01 09:48:19 2024
Offset          : +0.000113114 seconds
Peer delay      : 0.019906688 seconds
Peer dispersion : 0.000000079 seconds
Response time   : 0.000004407 seconds
Jitter asymmetry: +0.00
NTP tests       : 111 111 1101
Interleaved     : No
Authenticated   : Yes
TX timestamping : Daemon
RX timestamping : Kernel
Total TX        : 1724
Total RX        : 1717
Total valid RX  : 1717

-----Oprindelig meddelelse-----
Fra: Miroslav Lichvar <[email protected]> 
Sendt: 29. april 2024 09:25
Til: [email protected]
Emne: Re: [chrony-users] 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]


-- 
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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.