| Re: [chrony-users] Chronyd has good sources but rejects time "may be in error" and "Can't synchronise: no majority" |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chronyd has good sources but rejects time "may be in error" and "Can't synchronise: no majority"
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 27 May 2020 08:42:52 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590561776; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=GDQ58p3Pzsu63z3oSzoqv8CnLlazEgAEIWqQ6KXu4zY=; b=dR26LifvEp3OZGOkFiVFru9b62brD8dUPeVMA1+m6521yiYMx9HSnG9ZmsmsP/KRhN+Jiy A31OujPa0vZuXWYLV6GYDsmLqS9bHMiFw6acyCz9nQf0zKJyJU1MAouViCGVXlLTngBkwj +OZTUq6DHBUvkLo8mnM5UDTWL9QEKy8=
On Tue, May 26, 2020 at 11:21:47AM -0600, Aaron D. Gifford wrote:
> ## GPS NMEA reference:
> refclock SHM 0 offset 0.470 refid NMEA
>
> ## GPS PPS reference:
> refclock SHM 1 refid GPS lock NMEA
> THE PROBLEM: Periodically chronyd seems to stop listening to the GPS's
> date/time and PPS information, and even stops listening to peer NTP servers.
The problem is likely due to variable timing of the NMEA messages
(which may depend on the GPS firmware, number of satellites, and
probably other things), which causes the sources to not agree with
each another. Try removing the SHM 0 source, or add the noselect
option. Also, remove the lock option from the SHM 1 source. It works
only with PPS sources.
--
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.