Public bug reported:
if chroot a value has been entered in unbound.conf, unbound cannot
create a chroot and fails. An empty value for chroot works without
problems.
Jul 01 11:27:41 ldhost unbound[18800]: [18800:0] notice: init module 0: iterator
Jul 01 11:27:41 ldhost unbound[18800]: [18800:0] warning: root hints
/etc/unbound/root.hints: no NS content
Jul 01 11:27:41 ldhost unbound[18800]: [18800:0] fatal error: sd_notify failed
/run/systemd/notify: No such file or directory. Make sure that unbound has
access/permission to use the socket presented by>
Jul 01 11:27:41 ldhost systemd[1]: unbound.service: Main process exited,
code=exited, status=1/FAILURE
however, this problem only seems to arise from starting with systemd. If
you start unbound in the terminal with unbound -d -c
/etc/unbound/unbound.conf, it will be started without error reporting.
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885907
Title:
Unbound crash with chroot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1885907/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
