My stratum1 RPI server have a offset on about 3 ms if i see
https://www.pool.ntp.org/scores/92.246.24.228
It is GPS synced with NEO6M
Is it recomended that i move it to around 0 with
fudge 127.127.22.0 time1 0.003 refid kPPS
??
or shod i leave it where it is now ?
First check your ntpq -p output. If your ntpd sticks with GPS PPS signal well (offset and jitter both at microsecond level) then just leave it.
That seams ok - Here sample with 2 other ntp servers in internal dmz zone.
root@RPI001:/home/pi# ntpq -pcrv 192.168.1.1
remote refid st t when poll reach delay offset jitter
==============================================================================
oPPS(0) .kPPS. 0 l 2 16 377 0.000 0.000 0.001
SHM(0) .SHM. 15 l 4 16 377 0.000 4.813 1.373
*192.168.1.2 .kPPS. 1 u 19 64 377 0.140 0.000 0.003
+192.168.1.3 .kPPS. 1 u 33 64 377 0.142 -0.004 0.004
associd=0 status=014c leap_none, sync_pps, 4 events, clock_step,
version=“ntpd 4.2.8p13@1.3847-o Wed Aug 28 22:10:02 UTC 2019 (1)”,
processor=“armv7l”, system=“Linux/4.19.66-v7l+”, leap=00, stratum=1,
precision=-20, rootdelay=0.000, rootdisp=1.030, refid=kPPS,
reftime=e1231c56.0964fd4c Wed, Sep 11 2019 8:10:14.036,
clock=e1231c58.b26f7ca8 Wed, Sep 11 2019 8:10:16.697, peer=46470, tc=4,
mintc=3, offset=0.000486, frequency=-10.717, sys_jitter=0.000954,
clk_jitter=0.001, clk_wander=0.000, tai=37, leapsec=201701010000,
expire=201912280000
More stats on this server here (didt reset gps module at 23:00 cet = large peaks for sub ms change)
http://ntp.567.dk/stat/stat.php?prefix=rpi001&period=day&multi=1
I wouldn’t mess with it, 3ms is nothing over the internet, the difference is just asymmetrical delays that might be present between you and the monitor server… However that same delay might not be there for others closer to you, or could be totally different depending on network traffic.