On Mon, Sep 11, 2017 at 02:00:06PM +0200, Thibaut BEYLER wrote:
> Ok thanks, I tried with 'local" before and got very bad results, did some
> digging and turns out that was because I was having the same driftfile on
> both instance (probably the parameter isn't necessary on the server
> config), it's better now.
> 
> I specified a custom sock as bindcmdaddress for each instance
>  (/var/run/chrony/chronyd_1.sock and /var/run/chrony/chronyd_1.sock) and a
> custom cmdport for sthe server instance.
> 
> I can get chronyc to work with both instance, however ntpdata is not
> working on neitheir of them, i get "501 Not authorised", any idea ?

That means chronyc is not using the Unix domain socket. Did you
specify it with the -h option?

chronyc -h /var/run/chrony/chronyd_1.sock ntpdata

-- 
Miroslav Lichvar

-- 
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org 
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org 
with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to