| Re: [chrony-users] reachability cycling between 377 to 000 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] reachability cycling between 377 to 000
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 19 Oct 2020 09:15:12 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1603091718; 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=FJoiCYruuWNbVmw26OCfMFfPWwDFAeaeDodqJ7pTJAA=; b=CTjy300ac3N86ew/GM3Cahj5RTPbzbuAqqdVSWL+ZaAfaa6bJ8PrcSP2OejSkBrwSwiSM8 XPMVbW99qbRGdjmekD3aJ7oSLVDyK4IOYTBn8xHYIW8xS864M2yq6tqiKWa3+eHGOpcc4V xGjic6IOp1eNSPVV71PLOrdLXsXgz5k=
On Thu, Oct 15, 2020 at 05:50:01PM -0700, wis1@xxxxxxxxxxx wrote:
> If I monitor the output from 'chronyc sources', I see the reachability
> status change regularly from "377" to "000" and back again. Is this a known
> problem or a wrong / incomplete configuration?
Can you please post your chrony.conf and full chronyc sources? One
possibility is that the PPS locking is not good. This could be due to
an incorrect delay or offset specified for the NMEA source to which
the PPS is trying to lock. Try it without the lock option and ideally
also with some NTP servers.
--
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.