I can confirm that a fresh install of 1.4.22-1ubuntu3 works well.
Manually enabling the chroot feature also works, thanks Jonathan!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/13030
This bug was fixed in the package unbound - 1.4.22-1ubuntu3
---
unbound (1.4.22-1ubuntu3) trusty; urgency=low
* debian/patches/disable_chroot_by_default: Readded disable-chroot-by-default
functionality (LP: #1303088).
* debian/patches/silence_open_files_limit_warning: Readded
** Changed in: unbound (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/1303088
Title:
unbound-checkconf fatal error
To manage notifi
> This patch should be restored as it silences the warning about the open files
> limit and disable chroot by default.
>
> @Jonathan, if you introduced this delta with Debian on purpose and want to
> have chroot enabled by default, I could try to adapt the auto chroot feature.
We can certainly rei
** Changed in: unbound (Ubuntu)
Assignee: (unassigned) => Jonathan Davies (jpds)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/1303088
Title:
unbound-checkconf fatal error
To
After some digging, the problem was not introduced by the auto-chroot
feature but by the last Ubuntu specific upload:
unbound (1.4.22-1ubuntu2) trusty; urgency=medium
* debian/patches/debian-changes: Removed lingering changes from 1.4.22-1
upload.
This patch should be restored as it silenc
This is a bug (I) introduced with the auto chroot feature. I'll see how
to properly fix this but in the meantime, you can work around this by
setting an explicit chroot location like this in
/etc/unbound/unbound.conf:
server:
chroot: "/var/lib/unbound"
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unbound (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/13
