Re: [chrony-users] Time synchronisation over a high-latency packet radio network

[Chris Greenman]

Is there any possibility of using GPS for time?  I had a similar dilemma on
my raspberry pi based boat computer.  I didn't want to rely on internet
provided time since it might not be available if away from the slip.

On Tue, May 7, 2019, 11:30 AM Lonnie Abelbeck 
wrote:

>
>
> > On May 6, 2019, at 10:53 PM, Stuart Longland 
> wrote:
> >
> > Hi all,
> >
> > I've got a problem where I need to provide a time synchronisation
> > service for small embedded computers whose only link to the outside
> > world is a slow and high-latency packet radio network.
>
> Stuart, Indeed very interesting...
>
> > Below is my chronyd.conf:
> > - BEGIN chronyd.conf -
> > # Welcome to the chrony configuration file. See chrony.conf(5) for more
> > # information about usuable directives.
> > pool 2.debian.pool.ntp.org iburst
> >
> > # NTP proxy over APRS
> > server 127.0.0.1 port 3123 trust maxdelay 10 minpoll 3
>
> Just curious, it appears you have native DNS, why do you need to proxy NTP
> over APRS (unless you use a similar technique for DNS).
>
> BTW, at startup our project always steps the time using (8 second timeout
> would be too low for you):
> --
> chronyd -q -t 8 "server time.example.tld iburst"
> --
> before starting "chronyd" in the background. (no systemd).
>
> Lonnie
>
>
> --
> 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] Using symbolic network names in /etc/chrony.conf file?

[Chris Greenman]

When you specify a hostname, that's it. It's a 32bit address (ipv4 of
course).  Throwing a netmask on it does nothing except specify that your
network segment has 64,510 usable addresses.  Now if you edit /etc/networks
and add mynet 10.10.0.0 then you can use the mynet/16 notation in your
chrony.conf

On Jul 25, 2017 10:19 AM, "Miroslav Lichvar"  wrote:

> On Tue, Jul 25, 2017 at 08:37:18AM +0200, Miroslav Lichvar wrote:
> > On Mon, Jul 24, 2017 at 08:24:57PM +, Parker, Michael D. wrote:
> > > The chrony allow directive allows the addition of a symbolic hostname
> in its
> > > specification. However, I took a leap in entering the following
> directive:
> > >
> > > allow hostname/16
> > >
> > > which failed to do what I expected but no configuration file error was
> > > flagged.
> >
> > This is not supported. If allow/deny has a hostname, it always applies
> > to all 32 (for IPv4) or 128 bits (for IPv6).
>
> At least for now, I'll fix the parser to not allow slashes after
> hostnames in the allow/deny directives/commands.
>
> --
> 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.
>
>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Ok cool.I'll stick that refclock line in and call it good.

Thanks a bunch for all the help and tuning advise.   I might try and grab
some statistics during my race this week since I'll be on a cell phone LTE
hotspot which can get spotty in areas.

On Mon, Aug 22, 2016 at 4:26 AM, Miroslav Lichvar <mlich...@redhat.com>
wrote:

> On Fri, Aug 19, 2016 at 06:26:14PM -0400, Chris Greenman wrote:
> > Finally got a chance to grab more stats.my refclock line now looks
> like
> > this:
> >
> > refclock SHM 0 refid GPS offset 0.060 delay 0.22 minsamples 64
> >
> >
> > I'm attaching the latest stats.
>
> You might want to try something like this:
> refclock SHM 0 refid GPS offset 0.080 delay 0.2 minsamples 64
>
> That should move the offset closer to zero. It will be still moving
> around 10-20 milliseconds, but if your requirement was to keep the
> clock accurate to one second, I think it will be good enough.
>
> --
> 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.
>
>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

So how would i tell if my GPS does this and if so how do i get it
recognized by the kernel and gpsd?

On Fri, Aug 12, 2016 at 2:53 PM, Bill Unruh <un...@physics.ubc.ca> wrote:

> On Fri, 12 Aug 2016, Chris Greenman wrote:
>
> it's a usb puck.  so no.  Actually I haven't actually looked but typical
>> USB is +5v data+ data- and gnd.  As
>> far as I know the only place the pps signal is available is inside the
>> puck between the GPS module and the usb
>> interface.
>>
>
> Well, usb serial immitatiors can also immitate the control lines from a
> serial
> line. Thus one of the usb packets can be a simlation of the PPS signalalong
> the appropriate serial line.  But those are likely to have far worse
> behaviour than the actual lines.
> It might however be better than the data phrases usually coming along the
> serial line.
>
>
>
>
>>  like I said I COULD crack it open and run a new cable that included the
>> pps line.
>>
>> On Fri, Aug 12, 2016 at 2:24 PM, Bill Unruh <un...@physics.ubc.ca> wrote:
>>
>>
>>   William G. Unruh __| Canadian Institute for| Tel:
>> +1(604)822-3273
>>   Physics _|___ Advanced Research _| Fax:
>> +1(604)822-5324
>>   UBC, Vancouver,BC _|_ Program in Cosmology |
>> un...@physics.ubc.ca
>>   Canada V6T 1Z1 | and Gravity __|_
>> www.theory.physics.ubc.ca/
>>
>>   On Fri, 12 Aug 2016, Chris Greenman wrote:
>>
>> I CAN hook it up for PPS but it will require cracking open
>> the puck and it's not that
>> crucial for my use
>> anyway.
>>
>>
>>   Isn't there an output line from the puck which carries the PPS
>> signal?
>>
>>
>>
>>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Ok  I grabbed a sample of the clock statistics.



