Red Hat Bugzilla – Bug 1274995
knot: systemd service fails to start, not built with systemd support
Last modified: 2016-01-15 06:25:56 EST
Description of problem:
# systemctl start knot
Job for knot.service failed. See 'systemctl status knot.service' and 'journalctl -xn' for details.
From what I can tell knotd is not notifying systemd that it has started.
# ldd /usr/lib64/libknot.so.0 | grep systemd; echo $?
Version-Release number of selected component (if applicable):
# rpm -qa knot
How reproducible: Always
I tried using `./configure --enable-systemd=yes` but that did seem to make a difference.
This appears to be an upstream regression.
I compiled both 1.6.4 and 1.6.5 on the same system using the same method.
$ ldd knot-1.6.5/src/.libs/libknot.so.0.0.1 | grep systemd
$ ldd knot-1.6.4/src/.libs/libknot.so.0.0.1 | grep systemd
libsystemd-daemon.so.0 => /lib64/libsystemd-daemon.so.0 (0x00007f850f6bd000)
libsystemd-journal.so.0 => /lib64/libsystemd-journal.so.0 (0x00007f850f49f000)
libsystemd-id128.so.0 => /lib64/libsystemd-id128.so.0 (0x00007f850f299000)
Created an upstream bug report: https://gitlab.labs.nic.cz/labs/knot/issues/432
This has just been fixed upstream, see https://gitlab.labs.nic.cz/labs/knot/issues/432
Thanks for the report. I work for the upstream and we'll probably do a patch release containing this fix in a week or so. So I'll fix the package as well.
knot-2.1.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f84522615c
Resolved in knot-1.6.6-1.el6