unbound-checkconf fatal error

Bug #1303088 reported by Alexander Solla
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
unbound (Ubuntu)
Fix Released
Undecided
Jonathan Davies

Bug Description

Fresh install of Trusty Tahr, cloud image.

$ sudo apt-get install unbound
...

The following NEW packages will be installed:
  libunbound2 unbound unbound-anchor
...
Setting up unbound (1.4.22-1ubuntu2) ...
 * Starting recursive DNS server unbound
[1396714277] unbound[22340:0] warning: increased limit(open files) from 1024 to 4152
[1396714277] unbound-checkconf[22342:0] fatal error: config file //etc/unbound/unbound.conf is not inside chroot /etc/unbound

$ ls /etc/unbound/unbound.conf
/etc/unbound/unbound.conf

$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unbound (Ubuntu):
status: New → Confirmed
Revision history for this message
Simon Déziel (sdeziel) wrote :

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"

Revision history for this message
Simon Déziel (sdeziel) wrote :

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 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.

Jonathan Davies (jpds)
Changed in unbound (Ubuntu):
assignee: nobody → Jonathan Davies (jpds)
Revision history for this message
Jonathan Davies (jpds) wrote :

> 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 reintroduce this - when I looked at the source package the patch had no explaination on why it was needed in its patch headers and I couldn't see why we should be diverging from what upstream releases.

Jonathan Davies (jpds)
Changed in unbound (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 patch.
 -- Jonathan Davies <email address hidden> Mon, 07 Apr 2014 13:02:09 +0000

Changed in unbound (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Simon Déziel (sdeziel) wrote :

I can confirm that a fresh install of 1.4.22-1ubuntu3 works well. Manually enabling the chroot feature also works, thanks Jonathan!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.