On Fri, Aug 12, 2016 at 2:53 PM, Bill Unruh <un...@physics.ubc.ca> wrote:

> On Fri, 12 Aug 2016, Chris Greenman wrote:
>
> it's a usb puck.  so no.  Actually I haven't actually looked but typical
>> USB is +5v data+ data- and gnd.  As
>> far as I know the only place the pps signal is available is inside the
>> puck between the GPS module and the usb
>> interface.
>>
>
> Well, usb serial immitatiors can also immitate the control lines from a
> serial
> line. Thus one of the usb packets can be a simlation of the PPS signalalong
> the appropriate serial line.  But those are likely to have far worse
> behaviour than the actual lines.
> It might however be better than the data phrases usually coming along the
> serial line.
>
>
>
>
>>  like I said I COULD crack it open and run a new cable that included the
>> pps line.
>>
>> On Fri, Aug 12, 2016 at 2:24 PM, Bill Unruh <un...@physics.ubc.ca> wrote:
>>
>>
>>   William G. Unruh __| Canadian Institute for| Tel:
>> +1(604)822-3273
>>   Physics _|___ Advanced Research _| Fax:
>> +1(604)822-5324
>>   UBC, Vancouver,BC _|_ Program in Cosmology |
>> un...@physics.ubc.ca
>>   Canada V6T 1Z1 | and Gravity __|_
>> www.theory.physics.ubc.ca/
>>
>>   On Fri, 12 Aug 2016, Chris Greenman wrote:
>>
>> I CAN hook it up for PPS but it will require cracking open
>> the puck and it's not that
>> crucial for my use
>> anyway.
>>
>>
>>   Isn't there an output line from the puck which carries the PPS
>> signal?
>>
>>
>>
>>


statistics.tgz
Description: GNU Zip compressed data

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Ok I set it to 0.0065 offset.  Here's my chrony.conf

pool pool.ntp.org
driftfile /var/lib/chrony/drift
allow
refclock SHM 0 refid GPS offset 0.065
#refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
makestep 1 -1

and here is the chrony sources output:

irishmistii@IrishMistII:~ $ chronyc sources
210 Number of sources = 5
MS Name/IP address Stratum Poll Reach LastRx Last sample

===
#* GPS   0   4   37712  +2112us[+2967us] +/-
 325us
^- orchid.sidereal.ca2   61719+11ms[  +12ms] +/-
40ms
^- static-96-244-96-19.bltmm 2   61719+11ms[  +12ms] +/-
40ms
^- hydrogen.constant.com 2   61718+14ms[  +15ms] +/-
32ms
^- host2.kingrst.com 2   61519  +9078us[  +10ms] +/-
 100ms
irishmistii@IrishMistII:~ $ chronyc sources
210 Number of sources = 5
MS Name/IP address Stratum Poll Reach LastRx Last sample

===
#* GPS   0   4   377 9   +132us[ +236us] +/-
 339us
^- orchid.sidereal.ca2   61750  +9849us[  +12ms] +/-
40ms
^- static-96-244-96-19.bltmm 2   61751  +9227us[  +12ms] +/-
40ms
^- hydrogen.constant.com 2   61750+13ms[  +15ms] +/-
32ms
^- host2.kingrst.com 2   61551  +7529us[  +10ms] +/-
 100ms
irishmistii@IrishMistII:~ $ chronyc sources
210 Number of sources = 5
MS Name/IP address Stratum Poll Reach LastRx Last sample

===
#* GPS   0   4   377 9  +2596us[+3043us] +/-
 464us
^- orchid.sidereal.ca2   63713+14ms[  +14ms] +/-
39ms
^- static-96-244-96-19.bltmm 2   63713  +9722us[  +10ms] +/-
44ms
^- hydrogen.constant.com 2   63713+14ms[  +14ms] +/-
33ms
^- host2.kingrst.com 2   61578  +6938us[  +10ms] +/-
 100ms




On Tue, Aug 9, 2016 at 9:25 AM, Bill Unruh <un...@physics.ubc.ca> wrote:

