Date   

Re: ax25ipd- is something broken, or is the WIKI not up to date?

Basil Gunn
 

Weird...

I had other terminals open, and it must have been making a mess of
things...I closed the other terminals, and ran the same commands and
they worked as advertised...

...but previously I was getting numerous errors about files or
directories not existing... I can't explain it, I know enough by now
installing Draws to exactly do the commands in order...so not sure
what process was blocking things.

Sorry...
No problem Mike. Interested in any problems that come up. When you do
have problems supplying the console output in your post is a big help.


Re: ax25ipd- is something broken, or is the WIKI not up to date?

Mike B
 

Weird...

I had other terminals open, and it must have been making a mess of things...I closed the other terminals, and ran the same commands and they worked as advertised...

...but previously I was getting numerous errors about files or directories not existing...  I can't explain it, I know enough by now installing Draws to exactly do the commands in order...so not sure what process was blocking things.

Sorry...

Back to regular scheduled programming...

Mike
KF5DEY


Re: ax25ipd- is something broken, or is the WIKI not up to date?

Basil Gunn
 

ax25-status ax25-start ax25-stop all get copied your local bin directory
so they are in your path.

which ax25-status ax25-start ax25-stop
/home/pi/bin/ax25-status
/home/pi/bin/ax25-start
/home/pi/bin/ax25-stop

All of the "Testing AX.25" section works for me.
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#testing-ax25

Even though these scripts are in your path when logged in as user pi
they are not in your path when logged in as root. Scripts ax25-start & ax25-stop
require you to be root. When logged in as user pi, ax25-status will work
from any directory.

cd
cd bin
sudo su
ax25-stop
ax25-start

...in the section of ax25 testing, none of that in the wiki seems to
work any more.
Perhaps you can be more specific & give an example and a link to the
Wiki you are referring to.


Mike B <kf5dey@gmail.com> writes:

I am doing a new install, and double checking some things...in the section of ax25 testing, none of that in the wiki seems to work any more.

In my ax25 directory there is ax25ipd-stop and -start, no ax25-status to be found etc.

It is sending and receiving packets over the APRS freq (according to the raw packets function of APRS.FI)

I just want to know if there was a functional change, and the wiki hasn't been updated yet.

Thanks,
Mike


ax25ipd- is something broken, or is the WIKI not up to date?

Mike B
 

I am doing a new install, and double checking some things...in the section of ax25 testing, none of that in the wiki seems to work any more.

In my ax25 directory there is ax25ipd-stop and -start, no ax25-status to be found etc.

It is sending and receiving packets over the APRS freq (according to the raw packets function of APRS.FI)

I just want to know if there was a functional change, and the wiki hasn't been updated yet.

Thanks, 
Mike


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Basil,
We’ve spent enough time on this. I’ve created a new sd card image. Everything checks out through step 2 - all the crony steps are good. Time/date is current. 
Thanks for all you efforts. 
Richard


On Jul 18, 2021, at 9:28 PM, KI5EVJ - Richard via groups.io <rpgilbert1@...> wrote:


Success 

