Re: chronyc serverstats => 501 not autorized

Gerd Hoerst <[email protected]> Tue, 18 Nov 2025 14:44:17 +0100
Newsgroups gmane.comp.time.chrony.user
Message-ID <[email protected]>
Hi !

Its v 4.8
/var/run/chrony/chronyd.sock exists
its owned by user:group _chrony:chrony and has mode 755
(dir /var/run/chrony same owner:group but mode 700)
calling chronyc strace ends in:
Could not bind/connect client to unix socket
Unrecognized command

(run as root/su)

Ciao Gerd


Am 18.11.2025 08:37, schrieb Miroslav Lichvar:
> On Fri, Nov 14, 2025 at 12:41:09PM +0100, Gerd Hoerst wrote:
>> My 5 Chrony Server are runing quite a long time and in know these 
>> commands
>> have worked... but it seems during the last releases something has 
>> changed
>> when i issue the in subject named command i get a 501 not autothrized 
>> ...
>> even as root or via sudo..
>> Did i missed a change config setting ?
> 
> That suggests it's not communicating over the Unix domain socket. What
> chrony version is it? Does /var/run/chrony/chronyd.sock exist and what
> owner and permissions does it have? If everything looks ok, try
> running chronyc in strace to see why it's failing to use the socket.

-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]