> So GPS is what the system is using to set the time. clockb.ntpis.org is
> not
> responding at all. The other three have responded three times, and have not
> been queried again during the very brief time you have make these tests.
> They claim that your system time is out by about 60-70ms so you might want
> to use
> that as an offset for the GPS clock.
>
> I have no idea why clockb is claiming to be stratum 0 except that that is
> probably the default stratum if the remote clock is unreachable. I would
> have
> thought 15 was a more reasonable value for that, but
>
>
>
> On Tue, 9 Aug 2016, Chris Greenman wrote:
>
> Ok   I took out the offset, precision, and delay.  I let everything
>> stabilize a bit and then took 3 samples.
>> Here's what it came up with.
>> $ date && chronyc sources
>> Tue  9 Aug 08:54:52 EDT 2016
>> 210 Number of sources = 5
>> MS Name/IP address Stratum Poll Reach LastRx Last sample
>>
>> 
>> ===
>> #* GPS   0   4   37715  +1479us[+1575us] +/-
>>  522us
>> ^? clockb.ntpjs.org  0   6 0 - +0ns[   +0ns] +/-
>>0ns
>> ^- proxmox.undeadarmy.com2   6 7 8-63ms[  -63ms] +/-
>>   87ms
>> ^- host2.kingrst.com 2   6 7 9-72ms[  -72ms] +/-
>>   91ms
>> ^- clock.xmission.com1   6 7 8-65ms[  -65ms] +/-
>>   41ms
>>
>> irishmistii@IrishMistII:~ $ date && chronyc sources
>> Tue  9 Aug 08:55:00 EDT 2016
>> 210 Number of sources = 5
>> MS Name/IP address Stratum Poll Reach LastRx Last sample
>>
>> 
>> ===
>> #* GPS   0   4   37712   -606us[-1568us] +/-
>>  422us
>> ^? clockb.ntpjs.org  0   6 0 - +0ns[   +0ns] +/-
>>0ns
>> ^- proxmox.undeadarmy.com2   6 716-62ms[  -63ms] +/-
>>   87ms
>> ^- host2.kingrst.com 2   6 716-71ms[  -72ms] +/-
>>   91ms
>> ^- clock.xmission.com1   6 716-64ms[  -65ms] +/-
>>   41ms
>>
>> irishmistii@IrishMistII:~ $ date && chronyc sources
>> Tue  9 Aug 08:55:08 EDT 2016
>> 210 Number of sources = 5
>> MS Name/IP address Stratum Poll Reach LastRx Last sample
>>
>> 
>> ===
>> #* GPS

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Thanks.  I already enabled my NTP sources and you're right, the gps is
getting marked as bad.  I'll play with that today.

Chris

On Aug 9, 2016 4:42 AM, "Miroslav Lichvar" <mlich...@redhat.com> wrote:

> On Mon, Aug 08, 2016 at 01:21:56PM -0400, Chris Greenman wrote:
> > 210 Number of sources = 1
> > MS Name/IP address Stratum Poll Reach LastRx Last sample
> >
> > 
> ===
> > #* GPS   0   4   37717   +296us[ +347us] +/-
> >  200ms
> >
> >
> > I am perfectly happy with 200ms error in time.   That more than suits my
> > needs.
>
> You might want to try this with some NTP sources and see how accurate
> is the GPS time source. From that you would adjust the offset value on
> the refclock SHM line so the the error is reduced and the GPS source
> is not marked as a falseticker when there are other source. I'd also
> suggest to add "minsamples 64" to the refclock directive, so chronyd
> doesn't try to follow short-term variations in the measured offset
> (the error in the message based GPS time tends to be non-random).
>
> --
> 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.
>
>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

UGH!!!I really wish distros would provide software that is more up to
date.Looks like it might have been gpsd.

On a whim I decided to scrap the repo provided gpsd AND chrony and compiled
everything myself.  it now appears as if everything is working.

chrony sources output:

210 Number of sources = 1
MS Name/IP address Stratum Poll Reach LastRx Last sample

===
#* GPS   0   4   37717   +296us[ +347us] +/-
 200ms


I am perfectly happy with 200ms error in time.   That more than suits my
needs.

Sorry for wasting everyone's time.I was trying to save time and
frustration by using the repo supplied (and you would think tested)
binaries.   It would have been a lot quicker and less frustrating to just
compile.  lol.

On Mon, Aug 8, 2016 at 11:50 AM, Chris Greenman <chris.m.green...@gmail.com>
wrote:

> Ok,  Here are the latest strace files.  It looks like the chrony in the
> Jessie repos does not have debug compiled in.  I downloaded the latest
> source and compiled.  The trace is using that binary not the distro
> supplied (Ver. 1.30).  I should note that I already tried the fresh
> compiled version before and got the same results as the distro version.
>
>
>
> On Mon, Aug 8, 2016 at 9:19 AM, Miroslav Lichvar <mlich...@redhat.com>
> wrote:
>
>> On Mon, Aug 08, 2016 at 09:05:03AM -0400, Chris Greenman wrote:
>> > I didn't think the -F option was correct but it didn't seem to work
>> without
>> > it either.  I was just hunting and pecking.  My gps does not (directly)
>> > provide PPS.  It's a ublox 6 so I could probably wire it in but to be
>> > honest, I don't need that much precision.  For my needs NTP is accurate
>> > enough but it's not always available which is why I want time from GPS.
>>
>> Note that GPS without PPS is typically less stable than NTP over
>> internet. Binary mode may work better than NMEA.
>>
>> > As
>> > for the dependencies and starting order, that's easy to fix.  Right now
>> > gpsd is starting from init.d and chrony is starting from systemd.  I can
>> > just remove the rc#.d links and write a new .service file for gpsd with
>> > "After = chrony.service" and "Wanted by = default.target".  Then verify
>> the
>> > chrony service file jives with the one for gpsd.
>>
>> With SHM refclock that shouldn't be necessary. Only for SOCK chronyd
>> needs to be started first.
>>
>> > The last gps strace I posted was with the -D 8 option specified.   I did
>> > not, however, specify -f to strace so it is not following after it
>> forks.
>>
>> The -N option disables forking. Another useful option is -n, which
>> tells gpsd to not wait for clients, so SHM is always updated.
>>
>> > As soon as I get some play time today I'll run some new traces.  Is
>> > attaching the best way to send the files or is there a bit bucket
>> somewhere
>> > I should use?
>>
>> I think it's ok to post here if it's not too large (e.g. > 100KB). Or
>> you can compress it first.
>>
>> --
>> 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.
>>
>>
>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Ok,  Here are the latest strace files.  It looks like the chrony in the
Jessie repos does not have debug compiled in.  I downloaded the latest
source and compiled.  The trace is using that binary not the distro
supplied (Ver. 1.30).  I should note that I already tried the fresh
compiled version before and got the same results as the distro version.



