Miroslav Lichvar wrote:
On Mon, Feb 16, 2015 at 03:51:07PM +0000, David Lord wrote:
Miroslav Lichvar wrote:
As a workaround you can add "acquisitionport 123" to chrony.conf to
use just one socket for all (client, peer, server) communication,
which will effectively disable the check in which the server's request
is failing.
Done and ready for next restart.
Apparently, that workaround is not usable with 1.31, sorry for the
noise.
That was it, as restart after the client had been removed from
chrony.conf the client picked up a reply from chrony. So that
bug still needs fixing.
I'm not sure what's wrong, it seems to be working for me with
2.0-pre1.
Nothing wrong, it started working ok after I had removed that
client from the config file.
I meant with 2.0-pre1 the clients should be getting responses even if
they are configured as servers in chrony.conf with otherwise standard
configuration. It seems to work for me. If it doesn't for you, can you
please post your chronyd -d -d output?
Hi
I am using 2.0-pre1. The clients were not getting responses
when they were configured as servers in my original
chrony.conf. Since I added the "acquisitionport 123" line
it has been responding to requests.
I saw that the chronyd -d -d output flagged errors due to
either chrony.keys and/or keys directory from ntpd and after
these were cleared chronyd started ok and was responding to
requests without need of the "acquisitionport 123" line.
Script started on Tue Feb 17 01:37:23 2015
bash-4.3# /usr/local/sbin/chronyd -d -d -4 -f
/usr/local/etc/chrony/chrony.conf
2015-02-17T01:37:29Z main.c:433:(main) chronyd version 2.0-pre1
starting (+CMDMON +NTP +REFCLOCK -RTC -PRIVDROP -DEBUG
+ASYNCDNS +IPV6 -SECHASH)
2015-02-17T01:37:29Z reference.c:193:(REF_Initialise)
Frequency -0.073 +/- 4.049 ppm read from
/var/db/chrony/chrony.drift
2015-02-17T01:37:34Z sources.c:454:(log_selection_message)
Selected source 192.168.59.61
2015-02-17T01:54:32Z main.c:528:(main) chronyd exiting
bash-4.3# exit
Script done on Tue Feb 17 01:54:42 2015
Thanks
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
