Bug#947936: chrony: Does (still) not start properly on boot on buster

[Michael Biebl]

Am 03.01.20 um 18:06 schrieb Santiago Vila:
> reassign 947936 chrony,systemd
> thanks
> 
> I am unsure at this point where is exactly the problem.
> 
> I have several test instances at GCE (running buster) where chrony
> does not start even if it's enabled.
> 
> By trial and error I managed to make chrony to start again
> properly if I do this:
> 
> journalctl --rotate
> init 6
> 
> So the natural question would be: What kind of bug in systemd can make
> it not to start a service at all when there is a "bad" journal?

Can you provide instructions how this issue can be reproduced?

systemd in buster (and testing/sid) ships
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
which will prevent systemd-timesyncd from being started if chrony is
installed.
I'm running chrony here (with systemd-timesyncd being enabled) and it
works as expected.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200103/13e94b5f/attachment.sig>