On Mon, Aug 8, 2016 at 9:19 AM, Miroslav Lichvar <mlich...@redhat.com>
wrote:

> On Mon, Aug 08, 2016 at 09:05:03AM -0400, Chris Greenman wrote:
> > I didn't think the -F option was correct but it didn't seem to work
> without
> > it either.  I was just hunting and pecking.  My gps does not (directly)
> > provide PPS.  It's a ublox 6 so I could probably wire it in but to be
> > honest, I don't need that much precision.  For my needs NTP is accurate
> > enough but it's not always available which is why I want time from GPS.
>
> Note that GPS without PPS is typically less stable than NTP over
> internet. Binary mode may work better than NMEA.
>
> > As
> > for the dependencies and starting order, that's easy to fix.  Right now
> > gpsd is starting from init.d and chrony is starting from systemd.  I can
> > just remove the rc#.d links and write a new .service file for gpsd with
> > "After = chrony.service" and "Wanted by = default.target".  Then verify
> the
> > chrony service file jives with the one for gpsd.
>
> With SHM refclock that shouldn't be necessary. Only for SOCK chronyd
> needs to be started first.
>
> > The last gps strace I posted was with the -D 8 option specified.   I did
> > not, however, specify -f to strace so it is not following after it forks.
>
> The -N option disables forking. Another useful option is -n, which
> tells gpsd to not wait for clients, so SHM is always updated.
>
> > As soon as I get some play time today I'll run some new traces.  Is
> > attaching the best way to send the files or is there a bit bucket
> somewhere
> > I should use?
>
> I think it's ok to post here if it's not too large (e.g. > 100KB). Or
> you can compress it first.
>
> --
> 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.
>
>


straces.tgz
Description: GNU Zip compressed data

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

I've attached the strace files.   The commands I used were:

root@IrishMistII:/tmp# strace -o /tmp/chrony.strace.out chronyd
root@IrishMistII:/tmp# strace -o /tmp/gpsd.strace.out gpsd -D 8 -F
/var/run/chrony.ttyACM0.sock /dev/ttyACM0

On Aug 7, 2016 12:50 AM, "Steve Horton" <stevejhor...@gmail.com> wrote:

