[no subject]

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 <mlichvar@xxxxxxxxxx>=20
Sendt: 29. april 2024 09:25
Til: chrony-users@xxxxxxxxxxxxxxxxxxxx
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 r=
eference 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_measurem=
ents

> From the config file.
> server mmo1.nts.netnod.se nts iburst minpoll 6 maxpoll 7
>=20
> 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
>=20
> Regards
> Henning-

--
Miroslav Lichvar


--=20
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx=20
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx=20
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


-- 
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.