Hey Paul, Le 2026-05-16 17:12, Paul Gevers a écrit : > Hi Vincent, > > On 5/9/26 15:50, Vincent Blut wrote: > > I'm still unable to reproduce the reported issue though. Could you please > > test > > the attached chrony package with debugging support enabled? > > debian@ci-worker-ppc64el-01:~$ sudo /usr/bin/chronyc -d -h 127.0.0.1,::1 > waitsync 0 0.1 0.0 1 > Resolved 127.0.0.1 to 127.0.0.1 > Resolved ::1 to ::1 > Opened UDPv4 socket fd=3 remote=127.0.0.1:323 > Sent data fd=3 len=104 > Timeout 1.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 2.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 4.000000 seconds > Could not receive message fd=3 : Connection refused > Opened UDPv6 socket fd=3 remote=[::1]:323 > Sent data fd=3 len=104 > Timeout 1.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 2.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 4.000000 seconds > Could not receive message fd=3 : Connection refused > 506 Cannot talk to daemon > No socket to send request > Opened UDPv4 socket fd=3 remote=127.0.0.1:323 > Sent data fd=3 len=104 > Timeout 1.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 2.000000 seconds > Could not receive message fd=3 : Connection refused > Sent data fd=3 len=104 > Timeout 4.000000 seconds > Could not receive message fd=3 : Connection refused
It looks like the port that is used for run-time monitoring is not open. Please check if chronyd is listening on 323/udp: `ss -lu | grep 323` If not, it probably means that you disabled chronyc access using the 'cmdport 0' directive. Try `chronyd -p | grep cmdport` > Paul Cheers, Vincent
signature.asc
Description: PGP signature
