Re: [gpsd-users] Can't connect Chrony to Gpsd on Fedora 29 - no sharing memory data and no polling via sock

[Askar Ibragimov]

Hello!

actually the issue was that gpsd was running without -n option (started by Fedora scripts). This would have denied the connection as polling did not started.

Also, when I used -n and I finally did not forgot to run ntpshmmon as root, I start seeing the output.

Cheers, Asakr

пн, 18 февр. 2019 г. в 22:32, Gary E. Miller <address@hidden>:

Yo Askar!

On Sun, 17 Feb 2019 14:10:56 +0200
Askar Ibragimov <address@hidden> wrote:

> Trying to setup vanilla-state gpsd+chrony on Fedora 29. Both are
> taken from repo of the Fedora

Ugh,  They apply patches that are unknown to us.

> It's 3.17 of gpsd and GPS UBLOX6 is connected to COM1.

3,17 is over 18 months old, some known bugs.

> Given:
> - cgps shows valid data after some warm-up.

How did you configure gpsd?

> - I have installed ppstest and it outputs data such as

Looks good.

> However, ntpshmmon does not output anything.

Likely gpsd config problem.

> Also, used  the configs  for chrony directly pasted from
> http://www.catb.org/gpsd/gpsd-time-service-howto.html#_feeding_chrony_from_gpsd

Always focus on the first failure.  If there is nothing in ntpshmmon then
do not waste time looking at chrony/ntpd yet.

> I appreciate advice on how to finalize the setup on Fedora.

Well, Fedora does things differently that we do.  I suspect you
have a problem with their patches, not our code.  You should also
contact them.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin