This bug doesn't only affect `systemctl restart named.service`. After upgrading a server to bookworm yesterday I just found that named was being restarted periodically.
2023-08-06T15:48:31.080060+01:00 river systemd[1]: named.service: Failed with result 'timeout'. 2023-08-06T15:48:31.080557+01:00 river systemd[1]: Failed to start named.service - BIND Domain Name Server. 2023-08-06T15:48:31.315062+01:00 river systemd[1]: named.service: Scheduled restart job, restart counter is at 853. 2023-08-06T15:48:31.315934+01:00 river systemd[1]: Stopped named.service - BIND Domain Name Server. 2023-08-06T15:48:31.369499+01:00 river systemd[1]: Starting named.service - BIND Domain Name Server... 2023-08-06T15:48:31.370021+01:00 river systemd[1]: Started named.service - BIND Domain Name Server. ... 2023-08-06T15:48:31.435786+01:00 river named[792739]: all zones loaded I tracked this down to `Type=notify` with our chroot not having the socket present. Whilst it took me a while to notice because it was *mostly* working, this issue *was* causing some downtime during the restarts. It would also have been spamming secondary's with notifications upon each restart. I'll go see about implementing the socket in the chroot.... -- - Athanasius (he/him) = Athanasius(at)miggy.org / https://miggy.org/ GPG/PGP Key: https://miggy.org/gpg-key "And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
signature.asc
Description: PGP signature