> We need to see if gpsd is sending and if chrony is rx anything on that
> socket. I'd start both process in strace to srart. Then maybe start gpsd in
> debug -D 8 and see if its writing to that chrony socket. Strace will show
> what's happening underneath.
>
> On Aug 6, 2016 11:37 PM, "Chris Greenman" <chris.m.green...@gmail.com>
> wrote:
>
>> $ file /var/run/chrony.ttyACM0.sock
>> /var/run/chrony.ttyACM0.sock: socket
>>
>> cat /etc/init.d/gpsd
>>
>> $ cat /etc/init.d/gpsd
>> #!/bin/sh
>> ### BEGIN INIT INFO
>> # Provides:  gpsd
>> # Required-Start:$remote_fs $syslog $network
>> # Should-Start:  bluetooth dbus udev
>> # Required-Stop: $remote_fs $syslog $network
>> # Default-Start: 2 3 4 5
>> # Default-Stop:  0 1 6
>> # X-Start-Before:ntp
>> # Short-Description: GPS (Global Positioning System) daemon
>> # Description:   The gpsd service daemon is able to monitor one or
>> #more GPS devices connected to a host computer, making
>> #all data on the location and movements of the sensors
>> #available to be queried on TCP port 2947.
>> ### END INIT INFO
>>
>> # Author: Bernd Zeimetz <b...@debian.org>
>> #
>> # Please remove the "Author" lines above and replace them
>> # with your own name if you copy and modify this script.
>>
>> # Do NOT "set -e"
>>
>> # PATH should only include /usr/* if it runs after the mountnfs.sh script
>> RUNDIR=/run/gpsd
>> PATH=/sbin:/usr/sbin:/bin:/usr/bin
>> DESC="GPS (Global Positioning System) daemon"
>> NAME=gpsd
>> DAEMON=/usr/sbin/$NAME
>> PIDFILE=$RUNDIR/$NAME.pid
>> SCRIPTNAME=/etc/init.d/$NAME
>>
>> # Exit if the package is not installed
>> [ -x "$DAEMON" ] || exit 0
>>
>> # Read configuration variable file if it is present
>> [ -r /etc/default/$NAME ] && . /etc/default/$NAME
>>
>> if [ -z "$GPSD_SOCKET" ] && [ -z "$DEVICES" ]; then
>> GPSD_SOCKET=/var/run/gpsd.sock
>> fi
>>
>> if [ -n "$GPSD_SOCKET" ]; then
>> GPSD_OPTIONS="$GPSD_OPTIONS -F $GPSD_SOCKET"
>> fi
>>
>> # Load the VERBOSE setting and other rcS variables
>> . /lib/init/vars.sh
>>
>> # Define LSB log_* functions.
>> # Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
>> . /lib/lsb/init-functions
>>
>> #
>> # Function that starts the daemon/service
>> #
>> do_start()
>> {
>> # Return
>> #   0 if daemon has been started
>> #   1 if daemon was already running
>> #   2 if daemon could not be started
>>
>> mkdir -p $RUNDIR || return 2
>>
>> start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON
>> --test > /dev/null \
>> || return 1
>> start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
>> $GPSD_OPTIONS -P $PIDFILE $DEVICES \
>> || return 2
>> }
>>
>> #
>> # Function that stops the daemon/service
>> #
>> do_stop()
>> {
>> # Return
>> #   0 if daemon has been stopped
>> #   1 if daemon was already stopped
>> #   2 if daemon could not be stopped
>> #   other if a failure occurred
>> start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
>> $PIDFILE --name $NAME
>> RETVAL="$?"
>> [ "$RETVAL" = 2 ] && return 2
>> # Many daemons don't delete their pidfiles when they exit.
>> rm -f $PIDFILE
>> return "$RETVAL"
>> }
>>
>> #
>> # Function that sends a SIGHUP to the daemon/service
>> #
>> do_reload() {
>> #
>> # If the daemon can reload its configuration without
>> # restarting (for example, when it is sent a SIGHUP),
>> # then implement that here.
>> #
>> start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name
>> $NAME
>> return 0
>> }
>>
>> case "$1" in
>>   start)
>> if [ "$START_DAEMON" = "true" ]; then
>> [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
>> d

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

$ file /var/run/chrony.ttyACM0.sock
/var/run/chrony.ttyACM0.sock: socket

cat /etc/init.d/gpsd

$ cat /etc/init.d/gpsd
#!/bin/sh
### BEGIN INIT INFO
# Provides:  gpsd
# Required-Start:$remote_fs $syslog $network
# Should-Start:  bluetooth dbus udev
# Required-Stop: $remote_fs $syslog $network
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# X-Start-Before:ntp
# Short-Description: GPS (Global Positioning System) daemon
# Description:   The gpsd service daemon is able to monitor one or
#more GPS devices connected to a host computer, making
#all data on the location and movements of the sensors
#available to be queried on TCP port 2947.
### END INIT INFO

# Author: Bernd Zeimetz <b...@debian.org>
#
# Please remove the "Author" lines above and replace them
# with your own name if you copy and modify this script.

# Do NOT "set -e"

# PATH should only include /usr/* if it runs after the mountnfs.sh script
RUNDIR=/run/gpsd
PATH=/sbin:/usr/sbin:/bin:/usr/bin
DESC="GPS (Global Positioning System) daemon"
NAME=gpsd
DAEMON=/usr/sbin/$NAME
PIDFILE=$RUNDIR/$NAME.pid
SCRIPTNAME=/etc/init.d/$NAME

# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0

# Read configuration variable file if it is present
[ -r /etc/default/$NAME ] && . /etc/default/$NAME

if [ -z "$GPSD_SOCKET" ] && [ -z "$DEVICES" ]; then
GPSD_SOCKET=/var/run/gpsd.sock
fi

if [ -n "$GPSD_SOCKET" ]; then
GPSD_OPTIONS="$GPSD_OPTIONS -F $GPSD_SOCKET"
fi

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

#
# Function that starts the daemon/service
#
do_start()
{
# Return
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started

mkdir -p $RUNDIR || return 2

start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
|| return 1
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
$GPSD_OPTIONS -P $PIDFILE $DEVICES \
|| return 2
}

#
# Function that stops the daemon/service
#
do_stop()
{
# Return
#   0 if daemon has been stopped
#   1 if daemon was already stopped
#   2 if daemon could not be stopped
#   other if a failure occurred
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE
--name $NAME
RETVAL="$?"
[ "$RETVAL" = 2 ] && return 2
# Many daemons don't delete their pidfiles when they exit.
rm -f $PIDFILE
return "$RETVAL"
}

#
# Function that sends a SIGHUP to the daemon/service
#
do_reload() {
#
# If the daemon can reload its configuration without
# restarting (for example, when it is sent a SIGHUP),
# then implement that here.
#
start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
return 0
}

case "$1" in
  start)
if [ "$START_DAEMON" = "true" ]; then
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
do_start
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
else
[ "$VERBOSE" != no ] && \
log_daemon_msg "Not starting $DESC" "$NAME" && \
log_end_msg 0
fi
;;
  stop)
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
do_stop
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
esac
;;
  status)
   status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
   ;;
  reload|force-reload)
log_daemon_msg "Reloading $DESC" "$NAME"
do_reload
log_end_msg $?
;;
  restart)
#
# If the "reload" option is implemented then remove the
# 'force-reload' alias
#
log_daemon_msg "Restarting $DESC" "$NAME"
do_stop
case "$?" in
 0|1)
do_start
case "$?" in
0) log_end_msg 0 ;;
1) log_end_msg 1 ;; # Old process is still running
*) log_end_msg 1 ;; # Failed to start
esac
;;
 *)
# Failed to stop
log_end_msg 1
;;
esac
;;
  *)
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac

:



On Sat, Aug 6, 2016 at 11:08 PM, Steve Horton <stevejhor...@gmail.com>
wrote:

> Sorry..i meant your start script. So do you start gpsd after chrony is
> allready running and the sock created? Does it get built correctly? Can you
> do a file on it?
>
> On Aug 6, 2016 10:29 PM, "Chris Greenman" <chris.m.green...@gmail.com>
> wrote:
>
>> No gpsd.conf.  /etc/default/gpsd is :
&

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

No gpsd.conf.  /etc/default/gpsd is :

# Default settings for the gpsd init script and the hotplug wrapper.

# Start the gpsd daemon automatically at boot time
START_DAEMON="true"

# Use USB hotplugging to add new USB devices automatically to the daemon
USBAUTO="true"

# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES="/dev/ttyACM0"

