NTP time sync strange behavior

Modifications
,
1

Is it normal to have thousands of lines like the ones below in /var/log/messages ?
All files like messages.x(0,1,2,3,4,5) contains only lines like this, the oldest one being from June 19…
Sometime at second interval, other times jumping 2-3 hours between records…

Jun 27 04:19:23 einstein daemon.info connmand[749]: ntp: time slew -0.000673 s
Jun 27 04:19:24 einstein daemon.info connmand[749]: ntp: time slew +0.000079 s
Jun 27 04:19:25 einstein daemon.info connmand[749]: ntp: time slew +0.000419 s
Jun 27 04:19:26 einstein daemon.info connmand[749]: ntp: time slew +0.000309 s
Jun 27 04:19:27 einstein daemon.info connmand[749]: ntp: time slew -0.000341 s
Jun 27 04:19:28 einstein daemon.info connmand[749]: ntp: time slew -0.000254 s
Jun 27 04:19:29 einstein daemon.info connmand[749]: ntp: time slew +0.000003 s
Jun 27 04:19:30 einstein daemon.info connmand[749]: ntp: time slew -0.000005 s
Jun 27 04:19:31 einstein daemon.info connmand[749]: ntp: time slew +0.000488 s
Jun 27 04:19:32 einstein daemon.info connmand[749]: ntp: time slew -0.000698 s
Jun 27 04:19:35 einstein daemon.info connmand[749]: ntp: time slew +0.000223 s
Jun 27 04:19:36 einstein daemon.info connmand[749]: ntp: time slew +0.000599 s
Jun 27 04:19:37 einstein daemon.info connmand[749]: ntp: time slew +0.000242 s
Jun 27 04:19:38 einstein daemon.info connmand[749]: ntp: time slew -0.001440 s
Jun 27 04:19:39 einstein daemon.info connmand[749]: ntp: time slew +0.000048 s
Jun 27 04:19:40 einstein daemon.info connmand[749]: ntp: time slew +0.000129 s
Jun 27 04:19:41 einstein daemon.info connmand[749]: ntp: time slew -0.000097 s
Jun 27 04:19:42 einstein daemon.info connmand[749]: ntp: time slew -0.000380 s
Jun 27 04:19:43 einstein daemon.info connmand[749]: ntp: time slew -0.000026 s
Jun 27 04:19:44 einstein daemon.info connmand[749]: ntp: time slew +0.000199 s
Jun 27 04:19:45 einstein daemon.info connmand[749]: ntp: time slew +0.000583 s
Jun 27 04:19:46 einstein daemon.info connmand[749]: ntp: time slew -0.000320 s
Jun 27 04:19:47 einstein daemon.info connmand[749]: ntp: time slew +0.000308 s
Jun 27 04:19:48 einstein daemon.info connmand[749]: ntp: time slew -0.000241 s
Jun 27 04:19:49 einstein daemon.info connmand[749]: ntp: time slew -0.001053 s
Jun 27 04:19:50 einstein daemon.info connmand[749]: ntp: time slew +0.000335 s
Jun 27 04:19:51 einstein daemon.info connmand[749]: ntp: time slew +0.000923 s
Jun 27 04:19:52 einstein daemon.info connmand[749]: ntp: time slew +0.000012 s
Jun 27 04:19:53 einstein daemon.info connmand[749]: ntp: time slew -0.001545 s
Jun 27 04:19:54 einstein daemon.info connmand[749]: ntp: time slew +0.000233 s
Jun 27 04:19:55 einstein daemon.info connmand[749]: ntp: time slew -0.000174 s
Jun 27 04:19:56 einstein daemon.info connmand[749]: ntp: time slew +0.000390 s
Jun 27 04:19:57 einstein daemon.info connmand[749]: ntp: time slew -0.000441 s
Jun 27 04:19:58 einstein daemon.info connmand[749]: ntp: time slew +0.000020 s
Jun 27 04:19:59 einstein daemon.info connmand[749]: ntp: time slew -0.000489 s
2

From what I know, the poll adjustment ranges from the default minimum of 64 sec. to the default maximum of 1024 sec.
But here it seems that the system polls at second interval…
That “ntp: time slew…” message is a telltale that a NTP packet was received.
But in order for a packet to be received, a request must be sent.
So why the system is doing such an overhead, cluttering the network with such (non recommended) frequent requests??

PS.
I see that the message was moved by the admins through 3 categories until now…
Hope that an answer from developers to help us understand what is happening “underwater”.
Thanks in advance.

3

I see that only since April 23, 2025, the developers have silenced the “time slew log spam”, how they call it…
So this will not happen since version 3.60 onward…
To be clear…
The network traffic is still there (beware the ones with paid traffic), only the log was silenced…
Still, a small improvement, considering the log is on the non-volatile, wearable, memory…