The officially official Devuan Forum!

rmrichesjr

Member

Registered: 2018-12-18

Posts: 33  

ntpsec not managing drift in Daedalus

Since switching from Chimaera to Daedalus ~10 days ago, ntpsec shows it's contacting the servers, but the offset grows by a fraction of a second per day.  It appears it's contacting the servers but not managing the drift, not controlling the clock.

The only changes I made from the Daedalus factory-supplied /etc/ntpsec/ntp.conf file is to comment out the pool entries and add two server entries in order to have consistency from one boot to the next.  These are my server entries:

server time.cloudflare.com nts
server oregon.time.system76.com nts

Doing "ntpq -p" shows this about 3 days after running "ntpdig -S" and restarting ntpsec::

     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
+time.cloudflare 10.119.8.155     3 8   33   64  377  10.5348 623.7458   0.5835
+oregon.time.sys 128.138.141.177  2 8   17   64  377  15.7338 627.3030   0.7425

Any suggestions to get ntpsec to put its hands on the steering wheel and drive?

aluma

Member

Registered: 2022-10-26

Posts: 646  

Re: ntpsec not managing drift in Daedalus

I would return the settings to default.

root@devuan:/# ntpq -p
     remote           refid      st t when poll reach   delay   offset   jitter
===============================================================================
 0.debian.pool.n .POOL.          16 p    -  256    0   0.0000   0.0000   0.0001
 1.debian.pool.n .POOL.          16 p    -  256    0   0.0000   0.0000   0.0001
 2.debian.pool.n .POOL.          16 p    -  256    0   0.0000   0.0000   0.0001
 3.debian.pool.n .POOL.          16 p    -  256    0   0.0000   0.0000   0.0001
+colopanel.ip-co 62.149.0.30      2 u   33   64    1  13.9472  10.8900   0.7619
+ip-194-8-146-38 176.119.234.201  2 u   33   64    1  19.9207  10.4313   1.0358
+dns2.campus-rv. 172.16.0.123     2 u   33   64    1  13.3203  10.6493   0.9095
#250-87-53-37.ip 17.253.52.253    2 u   33   64    1  24.2997   9.0034   0.9842
+vds13.ekvia.com 31.28.161.68     2 u   32   64    1   9.3963  10.4705   1.5244
-127-80-53-37.po 17.253.52.253    2 u   32   64    1  26.4528  10.0307   1.2853
*ntp2.time.in.ua .GPS.            1 u   32   64    1   9.5793  10.8549   1.5424
#rs-project.org  91.236.251.35    3 u   32   64    1  19.3035  12.0461   1.7449
 time.cloudflare .INIT.          16 u    -   64    0   0.0000   0.0000   0.0001
 2001:67c:440:f6 .INIT.          16 u    -   64    0   0.0000   0.0000   0.0001
 ntp.time.in.ua  .INIT.          16 u    -   64    0   0.0000   0.0000   0.0001
 2001:67c:440:40 .INIT.          16 u    -   64    0   0.0000   0.0000   0.0001
-time.cloudflare 10.73.9.90       3 u   31   64    1  24.7559  11.6499   1.2899
#212.1.104.9     193.106.144.7    3 u   31   64    1  17.5746  14.6227   1.5784
 nsb.lds.online  .INIT.          16 u    -   64    0   0.0000   0.0000   0.0001
#main14.ip-conne 118.188.39.164   2 u   34   64    1  12.0824   6.6504   1.5609
+134-249-228-3.b 105.240.56.33    2 u   33   64    1  18.3379  10.3437   1.8805
-ns2.infomir.com 105.240.56.33    2 u   33   64    1  18.4700   9.7698   1.6263
+mail.agrogradv. 130.149.17.8     2 u   33   64    1  13.1765   9.7552   2.1682
-ns3.as41781.pp. 129.134.28.123   2 u   33   64    1   8.8992  11.5566   1.9688
root@devuan:/#                   

rmrichesjr

Member

Registered: 2018-12-18

Posts: 33  

Re: ntpsec not managing drift in Daedalus

In case anyone with a similar question/problem finds this, there is another solution.  I commented out the "tos minclock 4 minsane 3" line, and it appears to work fine now.  I suspect if I had four individual servers declared in the file, I could have kept the "tos ..." line.