Ubuntu
gpsd package

  1. Bug #1872175
  2. Comment #4

Comment 4 for bug 1872175

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

If GPSD tries to contact chrony I see entries like this:
  gpsd[2649]: gpsd:PROG: PPS:/dev/ttyAMA0 chrony socket /var/run/chrony.ttyAMA0.sock doesn't exist
  gpsd[2649]: gpsd:PROG: PPS:/dev/ttyUSB1 chrony socket /var/run/chrony.ttyUSB1.sock doesn't exist

I reduced it to just the device that seems to have working PPS and retried.
With chrony set up to expect /var/run/chrony.ttyUSB0.sock via

in Chrony.conf I set
# get input from GPSD
refclock SHM 0 refid GPS precision 1e-1 offset 0.9999 delay 0.2
refclock SOCK /var/run/chrony.ttyXX.sock refid PPS

After restart of chrony I had
srwxr-xr-x 1 root root 0 Apr 27 14:26 /var/run/chrony.ttyUSB0.sock=

And with that I get:
Apr 27 14:27:53 ubuntu gpsd[2568]: gpsd:PROG: PPS:/dev/ttyUSB0 connect chrony socket failed: /var/run/chrony.ttyUSB0.sock, error: -2, errno: 13/Permission denied

Ok it is reproducible now and thereby debuggable.
Maybe the code that drops GPSD permissions runs to early now or anything like that.
But at least I can now action on it over here.