On Fri, Nov 10, 2017 at 03:39:13AM +1100, Paul J R wrote: > The config on both is identical: > > refclock SHM 0 offset 0.395 delay 0.2 refid NMEA noselect > refclock PPS /dev/pps0 refid PPS poll 4 prefer lock NMEA > server 10.69.69.1 > > One cant seem to poll pps: > > root@ntp03:~# chronyc sources > 210 Number of sources = 3 > MS Name/IP address Stratum Poll Reach LastRx Last sample > =============================================================================== > #? NMEA 0 4 377 10 -264ms[ -264ms] +/- > 110ms > #? PPS 0 4 0 - +0ns[ +0ns] +/- 0ns > ^* 10.69.69.1 2 6 177 46 -4689ns[ -14us] +/- > 92ms
The offset of the NMEA source is probably too large to be locked with the PPS. You will need to adjust the offset value on the SHM line to bring it closer to UTC and allow PPS to lock. > And the other cant poll the server: > > root@ntp04:~# chronyc sources > 210 Number of sources = 3 > MS Name/IP address Stratum Poll Reach LastRx Last sample > =============================================================================== > #? NMEA 0 4 377 19 -24ms[ -24ms] +/- > 105ms > #* PPS 0 4 277 18 +39ns[ -5ns] +/- > 56ns > ^? 10.69.69.1 0 7 377 - +0ns[ +0ns] +/- > 0ns As a first step, it would be good to confirm that the server is responding. tcpdump-mini would be a good tool for that. :) If it does respond, then a second step would be to recompile chrony with debugging enabled, run chronyd with -d -d and see if there is anything interesting. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.