# Other options you want to pass to gpsd
GPSD_OPTIONS="-F /var/run/chrony.ttyACM0.sock"



$ ps -ef |grep gpsd |grep -v grep
gpsd 31426 1  0 13:36 ?00:00:00 /usr/sbin/gpsd -N -F
/var/run/chrony.ttyACM0.sock /dev/ttyACM0

cgps shows 3d fix

On Sat, Aug 6, 2016 at 2:11 PM, Steve Horton <stevejhor...@gmail.com> wrote:

> Ok..can I see your gpsd conf?
>
> On Aug 6, 2016 1:39 PM, "Chris Greenman" <chris.m.green...@gmail.com>
> wrote:
>
>> I only included the relevant lines.  When the socket didn't work either I
>> commented it out and went back to shm
>>
>> Here is my full chrony.conf.  Note, I commented out the ntp servers so
>> that I can just concentrate on troubleshooting the GPS clock and
>> uncommented the SOCK line
>>
>>
>> #server 0.us.pool.ntp.org
>> #server 1.us.pool.ntp.org
>> #server 2.us.pool.ntp.org
>> #server 3.us.pool.ntp.org
>>
>> driftfile /var/lib/chrony/drift
>>
>> allow
>>
>> # set larger delay to allow the NMEA source to overlap with
>> # the other sources and avoid the falseticker status
>> refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
>> #refclock SHM 1 refid PPS precision 1e-9
>> refclock SOCK /var/run/chrony.ttyACM0.sock refid GPSS
>>
>> makestep 1 -1
>>
>>
>>
>>
>> On Sat, Aug 6, 2016 at 10:41 AM, Steve Horton <stevejhor...@gmail.com>
>> wrote:
>>
>>> Not really Chris. I don't see a sock option in your configuration file.
>>> Gpsd should write time out to a device file some where and chrony can read
>>> the time from that device file via a Unix domain socket. Like I said..look
>>> into the sock option  and how it relates to gpsd.
>>>
>>> On Aug 6, 2016 10:10 AM, "Chris Greenman" <chris.m.green...@gmail.com>
>>> wrote:
>>>
>>>> Same thing.  Already tried it.
>>>>
>>>> On Aug 6, 2016 6:35 AM, "Steve Horton" <stevejhor...@gmail.com> wrote:
>>>>
>>>>> I'd look closer at the SOCK option under the refclock section.
>>>>> https://chrony.tuxfamily.org/manual.html#refclock-directive
>>>>>
>>>>> On Aug 6, 2016 12:00 AM, "Chris Greenman" <chris.m.green...@gmail.com>
>>>>> wrote:
>>>>> >
>>>>> > Hello,
>>>>> > I'm having an issue with getting time from gpsd.
>>>>> >
>>>>> > My setup is:
>>>>> > Raspberry Pi 3 running Jessie Lite
>>>>> > USB U-Blox gps
>>>>> >
>>>>> > gpsd is receiving NMEA from the GPS, cgps also shows time and
>>>>> position properly.
>>>>> >
>>>>> > My chrony.conf is:
>>>>> >>
>>>>> >> server 0.us.pool.ntp.org
>>>>> >> server 1.us.pool.ntp.org
>>>>> >> server 2.us.pool.ntp.org
>>>>> >> server 3.us.pool.ntp.org
>>>>> >> driftfile /var/lib/chrony/drift
>>>>> >> allow
>>>>> >> refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
>>>>> >> makestep 1 -1
>>>>> >>
>>>>> > Chronyc sources shows this:
>>>>> >>
>>>>> >> $ chronyc sources
>>>>> >> 210 Number of sources = 5
>>>>> >> MS Name/IP address Stratum Poll Reach LastRx Last sample
>>>>> >> 
>>>>> ===
>>>>> >> #? GPS   0   4 0   10y +0ns[
>>>>> +0ns] +/-0ns
>>>>> >> ^+ time-c.nist.gov   1   9   375   110-23ms[
>>>>>  -22ms] +/-   47ms
>>>>> >> ^* pool-96-248-122-64.cmdnnj 1  10   37756  +9749us[
>>>>>  +11ms] +/-   18ms
>>>>> >> ^- 104.156.99.2262   9   377   367+15ms[
>>>>>  +17ms] +/-  107ms
>>>>> >> ^- 4.53.160.75
>>>>> >>
>>>>> > This system is going to be used on a boat and might not have
>>>>> internet.  I can tell that both programs are accessing the shared memory
>>>>> using ipcs -m:
>>>>> >
>>>>> >> -- Shared Memory Segments 
>>>>> >> keyshmid  owner  perms  bytes  nattch
>>>>> status
>>>>> >> 0x4e545030 0  root   60080 2
>>>>>
>>>>> >> 0x4e545031 32769  root   60080 1
>>>>> >>
>>>>> > Any idea why chrony isn't getting time from the GPS?
>>>>> >
>>>>> > Thanks
>>>>>
>>>>
>>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Nothing in /dev/shm.   I added the log entries to chrony.conf but there is
no /var/log/chrony/refclocks file.

here is the latest chrony.conf.

#server 0.us.pool.ntp.org
#server 1.us.pool.ntp.org
#server 2.us.pool.ntp.org
#server 3.us.pool.ntp.org

driftfile /var/lib/chrony/drift

allow

# set larger delay to allow the NMEA source to overlap with
# the other sources and avoid the falseticker status
refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
#refclock SHM 1 refid PPS precision 1e-9
refclock SOCK /var/run/chrony.ttyACM0.sock refid GPSS

