RE: [chrony-users] Will it EVER synch and start serving? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: RE: [chrony-users] Will it EVER synch and start serving?
- From: "Dan Gearty" <dpgearty@xxxxxxxxxxxx>
- Date: Mon, 1 Mar 2021 13:50:19 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kolabnow.com; h= content-language:content-transfer-encoding:content-type :content-type:mime-version:message-id:date:date:subject:subject :in-reply-to:references:from:from:received:received:received; s= dkim20160331; t=1614624625; x=1616439026; bh=Kf1CgRZtGSiLGX9dQEn uzAEqivu7m4eVDCV0epHfct4=; b=BkrHDb2gB7E8nHf2fZbOifS2u0OOgkGOhjO VD/x0D9m1DTvOOKcQ3a5JRWDNOO1FaUhmL2O/Vui5kgK02UHhqtSVWjyF3Vvoa5f 0gOT/YVW49FseuGZwchDg5d6M9EvlpSunSFZmQbOTxi/UnE0cnFwVlkK0hyJcgYX OUwGTNfIHzAYdg86kJW29cVsQ10yAa9bNlNzVkKz8aVt1Q92PyCkd2IKBJAzrlSc hLo65nJaWVUFv/HjeixOy4kiTGNUfUf8V2jJaaNDD38E3cqCPVM8mHZOimrmBVrf 7XEYbuzuLRIslUG7rb1SR02kuUuZg6pixJUn2tHUDUr56zeidkplszvXg6LBHGAC tFboJxpk5f4W3ev981omzKF9iVX1nznwibnG/sT+RKkNVVyh8GAcWbUqcIXHbh/G jQLKlMr6gJu80FSDgSfGaKT4gohbjxKUZ4kNWTqQViSvUHgOjzej9PT/2eexJMw9 k2vT8rP7xk24CtaLNeW/EuQ5bmyUG0OQ7P28HWZjRlQhq+Uq9Pm0sUCqk0Z1U1T0 5JTrmYVkIze2Nb3WRpefCDT+rM5duUSvBjiEtORJoNdM1PrzIxZnA+S4cwMzxGwH buYddfpYGYQXr+5vkR0+GpSTd/G+T6VzVOH6xN+rvaIgTA+dGkNTQZejIkKQYNX8 zWPolF7s=
- Thread-index: AQHdm8hoCXc5eE7P/YvpQkFaOP1XfAIl6ZOxAnwrVZUDLNc2NQMamirsqgsTeBA=
I am just another user and do not know the details, but isn't makestep necessary to allow for a large enough clock jump to a close enough time for the clock speed algorithm to have a chance of functioning?
makestep 1.0 3
And if that works, a driftfile will assist the subsequent startups of the clock speed algorithm
driftfile /opt/var/lib/chrony/drift
Ignore the path, I am running chrony on a consumer wireless router via Entware.
-----Original Message-----
From: Aaron D. Gifford <synctimeguy1@xxxxxxxxxxx>
Sent: Monday, March 1, 2021 12:16 PM
To: chrony-users@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [chrony-users] Will it EVER synch and start serving?
On 3/1/21 9:47 AM, Bill Unruh wrote:
> Why not try Lichvar's suggestion and post your configuration
> (chrony.conf) as
> this may well be a configuration problem. Or a DNS problem.
No DNS issues. Forward and reverse DNS resolution works perfectly.
Though the config. below uses hostnames, in reality raw IPv4 and IPv6 addresses are used. All of the NTP server hosts are reachable and are responding, as evidenced chronyc outputs shown in earlier messages in this thread (Reach/LastRx/Last sample output columns).
> (eg, my system cannot resolve any of your sources. ARe those just
> phony names to protect something, or are they names you got from some
> document assuming they were real?)
Obviously I've masked the raw IPv4 and IPv6 addresses with phony names to protect the, uh, innocent...? Or the guilty? ;) *chuckle*
CONFIG:
ratelimit interval 3 burst 8
dumpdir /var/db/chrony
ntsdumpdir /var/db/chrony
cmdport 0
bindaddress local-public-ipv4-address.example.com
bindacqaddress local-public-ipv4-address.example.com
bindaddress local-public-ipv6-address.example.com
bindacqaddress local-public-ipv6-address.example.com
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server timesource-8-example.org iburst
server ip6timesource.example.org iburst
This is a FreeBSD 12.2-RELEASE-p4 host running the chrony-4.0 FreeBSD
package.
From `chronyd -v`:
chronyd (chrony) version 4.0 (+CMDMON +NTP +REFCLOCK -RTC +PRIVDROP
-SCFILTER -SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Thanks for any/all pointers as to where to look next!
Aaron out.
--
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.
--
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.