| Re: [chrony-users] chrony losing sync with GPS reference |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, Dec 04, 2018 at 07:23:17PM -0800, Bill Unruh wrote:
>
> On Wed, 5 Dec 2018, Brendan Simon (eTRIX) wrote:
>
> > I'm running Debian Linux (Jessie based with a few backport packages) on some embedded systems that use a GPS
> > receiver to set the system clock.
> >
> > The problem I have seen is that the chrony loses sync with the GPS reference after some time, and the system clock
> > starts to drift and never recovers. This is disastrous as I need to have the clocks synchronised.
> >
> > gpsd was restarted and then chrony started synchronising the system clock again.
> >
> > gpsd is 3.16 (jessie-backports) and chrony is 1.30 (jessie)
> >
>
> I think more information is needed. Make sure that the "refclocks" logs are
> enabled, and look at them when the clock loses sync to see what is happening.
> Are you using PPS or just the UTC time stamos from theGPS?
If would also help to see the configuration file and the debug output
from chronyd -d -d (it needs to be compiled with the --enable-debug
option to get the debug messages).
When PPS doesn't work, it's usually a problem with the "locked"
reference. Its offset may be too large or too variable.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.