pi@DRAWS:~ $ sudo systemctl start chrony
pi@DRAWS:~ $ systemctl status chrony
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-07-16 15:52:02 CDT; 23s ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 24067 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
  Process: 24072 ExecStartPost=/usr/lib/chrony/chrony-helper update-daemon (code=exited, s
 Main PID: 24069 (chronyd)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/chrony.service
           \u251c\u250024069 /usr/sbin/chronyd -F -1
           \u2514\u250024070 /usr/sbin/chronyd -F -1
 
Jul 16 15:52:01 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 16 15:52:02 DRAWS chronyd[24069]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK
Jul 16 15:52:02 DRAWS chronyd[24069]: Frequency 2.415 +/- 5.189 ppm read from /var/lib/chr
Jul 16 15:52:02 DRAWS chronyd[24069]: Loaded seccomp filter
Jul 16 15:52:02 DRAWS systemd[1]: Started chrony, an NTP client/server.
lines 1-19/19 (END)

pi@DRAWS:~ $ chronyc sources
210 Number of sources = 8
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#x GPS                           0   3   377     6   -3210m[ -3210m] +/-  101ms
#- PPS                           0   3   377     6   -3210m[ -3210m] +/-  468ns
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^- time.cloudflare.com           3   6   177    63   -3210m[ -3210m] +/-   13ms
^- static-72-87-88-203.prvd>     2   7    42   184   -3210m[ -3210m] +/-   63ms
^- c-73-239-136-185.hsd1.wa>     3   6   177    63   -3210m[ -3210m] +/-   51ms
^- ntp6.doctor.com               2   6   177    63   -3210m[ -3210m] +/-   49ms
pi@DRAWS:~ $ chronyc sourcestats
210 Number of sources = 8
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                        12   6    88    +10.807     37.462   -3210m   782us
PPS                        18   9   136     +0.984      0.012   -3210m   537ns
GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
time.cloudflare.com         8   5   266     -0.322     22.404   -3210m  1219us
static-72-87-88-203.prvd>   4   3    79    -21.608    707.013   -3210m   684us
c-73-239-136-185.hsd1.wa>   8   6   266     +1.202     24.051   -3210m  1261us
ntp6.doctor.com             8   4   266     +2.440      9.284   -3210m   445us
pi@DRAWS:~ $ chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000004 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 2.415 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised
pi@DRAWS:~ $ chronyc activity
200 OK
4 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address
 
 


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Success 

pi@DRAWS:~ $ sudo systemctl start chrony
pi@DRAWS:~ $ systemctl status chrony
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-07-16 15:52:02 CDT; 23s ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 24067 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
  Process: 24072 ExecStartPost=/usr/lib/chrony/chrony-helper update-daemon (code=exited, s
 Main PID: 24069 (chronyd)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/chrony.service
           \u251c\u250024069 /usr/sbin/chronyd -F -1
           \u2514\u250024070 /usr/sbin/chronyd -F -1
 
Jul 16 15:52:01 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 16 15:52:02 DRAWS chronyd[24069]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK
Jul 16 15:52:02 DRAWS chronyd[24069]: Frequency 2.415 +/- 5.189 ppm read from /var/lib/chr
Jul 16 15:52:02 DRAWS chronyd[24069]: Loaded seccomp filter
Jul 16 15:52:02 DRAWS systemd[1]: Started chrony, an NTP client/server.
lines 1-19/19 (END)

pi@DRAWS:~ $ chronyc sources
210 Number of sources = 8
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#x GPS                           0   3   377     6   -3210m[ -3210m] +/-  101ms
#- PPS                           0   3   377     6   -3210m[ -3210m] +/-  468ns
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^- time.cloudflare.com           3   6   177    63   -3210m[ -3210m] +/-   13ms
^- static-72-87-88-203.prvd>     2   7    42   184   -3210m[ -3210m] +/-   63ms
^- c-73-239-136-185.hsd1.wa>     3   6   177    63   -3210m[ -3210m] +/-   51ms
^- ntp6.doctor.com               2   6   177    63   -3210m[ -3210m] +/-   49ms
pi@DRAWS:~ $ chronyc sourcestats
210 Number of sources = 8
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                        12   6    88    +10.807     37.462   -3210m   782us
PPS                        18   9   136     +0.984      0.012   -3210m   537ns
GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
time.cloudflare.com         8   5   266     -0.322     22.404   -3210m  1219us
static-72-87-88-203.prvd>   4   3    79    -21.608    707.013   -3210m   684us
c-73-239-136-185.hsd1.wa>   8   6   266     +1.202     24.051   -3210m  1261us
ntp6.doctor.com             8   4   266     +2.440      9.284   -3210m   445us
pi@DRAWS:~ $ chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000004 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 2.415 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised
pi@DRAWS:~ $ chronyc activity
200 OK
4 sources online
0 sources offline
0 sources doing burst (return to online)
0 sources doing burst (return to offline)
0 sources with unknown address
 
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Fixed the glitch Steve pointed out and reran the steps
I don't think you fixed it.

As I mentioned in my previous post delete the entire line that has the script
name then restart the chrony daemon. If you still get an error when
checking the chrony daemon status (sudo systemctl chrony) then
post your /etc/chrony/chrony.conf file.

Your other choice is to burn a new SD Card with an image file and
DO NOT EDIT ANY config files.


KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

Fixed the glitch Steve pointed out and reran the steps. Still seeing the daemon error:


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Fixed the glitch Steve pointed out and reran the steps. Still seeing the daemon error:

pi@DRAWS:~/n7nix/gps $ ./verify_time.sh
 
date cmd: Fri 16 Jul 2021 09:58:38 AM CDT
 
timedatectl
 
               Local time: Fri 2021-07-16 09:58:39 CDT
           Universal time: Fri 2021-07-16 14:58:39 UTC
                 RTC time: n/a
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
 
chronyc sources
 
506 Cannot talk to daemon
 
chronyc sourcestats
 
506 Cannot talk to daemon
 
chronyc tracking
 
506 Cannot talk to daemon
 
chronyc activity
 
506 Cannot talk to daemon
 
chronyd systemctl status
 
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2021-07-16 09:50:35 CDT; 8min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 593 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
 
Jul 16 09:50:35 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 16 09:50:35 DRAWS chronyd[603]: chronyd version 3.4 starting (+CMDMON +NTP +REFC\u2026EBUG)
Jul 16 09:50:35 DRAWS chronyd[603]: Fatal error : Invalid command at line 15 in file\u2026.conf
Jul 16 09:50:35 DRAWS chronyd[593]: Invalid command at line 15 in file /etc/chrony/c\u2026.conf
Jul 16 09:50:35 DRAWS systemd[1]: chrony.service: Control process exited, code=exite\u2026ILURE
Jul 16 09:50:35 DRAWS systemd[1]: chrony.service: Failed with result 'exit-code'.
Jul 16 09:50:35 DRAWS systemd[1]: Failed to start chrony, an NTP client/server.
Hint: Some lines were ellipsized, use -l to show in full.
 
gpsd systemctl status
 
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-07-16 09:50:35 CDT; 8min ago
  Process: 617 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 655 (gpsd)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gpsd.service
           \u2514\u2500655 /usr/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 16 09:50:35 DRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 16 09:50:35 DRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
gpsd: 3.22 (revision 3.22)
 
gpsd config
 
# 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="false"
 
# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES="/dev/ttySC0 /dev/pps0"
 
# Other options you want to pass to gpsd
GPSD_OPTIONS="-n"
pi@DRAWS:~/n7nix/gps $ chronyc sourcestats
506 Cannot talk to daemon
pi@DRAWS:~/n7nix/gps $ cd
pi@DRAWS:~ $ chronyc sourcestats
506 Cannot talk to daemon
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

verify_time.sh script.# Uncomment the following line to turn logging on.
log measurements statistics tracking
In file /etc/chrony/chrony.conf delete entire line beginning with script name
"verify_time.sh" save your edit and EXIT your editor.

Then restart the chrony daemon

sudo systemctl start chrony

# Then check the status of the chrony daemon

systemctl status chrony

KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

If the first line is line 1 then your line 15 is my line 16. If it
starts at line 0 then it is the same. I included the whole file
because there are two sets of broadcast and allow statements at the
bottom of the file. Not sure which is correct. I really appreciate
your help with this.


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Nice catch, Steve! I’ll run this again and post. 
Richard


On Jul 18, 2021, at 2:47 PM, Steve, N9VW <steve@...> wrote:

 The line above the "log measurements...." statement appears to be fouled up.

verify_time.sh script.# Uncomment the following line to turn logging on.

Notice the "." following the script command. That changes the filename somewhat...

FWIW,
73 de Steve, N9VW

On 7/18/2021 12:42 PM, KI5EVJ - Richard via groups.io wrote:
If the first line is line 1 then your line 15 is my line 16. If it starts at line 0 then it is the same. I included the whole file because there are two sets of broadcast and allow statements at the bottom of the file. Not sure which is correct. I really appreciate your help with this.

# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
pool 2.debian.pool.ntp.org iburst
 
# initstepslew 30 2.debian.pool.ntp.org
 
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
 
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
 
verify_time.sh script.# Uncomment the following line to turn logging on.
log  measurements statistics tracking
 
# Log files location.
logdir /var/log/chrony
 
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
 
# This directive tells 'chronyd' to parse the 'adjtime' file to find out if the
# real-time clock keeps local time or UTC. It overrides the 'rtconutc' directive.
#hwclockfile /etc/adjtime
 
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
 
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust
# SHM1 from gpsd (if present) is from the kernel PPS_LDISC module.
# It includes PPS and will be accurate to a few ns
# refclock SHM 1 offset 0.0 delay 0.1 refid PPS
# refclock PPS /dev/pps0 lock GPS trust prefer
 
# Configure broadcast and allow for your network and uncomment (Multiple declarations for$
#broadcast 30 192.168.255.255
#allow 192.168.0.0/16
#allow 44.0.0.0/8
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust require
refclock SHM 2 refid PPS precision 1e-9 poll 3 trust
 
broadcast 30 192.168.1.255
allow 192.168.1.0/24
 


Re: GPS has been working but not since Saturday #gpsd

Steve, N9VW
 

The line above the "log measurements...." statement appears to be fouled up.

verify_time.sh script.# Uncomment the following line to turn logging on.

Notice the "." following the script command. That changes the filename somewhat...

FWIW,
73 de Steve, N9VW

On 7/18/2021 12:42 PM, KI5EVJ - Richard via groups.io wrote:
If the first line is line 1 then your line 15 is my line 16. If it starts at line 0 then it is the same. I included the whole file because there are two sets of broadcast and allow statements at the bottom of the file. Not sure which is correct. I really appreciate your help with this.

# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
pool 2.debian.pool.ntp.org iburst
 
# initstepslew 30 2.debian.pool.ntp.org
 
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
 
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
 
verify_time.sh script.# Uncomment the following line to turn logging on.
log  measurements statistics tracking
 
# Log files location.
logdir /var/log/chrony
 
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
 
# This directive tells 'chronyd' to parse the 'adjtime' file to find out if the
# real-time clock keeps local time or UTC. It overrides the 'rtconutc' directive.
#hwclockfile /etc/adjtime
 
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
 
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust
# SHM1 from gpsd (if present) is from the kernel PPS_LDISC module.
# It includes PPS and will be accurate to a few ns
# refclock SHM 1 offset 0.0 delay 0.1 refid PPS
# refclock PPS /dev/pps0 lock GPS trust prefer
 
# Configure broadcast and allow for your network and uncomment (Multiple declarations for$
#broadcast 30 192.168.255.255
#allow 192.168.0.0/16
#allow 44.0.0.0/8
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust require
refclock SHM 2 refid PPS precision 1e-9 poll 3 trust
 
broadcast 30 192.168.1.255
allow 192.168.1.0/24
 


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

If the first line is line 1 then your line 15 is my line 16. If it starts at line 0 then it is the same. I included the whole file because there are two sets of broadcast and allow statements at the bottom of the file. Not sure which is correct. I really appreciate your help with this.

# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
pool 2.debian.pool.ntp.org iburst
 
# initstepslew 30 2.debian.pool.ntp.org
 
# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys
 
# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift
 
verify_time.sh script.# Uncomment the following line to turn logging on.
log  measurements statistics tracking
 
# Log files location.
logdir /var/log/chrony
 
# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
 
# This directive tells 'chronyd' to parse the 'adjtime' file to find out if the
# real-time clock keeps local time or UTC. It overrides the 'rtconutc' directive.
#hwclockfile /etc/adjtime
 
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can't be used along with the 'rtcfile' directive.
rtcsync
 
# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust
# SHM1 from gpsd (if present) is from the kernel PPS_LDISC module.
# It includes PPS and will be accurate to a few ns
# refclock SHM 1 offset 0.0 delay 0.1 refid PPS
# refclock PPS /dev/pps0 lock GPS trust prefer
 
# Configure broadcast and allow for your network and uncomment (Multiple declarations for$
#broadcast 30 192.168.255.255
#allow 192.168.0.0/16
#allow 44.0.0.0/8
 
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust require
refclock SHM 2 refid PPS precision 1e-9 poll 3 trust
 
broadcast 30 192.168.1.255
allow 192.168.1.0/24
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Thank you for the updated console output.
Your chronyd daemon is not starting because of a failure in the chrony
config file.

From that output:
Jul 15 03:25:40 DRAWS chronyd[614]: Fatal error : Invalid command at
line 15 in file /etc/chrony/chrony.conf
Please look at file /etc/chrony/chrony.conf line 15 and paste it in a
post to the forum. Perhaps provide a few lines above & below that line.

My line 15 in that file looks like the following, make sure yours does
as well.

log measurements statistics tracking

KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

I went though your steps but I am still having problems with the
chronyc sources/sourcestats/tracking. I get "Cannot talk to daemon"I
have a battery now but have held off installing it so we can fix this
problem. Richard
Jul 15 03:25:40 DRAWS chronyd[614]: Fatal error : Invalid command at line 15 in file\u2026.conf
Jul 15 03:25:40 DRAWS chronyd[606]: Invalid command at line 15 in file /etc/chrony/c\u2026.conf
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Control process exited, code=exite\u2026ILURE


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

I went though your steps but I am still having problems with the chronyc sources/sourcestats/tracking.  I get "Cannot talk to daemon"I have a battery now but have held off installing it so we can fix  this problem.
Richard

pi@DRAWS:~/n7nix $ git pull
remote: Enumerating objects: 7, done.
remote: Counting objects: 100% (7/7), done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0
Unpacking objects: 100% (4/4), done.
From https://github.com/nwdigitalradio/n7nix
   4c30238..6f82212  master     -> origin/master
Updating 4c30238..6f82212
Fast-forward
 gps/verify_time.sh | 3 +++
 1 file changed, 3 insertions(+)
pi@DRAWS:~/n7nix $ cd gps
pi@DRAWS:~/n7nix/gps $ ./verify_time.sh
 
date cmd: Thu 15 Jul 2021 03:28:19 AM CDT
 
timedatectl
 
               Local time: Thu 2021-07-15 03:28:19 CDT
           Universal time: Thu 2021-07-15 08:28:19 UTC
                 RTC time: n/a
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
 
chronyc sources
 
506 Cannot talk to daemon
 
chronyc sourcestats
 
506 Cannot talk to daemon
 
chronyc tracking
 
506 Cannot talk to daemon
 
chronyc activity
 
506 Cannot talk to daemon
 
chronyd systemctl status
 
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-07-15 03:25:40 CDT; 2min 39s ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 606 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
 
Jul 15 03:25:40 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 15 03:25:40 DRAWS chronyd[614]: chronyd version 3.4 starting (+CMDMON +NTP +REFC\u2026EBUG)
Jul 15 03:25:40 DRAWS chronyd[614]: Fatal error : Invalid command at line 15 in file\u2026.conf
Jul 15 03:25:40 DRAWS chronyd[606]: Invalid command at line 15 in file /etc/chrony/c\u2026.conf
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Control process exited, code=exite\u2026ILURE
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Failed with result 'exit-code'.
Jul 15 03:25:40 DRAWS systemd[1]: Failed to start chrony, an NTP client/server.
Hint: Some lines were ellipsized, use -l to show in full.
 
gpsd systemctl status
 
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2021-07-15 03:25:40 CDT; 2min 39s ago
  Process: 621 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 646 (gpsd)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gpsd.service
           \u2514\u2500646 /usr/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 15 03:25:40 DRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 15 03:25:40 DRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
gpsd: 3.22 (revision 3.22)
 
gpsd config
 
# 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="false"
 
# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES="/dev/ttySC0 /dev/pps0"
 
# Other options you want to pass to gpsd
GPSD_OPTIONS="-n"
pi@DRAWS:~/n7nix/gps $ cd 
pi@DRAWS:~ $ cd n7nix/debug
pi@DRAWS:~/n7nix/debug $ ./btest.sh --gps
*** Running as user: pi ***
Verify gpsd is returning sentences: Sentence count: 3
Test nmea sentence: GPS nmea sentences OK
pi@DRAWS:~/n7nix/debug $ systemctl status chronyd
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-07-15 03:25:40 CDT; 11min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 606 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
 
Jul 15 03:25:40 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 15 03:25:40 DRAWS chronyd[614]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +
Jul 15 03:25:40 DRAWS chronyd[614]: Fatal error : Invalid command at line 15 in file /etc/
Jul 15 03:25:40 DRAWS chronyd[606]: Invalid command at line 15 in file /etc/chrony/chrony.
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Control process exited, code=exited, sta
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Failed with result 'exit-code'.
Jul 15 03:25:40 DRAWS systemd[1]: Failed to start chrony, an NTP client/server.
 
pi@DRAWS:~/n7nix/debug $ gpsmon
pi@DRAWS:~/n7nix/debug $ cgps
cgps: caught signal 2
pi@DRAWS:~/n7nix/debug $ cd
pi@DRAWS:~ $ chronyc sources
506 Cannot talk to daemon
pi@DRAWS:~ $ chronyc sourcestats
506 Cannot talk to daemon
pi@DRAWS:~ $ cd /n7nix/debug
bash: cd: /n7nix/debug: No such file or directory
pi@DRAWS:~ $ cd n7nix
pi@DRAWS:~/n7nix $ cd debug
pi@DRAWS:~/n7nix/debug $ systemctl status chronyd
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-07-15 03:25:40 CDT; 18min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 606 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
 
Jul 15 03:25:40 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 15 03:25:40 DRAWS chronyd[614]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +
Jul 15 03:25:40 DRAWS chronyd[614]: Fatal error : Invalid command at line 15 in file /etc/
Jul 15 03:25:40 DRAWS chronyd[606]: Invalid command at line 15 in file /etc/chrony/chrony.
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Control process exited, code=exited, sta
Jul 15 03:25:40 DRAWS systemd[1]: chrony.service: Failed with result 'exit-code'.
Jul 15 03:25:40 DRAWS systemd[1]: Failed to start chrony, an NTP client/server.
 
pi@DRAWS:~/n7nix/debug $ cgps
cgps: caught signal 2
pi@DRAWS:~/n7nix/debug $ gpspipe -r
{"class":"VERSION","release":"3.17","rev":"3.17","proto_major":3,"proto_minor":12}
{"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttySC0","driver":"NMEA0183","activated":"2021-07-15T08:45:19.487Z","flags":1,"native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00},{"class":"DEVICE","path":"/dev/pps0","driver":"PPS","activated":"2021-07-15T08:45:19.516Z"}]}
{"class":"WATCH","enable":true,"json":false,"nmea":true,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
$GNGGA,141453.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*72
$GNGLL,3314.7083,N,09703.7306,W,141453.000,A,D*50
$GNGSA,A,3,22,06,13,30,02,19,14,01,17,24,03,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141453.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*6C
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141453.000,17,07,2021,00,00*4E
$GNGGA,141454.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*75
$GNGLL,3314.7083,N,09703.7306,W,141454.000,A,D*57
$GNGSA,A,3,22,06,13,30,02,19,14,01,17,24,03,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141454.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*6B
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141454.000,17,07,2021,00,00*49
$GNGGA,141455.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*74
$GNGLL,3314.7083,N,09703.7306,W,141455.000,A,D*56
$GNGSA,A,3,22,06,13,30,02,19,14,01,17,24,03,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GPGSV,4,1,13,19,65,329,22,17,55,026,21,06,54,195,37,14,54,096,21*7A
$GPGSV,4,2,13,46,38,229,44,24,26,306,18,02,23,211,23,11,23,204,45*75
$GPGSV,4,3,13,30,19,170,40,03,15,067,19,01,08,038,30,22,07,047,31*7C
$GPGSV,4,4,13,13,06,232,34*4B
$GLGSV,2,1,07,83,72,315,,80,71,144,,73,53,330,,82,36,026,*6E
$GLGSV,2,2,07,84,26,232,27,79,13,146,35,74,06,328,*59
$GNRMC,141455.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*6A
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141455.000,17,07,2021,00,00*48
$GNGGA,141456.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*77
$GNGLL,3314.7083,N,09703.7306,W,141456.000,A,D*55
$GNGSA,A,3,22,06,13,30,02,19,03,14,01,17,24,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141456.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*69
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141456.000,17,07,2021,00,00*4B
$GNGGA,141457.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*76
$GNGLL,3314.7083,N,09703.7306,W,141457.000,A,D*54
$GNGSA,A,3,22,06,13,30,02,19,03,14,01,17,24,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141457.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*68
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141457.000,17,07,2021,00,00*4A
$GNGGA,141458.000,3314.7083,N,09703.7306,W,2,13,0.7,188.7,M,-27.4,M,,0000*77
$GNGLL,3314.7083,N,09703.7306,W,141458.000,A,D*5B
$GNGSA,A,3,22,06,13,30,02,19,03,14,24,01,17,,1.3,0.7,1.1*23
$GNGSA,A,3,79,84,,,,,,,,,,,1.3,0.7,1.1*2B
$GPGSV,4,1,13,19,65,329,21,17,55,026,25,06,54,195,36,14,54,096,20*7D
$GPGSV,4,2,13,46,38,229,43,24,26,306,17,02,23,211,23,11,23,204,44*7C
$GPGSV,4,3,13,30,19,170,41,03,15,067,18,01,08,038,31,22,07,047,31*7D
$GPGSV,4,4,13,13,06,232,35*4A
$GLGSV,2,1,07,83,72,315,,80,71,144,,73,53,330,,82,36,026,*6E
$GLGSV,2,2,07,84,26,232,27,79,13,146,34,74,06,328,*58
$GNRMC,141458.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*67
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141458.000,17,07,2021,00,00*45
$GNGGA,141459.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*78
$GNGLL,3314.7083,N,09703.7306,W,141459.000,A,D*5A
$GNGSA,A,3,22,06,13,30,02,19,03,14,01,17,24,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141459.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*66
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141459.000,17,07,2021,00,00*44
$GNGGA,141500.000,3314.7083,N,09703.7306,W,2,13,0.8,188.7,M,-27.4,M,,0000*74
$GNGLL,3314.7083,N,09703.7306,W,141500.000,A,D*57
$GNGSA,A,3,22,06,13,30,02,19,14,24,01,17,03,,1.3,0.8,1.1*2C
$GNGSA,A,3,79,84,,,,,,,,,,,1.3,0.8,1.1*24
$GNRMC,141500.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*6B
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141500.000,17,07,2021,00,00*49
$GNGGA,141501.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*74
$GNGLL,3314.7083,N,09703.7306,W,141501.000,A,D*56
$GNGSA,A,3,22,06,13,30,02,19,03,14,01,17,24,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GPGSV,4,1,13,19,65,329,20,17,55,026,25,06,54,195,37,14,54,096,20*7D
$GPGSV,4,2,13,46,38,229,43,24,26,306,18,02,23,211,25,11,23,204,44*75
$GPGSV,4,3,13,30,19,170,40,03,15,067,18,01,08,038,31,22,07,047,32*7F
$GPGSV,4,4,13,13,06,232,35*4A
$GLGSV,2,1,07,83,72,315,,80,71,144,,73,53,330,,82,36,026,*6E
$GLGSV,2,2,07,84,26,232,26,79,13,146,35,74,06,328,*58
$GNRMC,141501.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*6A
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141501.000,17,07,2021,00,00*48
$GNGGA,141502.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*77
$GNGLL,3314.7083,N,09703.7306,W,141502.000,A,D*55
$GNGSA,A,3,22,06,13,30,02,19,03,14,01,17,24,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
$GNRMC,141502.000,A,3314.7083,N,09703.7306,W,000.0,008.1,170721,,,D*69
$GNVTG,008.1,T,,M,000.0,N,000.0,K,D*1F
$GNZDA,141502.000,17,07,2021,00,00*4B
$GNGGA,141503.000,3314.7083,N,09703.7306,W,2,13,0.9,188.7,M,-27.4,M,,0000*76
$GNGLL,3314.7083,N,09703.7306,W,141503.000,A,D*54
$GNGSA,A,3,22,06,13,30,02,19,14,01,17,24,03,,1.4,0.9,1.1*2A
$GNGSA,A,3,79,84,,,,,,,,,,,1.4,0.9,1.1*22
^C
 


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

My apologies. I actually ran the startup before I got you previous instructions so I skipped that part and missed your changes. I’ll go back and redo your previous post. Sorry to be such a clutz.

On Jul 16, 2021, at 5:42 PM, Basil Gunn <basil@pacabunga.com> wrote:


Richard,

1. Disappointed you did not refresh the n7nix repo as I asked as I
modified the verify_time.sh script to give me more information about
your problem.

2. Chrony was working in your previous posts but it looks like you
perhaps edited /etc/chrony/chrony.conf and caused chronyd start up to now
fail. From your console output:

Jul 14 06:15:21 DRAWS chronyd[608]: Invalid command at line 15 in file /etc/chrony/chrony.conf

My line 15 in that file looks like the following, make sure yours does
as well.

log measurements statistics tracking

3. The init config scripts that I have you run when you do an initial
install has working configurations for gpsd & chronyd. If you change
those config files I will not be able to help you.

/Basil


KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

:~/n7nix/gps $ ./verify_time.sh

timedatectl

Local time: Wed 2021-07-14 10:41:58 CDT
Universal time: Wed 2021-07-14 15:41:58 UTC
RTC time: n/a
Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

chronyc sources

506 Cannot talk to daemon




Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Richard,

1. Disappointed you did not refresh the n7nix repo as I asked as I
modified the verify_time.sh script to give me more information about
your problem.

2. Chrony was working in your previous posts but it looks like you
perhaps edited /etc/chrony/chrony.conf and caused chronyd start up to now
fail. From your console output:

Jul 14 06:15:21 DRAWS chronyd[608]: Invalid command at line 15 in file /etc/chrony/chrony.conf

My line 15 in that file looks like the following, make sure yours does
as well.

log measurements statistics tracking

3. The init config scripts that I have you run when you do an initial
install has working configurations for gpsd & chronyd. If you change
those config files I will not be able to help you.

/Basil


KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

:~/n7nix/gps $ ./verify_time.sh

timedatectl

Local time: Wed 2021-07-14 10:41:58 CDT
Universal time: Wed 2021-07-14 15:41:58 UTC
RTC time: n/a
Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no

chronyc sources

506 Cannot talk to daemon


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

:~/n7nix/gps $ ./verify_time.sh
 
timedatectl
 
               Local time: Wed 2021-07-14 10:41:58 CDT
           Universal time: Wed 2021-07-14 15:41:58 UTC
                 RTC time: n/a
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
 
chronyc sources
 
506 Cannot talk to daemon
 
chronyc sourcestats
 
506 Cannot talk to daemon
 
chronyc tracking
 
506 Cannot talk to daemon
 
chronyc activity
 
506 Cannot talk to daemon
 
chronyd systemctl status
 
\u25cf chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-07-14 06:15:21 CDT; 4h 26min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
  Process: 608 ExecStart=/usr/sbin/chronyd $DAEMON_OPTS (code=exited, status=1/FAILURE)
 
Jul 14 06:15:21 DRAWS systemd[1]: Starting chrony, an NTP client/server...
Jul 14 06:15:21 DRAWS chronyd[619]: chronyd version 3.4 starting (+CMDMON +NTP +REFC\u2026EBUG)
Jul 14 06:15:21 DRAWS chronyd[619]: Fatal error : Invalid command at line 15 in file\u2026.conf
Jul 14 06:15:21 DRAWS chronyd[608]: Invalid command at line 15 in file /etc/chrony/c\u2026.conf
Jul 14 06:15:21 DRAWS systemd[1]: chrony.service: Control process exited, code=exite\u2026ILURE
Jul 14 06:15:21 DRAWS systemd[1]: chrony.service: Failed with result 'exit-code'.
Jul 14 06:15:21 DRAWS systemd[1]: Failed to start chrony, an NTP client/server.
Hint: Some lines were ellipsized, use -l to show in full.
 
gpsd systemctl status
 
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2021-07-14 06:15:21 CDT; 4h 26min ago
  Process: 635 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 653 (gpsd)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gpsd.service
           \u2514\u2500653 /usr/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 14 06:15:21 DRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 14 06:15:21 DRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
gpsd: 3.22 (revision 3.22)
pi@DRAWS:~/n7nix/gps $ 

Not sure what I'm missing here:

pi@DRAWS:/etc/chrony $ chronyc sourcestats
506 Cannot talk to daemon
pi@DRAWS:/etc/chrony $ 

pi@DRAWS:~ $ chronyc sourcestats
506 Cannot talk to daemon
pi@DRAWS:~ $ 
 
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

It looks like you have 2 instances of the gps/pps device running, one
configured properly and one not. Also you weren't able to give me all
the chronyc tests I require. So please do this:

# Update your local copy of the n7nix repo
cd
cd n7nix
git pull

# Run the verify_time.sh script

cd gps
./verify_time.sh

Please post the console output.


KI5EVJ - Richard via groups.io <rpgilbert1=verizon.net@groups.io> writes:

Here are the 3 chrony test results. Number 2 is a problem:
pi@draws:~ $ chronyc sources
210 Number of sources = 8
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#x GPS 0 3 377 6 -2126m[ -2126m] +/- 103ms
#- PPS 0 3 377 5 -2126m[ -2126m] +/- 977ns
#? GPS 0 3 0 - +0ns[ +0ns] +/- 0ns
#? PPS 0 3 0 - +0ns[ +0ns] +/- 0ns
^- 38.229.54.9 2 10 277 110 -2126m[ -2126m] +/- 104ms
^- time.cloudflare.com 3 10 377 82 -2126m[ -2126m] +/- 14ms
^- 45.15.168.198 3 10 173 354 -2126m[ -2126m] +/- 65ms
^- triangle.kansas.net 2 10 376 42m -2126m[ -2126m] +/- 54ms

pi@draws:~ $ chronyc source stats
Unrecognized command
Asked for: chronyc sourcestats
NO space between source & stats

pi@draws:~ $ chronyc tracking
Reference ID : 00000000 ()
Stratum : 0
Ref time (UTC) : Thu Jan 01 00:00:00 1970
System time : 0.000000039 seconds fast of NTP time
Last offset : +0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 2.415 ppm fast
Residual freq : +0.000 ppm
Skew : 0.000 ppm
Root delay : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised


Re: GPS has been working but not since Saturday #gpsd

KI5EVJ - Richard
 

Here are the 3 chrony test results. Number 2 is a problem:
pi@draws:~ $ chronyc sources
210 Number of sources = 8
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#x GPS                           0   3   377     6   -2126m[ -2126m] +/-  103ms
#- PPS                           0   3   377     5   -2126m[ -2126m] +/-  977ns
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^- 38.229.54.9                   2  10   277   110   -2126m[ -2126m] +/-  104ms
^- time.cloudflare.com           3  10   377    82   -2126m[ -2126m] +/-   14ms
^- 45.15.168.198                 3  10   173   354   -2126m[ -2126m] +/-   65ms
^- triangle.kansas.net           2  10   376   42m   -2126m[ -2126m] +/-   54ms


pi@draws:~ $ chronyc source stats
Unrecognized command


pi@draws:~ $ chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000039 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 2.415 ppm fast
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised
 


Re: GPS has been working but not since Saturday #gpsd

Basil Gunn
 

Are you using an NWDR image and execute a config as described in the
"Getting started Guide"
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

or even better from the github repo

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_CONFIG.md

I am guessing that one of the following 3 things is your problem.

1. Do you have a working CR 1220 3V battery on your DRAWS hat?

2. Is your gps antenna in a window? ie. can it "see" some part of the
sky. Note the antenna is directional.

3. Chrony is not running.

Run the following and post the console output:

cd
cd n7nix/debug
./btest.sh --gps

Go to this link and run the listed tests and post the console output.
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#check-gps

Especially the chrony tests

chronyc sources
chronyc source stats
chronyc tracking

You should get output that looks something like this:

$ chronyc sources
210 Number of sources = 6
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#x GPS 0 3 377 8 -167ms[ -167ms] +/- 103ms
#* PPS 0 3 377 8 +58ns[ +388ns] +/- 444ns
^- nu.binary.net 2 9 377 173 -137us[ -142us] +/- 65ms
^- 159.89.45.132 2 10 377 159 +197us[ +194us] +/- 67ms
^- 38.229.53.9 2 10 377 685 +508us[ +481us] +/- 47ms
^- hc-007-ntp1.weber.edu 1 10 377 75 -62us[ -62us] +/- 14ms

pi@test11906072021:~/n7nix/debug $ chronyc sourcestats
210 Number of sources = 6
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
GPS 6 3 40 -414.303 738.161 -176ms 2230us
PPS 6 3 42 -0.009 0.108 -10ns 439ns
nu.binary.net 6 3 43m -0.186 0.453 -379us 106us
159.89.45.132 6 3 86m -0.185 0.295 +134us 156us
38.229.53.9 7 5 103m -0.007 1.593 +2240us 1498us
hc-007-ntp1.weber.edu 6 3 85m -0.274 0.145 -218us 61us

pi@test11906072021:~/n7nix/debug $ chronyc tracking
Reference ID : 50505300 (PPS)
Stratum : 1
Ref time (UTC) : Wed Jul 14 22:13:56 2021
System time : 0.000000149 seconds fast of NTP time
Last offset : +0.000000668 seconds
RMS offset : 0.000000466 seconds
Frequency : 11.571 ppm fast
Residual freq : +0.009 ppm
Skew : 0.112 ppm
Root delay : 0.000000001 seconds
Root dispersion : 0.000010429 seconds
Update interval : 8.0 seconds
Leap status : Normal

Something is still off. Gpsmon shows current time but if I enter
"date" in a terminal window I get yesterday evening (correct time
zone).
This indicates that chrony (https://chrony.tuxfamily.org/) is not
running which will happen if you didn't follow the "Getting Started
Guide"

I am connected by WIFI to our LAN but I'm not getting updates
from either the gps or WIFI. Reboots don't help. Richard

1 - 20 of 5764