makestep 1 -1

logdir /var/log/chrony
log refclocks

after making the mods I restarted chrony.  here is the chronyc sources
output

210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
#? GPS   0   4 0   10y +0ns[   +0ns] +/-
 0ns
#? GPSS  0   4 0   10y +0ns[   +0ns] +/-
 0ns


ps -ef |grep gpsd |grep -v grep
gpsd 31426 1  0 13:36 ?00:00:00 /usr/sbin/gpsd -N -F
/var/run/chrony.ttyACM0.sock /dev/ttyACM0



On Sat, Aug 6, 2016 at 11:48 AM, Steve Horton <stevejhor...@gmail.com>
wrote:

> Agreed. Shms live in /dev along with the real time clocks /dev/rtc0. Your
> kernel config dictates what's there. Look around in dev and see what shms
> are there and mod your chrony configuration to point to one of them and
> check tracking. I'd also comment out all server lines until you get it
> syncing with the GPS device.
>
> On Aug 6, 2016 11:18 AM, "Bill Unruh" <un...@physics.ubc.ca> wrote:
>
>> shm should also work. Question is if they are reading the same shm
>> location.
>>
>>
>>
>>
>> William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
>> Physics _|___ Advanced Research _| Fax: +1(604)822-5324
>> UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
>> Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
>>
>> On Sat, 6 Aug 2016, Steve Horton wrote:
>>
>>
>>> Not really Chris. I don't see a sock option in your configuration file.
>>> Gpsd should write time out to a device
>>> file some where and chrony can read the time from that device file via a
>>> Unix domain socket. Like I said..look
>>> into the sock option  and how it relates to gpsd.
>>>
>>>
>>> On Aug 6, 2016 10:10 AM, "Chris Greenman" <chris.m.green...@gmail.com>
>>> wrote:
>>>
>>>   Same thing.  Already tried it.
>>>
>>>
>>>   On Aug 6, 2016 6:35 AM, "Steve Horton" <stevejhor...@gmail.com>
>>> wrote:
>>>
>>> I'd look closer at the SOCK option under the refclock
>>> section.
>>> https://chrony.tuxfamily.org/manual.html#refclock-directive
>>>
>>> On Aug 6, 2016 12:00 AM, "Chris Greenman" <
>>> chris.m.green...@gmail.com> wrote:
>>> >
>>> > Hello,
>>> > I'm having an issue with getting time from gpsd.
>>> >
>>> > My setup is:
>>> > Raspberry Pi 3 running Jessie Lite
>>> > USB U-Blox gps
>>> >
>>> > gpsd is receiving NMEA from the GPS, cgps also shows time
>>> and position properly.
>>> >
>>> > My chrony.conf is:
>>> >>
>>> >> server 0.us.pool.ntp.org
>>> >> server 1.us.pool.ntp.org
>>> >> server 2.us.pool.ntp.org
>>> >> server 3.us.pool.ntp.org
>>> >> driftfile /var/lib/chrony/drift
>>> >> allow
>>> >> refclock SHM 0 refid GPS precision 1e-1 offset 0.
>>> delay 0.2
>>> >> makestep 1 -1
>>> >>
>>> > Chronyc sources shows this:
>>> >>
>>> >> $ chronyc sources
>>> >> 210 Number of sources = 5
>>> >> MS Name/IP address Stratum Poll Reach LastRx Last
>>> sample
>>> >> ==
>>> =
>>> >> #? GPS   0   4 0   10y
>>> +0ns[   +0ns] +/-0ns
>>> >> ^+ 

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

I only included the relevant lines.  When the socket didn't work either I
commented it out and went back to shm

Here is my full chrony.conf.  Note, I commented out the ntp servers so that
I can just concentrate on troubleshooting the GPS clock and uncommented the
SOCK line


#server 0.us.pool.ntp.org
#server 1.us.pool.ntp.org
#server 2.us.pool.ntp.org
#server 3.us.pool.ntp.org

driftfile /var/lib/chrony/drift

allow

# set larger delay to allow the NMEA source to overlap with
# the other sources and avoid the falseticker status
refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
#refclock SHM 1 refid PPS precision 1e-9
refclock SOCK /var/run/chrony.ttyACM0.sock refid GPSS

makestep 1 -1




On Sat, Aug 6, 2016 at 10:41 AM, Steve Horton <stevejhor...@gmail.com>
wrote:

> Not really Chris. I don't see a sock option in your configuration file.
> Gpsd should write time out to a device file some where and chrony can read
> the time from that device file via a Unix domain socket. Like I said..look
> into the sock option  and how it relates to gpsd.
>
> On Aug 6, 2016 10:10 AM, "Chris Greenman" <chris.m.green...@gmail.com>
> wrote:
>
>> Same thing.  Already tried it.
>>
>> On Aug 6, 2016 6:35 AM, "Steve Horton" <stevejhor...@gmail.com> wrote:
>>
>>> I'd look closer at the SOCK option under the refclock section.
>>> https://chrony.tuxfamily.org/manual.html#refclock-directive
>>>
>>> On Aug 6, 2016 12:00 AM, "Chris Greenman" <chris.m.green...@gmail.com>
>>> wrote:
>>> >
>>> > Hello,
>>> > I'm having an issue with getting time from gpsd.
>>> >
>>> > My setup is:
>>> > Raspberry Pi 3 running Jessie Lite
>>> > USB U-Blox gps
>>> >
>>> > gpsd is receiving NMEA from the GPS, cgps also shows time and position
>>> properly.
>>> >
>>> > My chrony.conf is:
>>> >>
>>> >> server 0.us.pool.ntp.org
>>> >> server 1.us.pool.ntp.org
>>> >> server 2.us.pool.ntp.org
>>> >> server 3.us.pool.ntp.org
>>> >> driftfile /var/lib/chrony/drift
>>> >> allow
>>> >> refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
>>> >> makestep 1 -1
>>> >>
>>> > Chronyc sources shows this:
>>> >>
>>> >> $ chronyc sources
>>> >> 210 Number of sources = 5
>>> >> MS Name/IP address Stratum Poll Reach LastRx Last sample
>>> >> 
>>> ===
>>> >> #? GPS   0   4 0   10y +0ns[   +0ns]
>>> +/-0ns
>>> >> ^+ time-c.nist.gov   1   9   375   110-23ms[  -22ms]
>>> +/-   47ms
>>> >> ^* pool-96-248-122-64.cmdnnj 1  10   37756  +9749us[  +11ms]
>>> +/-   18ms
>>> >> ^- 104.156.99.2262   9   377   367+15ms[  +17ms]
>>> +/-  107ms
>>> >> ^- 4.53.160.75
>>> >>
>>> > This system is going to be used on a boat and might not have
>>> internet.  I can tell that both programs are accessing the shared memory
>>> using ipcs -m:
>>> >
>>> >> -- Shared Memory Segments 
>>> >> keyshmid  owner  perms  bytes  nattch
>>> status
>>> >> 0x4e545030 0  root   60080 2
>>>
>>> >> 0x4e545031 32769  root   60080 1
>>> >>
>>> > Any idea why chrony isn't getting time from the GPS?
>>> >
>>> > Thanks
>>>
>>

Re: [chrony-users] Not getting time from gpsd

[Chris Greenman]

Same thing.  Already tried it.

On Aug 6, 2016 6:35 AM, "Steve Horton" <stevejhor...@gmail.com> wrote:

> I'd look closer at the SOCK option under the refclock section.
> https://chrony.tuxfamily.org/manual.html#refclock-directive
>
> On Aug 6, 2016 12:00 AM, "Chris Greenman" <chris.m.green...@gmail.com>
> wrote:
> >
> > Hello,
> > I'm having an issue with getting time from gpsd.
> >
> > My setup is:
> > Raspberry Pi 3 running Jessie Lite
> > USB U-Blox gps
> >
> > gpsd is receiving NMEA from the GPS, cgps also shows time and position
> properly.
> >
> > My chrony.conf is:
> >>
> >> server 0.us.pool.ntp.org
> >> server 1.us.pool.ntp.org
> >> server 2.us.pool.ntp.org
> >> server 3.us.pool.ntp.org
> >> driftfile /var/lib/chrony/drift
> >> allow
> >> refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
> >> makestep 1 -1
> >>
> > Chronyc sources shows this:
> >>
> >> $ chronyc sources
> >> 210 Number of sources = 5
> >> MS Name/IP address Stratum Poll Reach LastRx Last sample
> >> 
> ===
> >> #? GPS   0   4 0   10y +0ns[   +0ns]
> +/-0ns
> >> ^+ time-c.nist.gov   1   9   375   110-23ms[  -22ms]
> +/-   47ms
> >> ^* pool-96-248-122-64.cmdnnj 1  10   37756  +9749us[  +11ms]
> +/-   18ms
> >> ^- 104.156.99.2262   9   377   367+15ms[  +17ms]
> +/-  107ms
> >> ^- 4.53.160.75
> >>
> > This system is going to be used on a boat and might not have internet.
> I can tell that both programs are accessing the shared memory using ipcs -m:
> >
> >> -- Shared Memory Segments 
> >> keyshmid  owner  perms  bytes  nattch
> status
> >> 0x4e545030 0  root   60080 2
>
> >> 0x4e545031 32769  root   60080 1
> >>
> > Any idea why chrony isn't getting time from the GPS?
> >
> > Thanks
>

[chrony-users] Not getting time from gpsd

[Chris Greenman]

Hello,
I'm having an issue with getting time from gpsd.

My setup is:
Raspberry Pi 3 running Jessie Lite
USB U-Blox gps

gpsd is receiving NMEA from the GPS, cgps also shows time and position
properly.

My chrony.conf is:

server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org
driftfile /var/lib/chrony/drift
allow
refclock SHM 0 refid GPS precision 1e-1 offset 0. delay 0.2
makestep 1 -1

Chronyc sources shows this:

$ chronyc sources
210 Number of sources = 5
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
#? GPS   0   4 0   10y +0ns[   +0ns] +/-
 0ns
^+ time-c.nist.gov   1   9   375   110-23ms[  -22ms] +/-
47ms
^* pool-96-248-122-64.cmdnnj 1  10   37756  +9749us[  +11ms] +/-
18ms
^- 104.156.99.2262   9   377   367+15ms[  +17ms] +/-
 107ms
^- 4.53.160.75

This system is going to be used on a boat and might not have internet.  I
can tell that both programs are accessing the shared memory using ipcs -m:

-- Shared Memory Segments 
keyshmid  owner  perms  bytes  nattch status

0x4e545030 0  root   60080 2

0x4e545031 32769  root   60080 1

Any idea why chrony isn't getting time from the GPS?

Thanks