Re: [chrony-users] chronyc serverstats => 501 not autorized

[Gerd Hoerst <gerd@xxxxxxxxxx>]

  Hi !
  
  
I compiled it on 24.04 with options from 4.7
  
  
Ciao Gerd

20.11.2025 08:28:47 Miroslav Lichvar <mlichvar@xxxxxxxxxx>:

On Wed, Nov 19, 2025 at 05:21:55PM +0100, Gerd Hoerst wrote:

Hi !

So here again.... for 4.7 i made 2 traces because the option -u is not
available there.

Both on same machine with same system (ubuntu 24.04)

Ok, so with 4.7 there is:

bind(3, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyc.89798.sock"}, 33) = 0
connect(3, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyd.sock"}, 27) = 0

but with 4.8 it is:

geteuid()                               = 0
bind(5, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyc.89002/pyyqvBK3cIONiIxh/sock"}, 50) = 0
connect(5, {sa_family=AF_UNIX, sun_path="/run/chrony/chronyd.sock"}, 27) = -1 EACCES (Keine Berechtigung)

For some reason, the same connect() call is failing with 4.8.
geteuid() returning 0 confirms it's running as root. The difference in
the bind() call is expected, that's was one of the changes made in
4.8, but I'm not sure how could that impact the connect() call.

I still suspect an AppArmor issue. Where did you get the 4.8 package?
On https://launchpad.net/ubuntu/+source/chrony I see the latest
version that Ubuntu has is 4.7.

--
Miroslav Lichvar