|Re: [chrony-users] Many servers became unreachable|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
On Mon, Jun 01, 2015 at 07:36:37PM +0200, Roel Schroeven wrote:
> Roel Schroeven schreef op 2015-06-01 17:41:
> >That setup has worked nicely for quote some time, but today suddenly it
> >failed: chrony can't connect to its upstream servers anymore, and I have no
> >idea why.
> Everything works again now. It's a complete mystery to me.
It's probably the NAT on your firewall giving you source ports below
123, which older ntpd versions reject as bogus:
ntpdate -q works because it uses a random source port. chronyd
in recent versions does that too by default. Here is what I see with
when I fix the source port and query one of the servers from your
# /usr/sbin/chronyd -Q 'acquisitionport 122' 'server ntp1.telenet-ops.be iburst'
2015-06-02T07:41:37Z chronyd version 2.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
2015-06-02T07:41:37Z Initial frequency -22.698 ppm
2015-06-02T07:41:47Z No suitable source for synchronisation
2015-06-02T07:41:47Z chronyd exiting
# /usr/sbin/chronyd -Q 'acquisitionport 123' 'server ntp1.telenet-ops.be iburst'
2015-06-02T07:41:50Z chronyd version 2.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
2015-06-02T07:41:50Z Initial frequency -22.698 ppm
2015-06-02T07:41:54Z System clock wrong by -0.002986 seconds (ignored)
2015-06-02T07:41:54Z chronyd exiting
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.