Re: [chrony-users] Chrony and raw DCF receivers?
On Wed, 25 Oct 2017, V10lator wrote: Hi, I wanted to setup my own stratum 1 NTP server, so I wired a raw DCF77 receiver (127.127.8.0 mode 5 or 127.127.8.0 mode 6 with ntpd) to a SBC and tested a bit with ntpd. After some time I decided to give chrony a try as ntpd had too much shortcomings. Now chronyc is a complete show stopper as I can't find a way to tell it to read the DCF77 signal. There are only options for PPS (GPS receivers, I think). SHM also is no option as the only thing usable with this is radioclk but that seems to be for ntpd only: a) you will need some daemon to actually read the dcf77 signal. chronyd (not chronyc-- that is just a monitoring tool) does not have anything native. I know that originally when Lichvar took over he implimented a way to use the ntpd daemons to read the various refclocks and deliver those to chrony, but I neither remember or ever used that, and it may not have survived. b) dcf77 is a lousy refclock. It is only good to ms accuracy, because there is no way to compensate for the travel time of the signal, or the variations in that travel time produced by the ionosphere/clouds/... You get much better accuracy from network time signals, or using a cheap gps receiver. $ apt-get install radioclk Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libtomcrypt0 libtommath0 timelimit Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ntp Suggested packages: ntp-doc apparmor The following packages will be REMOVED: chrony The following NEW packages will be installed: ntp radioclk 0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded. Need to get 20.4 kB/485 kB of archives. After this operation, 910 kB of additional disk space will be used. You installed ntpd and removed chrony. So how to use chrony with a raw DCF77 receiver? There doesn't seem to be any info on the net other than -- 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. -- 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.
Re: [chrony-users] Possible bug in PPS support
Miroslav Lichvar wrote:
On Tue, Oct 24, 2017 at 11:14:21PM +0200, Rob Janssen wrote:
I am now monitoring the Root dispersion and this appears to work OK, after some
tweaking
of the threshold value. The reference time unfortunately is in a format that
is not easy to
check for "being recent" in a simple script, it would be nice if there was a
"seconds since epoch"
field as well (as there is in ntpd/ntpq).
With the -c option, which is available in newer chrony versions, the
reference timestamp is printed in "seconds since epoch".
$ chronyc -c tracking | awk -F , '{ print $4 }'
1508912704.491908798
Thanks! I have updated to 3.2 but not re-read the manpage.
This format is much easier to parse in our monitoring plugin, I'll rework it to
use this feature.
Rob
--
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.
Re: [chrony-users] Chrony and raw DCF receivers?
On Wed, Oct 25, 2017 at 09:04:29AM +0200, V10lator wrote: > Now chronyc is a complete show stopper as I can't find a way to tell it to > read the DCF77 signal. There are only options for PPS (GPS receivers, I > think). SHM also is no option as the only thing usable with this is radioclk > but that seems to be for ntpd only: radioclk should work with chrony. It uses the SHM protocol and doesn't care what NTP daemon is reading the measurements it makes. It seems it is just a packaging bug in the radioclk package that it depends on ntp (only): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863070 There is probably a way to force apt-get or dpkg to install the package without uninstalling chrony. -- 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.
[chrony-users] Chrony and raw DCF receivers?
Hi, I wanted to setup my own stratum 1 NTP server, so I wired a raw DCF77 receiver (127.127.8.0 mode 5 or 127.127.8.0 mode 6 with ntpd) to a SBC and tested a bit with ntpd. After some time I decided to give chrony a try as ntpd had too much shortcomings. Now chronyc is a complete show stopper as I can't find a way to tell it to read the DCF77 signal. There are only options for PPS (GPS receivers, I think). SHM also is no option as the only thing usable with this is radioclk but that seems to be for ntpd only: $ apt-get install radioclk Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libtomcrypt0 libtommath0 timelimit Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ntp Suggested packages: ntp-doc apparmor The following packages will be REMOVED: chrony The following NEW packages will be installed: ntp radioclk 0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded. Need to get 20.4 kB/485 kB of archives. After this operation, 910 kB of additional disk space will be used. So how to use chrony with a raw DCF77 receiver? There doesn't seem to be any info on the net other than -- 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.
Re: [chrony-users] Possible bug in PPS support
On Tue, Oct 24, 2017 at 11:14:21PM +0200, Rob Janssen wrote:
> I am now monitoring the Root dispersion and this appears to work OK, after
> some tweaking
> of the threshold value. The reference time unfortunately is in a format that
> is not easy to
> check for "being recent" in a simple script, it would be nice if there was a
> "seconds since epoch"
> field as well (as there is in ntpd/ntpq).
With the -c option, which is available in newer chrony versions, the
reference timestamp is printed in "seconds since epoch".
$ chronyc -c tracking | awk -F , '{ print $4 }'
1508912704.491908798
--
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.
