8 Říj
2026
8 Říj
'26
13:51
Hi Anand,
Knot DNS already send READY=1, STOPPING=1, RELOADING=1 (see
https://gitlab.nic.cz/knot/knot-dns/-/blob/master/src/knot/common/systemd.c)
Do you have?
```
$ knotd -VV | grep Systemd
Systemd integration: yes
```
Daniel
On 10/8/26 11:20, Anand Buddhdev wrote:
On 08/10/2026 08:43, Anand Buddhdev wrote:
For this, Knot DNS needs to support the READY=1,
STOPPING=1, RELOADING=1 messages using sd_notify.
Okay, so I just tried this out.
"Type=notify" works just fine. However, "Type=notify-reload"
doesn't work as I expected:
# systemctl reload knot
Job for knot.service failed.
See "systemctl status knot.service" and "journalctl -xeu
knot.service" for details.
In the journal, I see:
Oct 08 09:14:51 systemd[1]: Reloading Knot DNS Server...
Oct 08 09:14:51 knotd[1131575]: info: reloading configuration file
'/etc/knot/knot.conf'
Oct 08 09:14:51 knotd[1131575]: info: configuration reloaded
Oct 08 09:16:21 systemd[1]: knot.service: Reload operation timed out. Killing reload
process.
Oct 08 09:16:21 systemd[1]: Reload failed for Knot DNS Server.
So knot receives a HUP signal, and reloads its configuration, but I suspect that it does
not notify systemd with "RELOADING=1" and then "READY=1". Is it
possible to add this functionality to Knot DNS?
Regards,
Anand
--