Bug#1135826: chrony: chrony-wait.service times out if chronyd is on a socket

[Paul Gevers]

Hi Vincent,

On 5/6/26 20:07, Vincent Blut wrote:

I just deployed a new host on ci.debian.net and the chrony-wait service is
failing.

Note, this is a ppc64el host.

Any interesting logs?

I reverted my changed, rebooted and after reboot I have this:

debian@ci-worker-ppc64el-01:~$ sudo journalctl -b -t chronyd

May 07 19:59:08 ci-worker-ppc64el-01 chronyd[1107]: Loaded 0 symmetric keys



And here you can see it's not a timing issue:


506 Cannot talk to daemon
506 Cannot talk to daemon
^C
debian@ci-worker-ppc64el-01:~$ /usr/bin/chronyc  waitsync 0 0.1 0.0 1
506 Cannot talk to daemon
506 Cannot talk to daemon
506 Cannot talk to daemon
^C

506 Cannot talk to daemon
506 Cannot talk to daemon
506 Cannot talk to daemon
^C
debian@ci-worker-ppc64el-01:~$ sudo /usr/bin/chronyc  waitsync 0 0.1 0.0 1
try: 1, refid: 95F80CA7, correction: 0.000190875, skew: 0.006

506 Cannot talk to daemon
506 Cannot talk to daemon

May 07 19:59:08 ci-worker-ppc64el-01 chronyd[1107]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +S> May 07 19:59:08 ci-worker-ppc64el-01 chronyd[1107]: Using leap second list /usr/share/zoneinfo/leap-seconds.list May 07 19:59:08 ci-worker-ppc64el-01 chronyd[1107]: Frequency 0.344 +/- 0.006 ppm read from /var/lib/chrony/chrony.drift May 07 19:59:08 ci-worker-ppc64el-01 chronyd[1107]: Loaded seccomp filter (level 1) May 07 19:59:13 ci-worker-ppc64el-01 chronyd[1107]: Selected source 149.248.12.167 (2.debian.pool.ntp.org) May 07 19:59:13 ci-worker-ppc64el-01 chronyd[1107]: System clock TAI offset set to 37 seconds debian@ci-worker-ppc64el-01:~$ /usr/bin/chronyc -h 127.0.0.1,::1 waitsync 0 0.1 0.0 1 debian@ci-worker-ppc64el-01:~sudo /usr/bin/chronyc -h 127.0.0.1,::1 waitsync 0 0.1 0.0 1 debian@ci-worker-ppc64el-01:~$ sudo /usr/bin/chronyc -h 127.0.0.1,::1 waitsync 0 0.1 0.0 1

Assuming you are not trying to access chronyd remotely and/or that your
firewall does not block UDP port 323, this typically means that chronyd
is not running.

I doubt it, because when I run it with sudo and no -h option it works, while it fails with -h options or without sudo.

If that command has been run shortly after the previous one, I assume
chronyd finished starting‽

Well, after success, the next try with -h option fails again.

By the way, the above commands can be run without elevated privileges.

Not for me, as shown above.

Paul

OpenPGP_signature.asc
Description: OpenPGP digital signature