Simon Deziel wrote: > On 2019-02-06 11:12 a.m., Ryan Kavanagh wrote: > > Since the upgrade to 1.9.0-1, unbound fails to start. Purging the > > package and reinstalling does not fix the issue. The errors seem to be > > due to being unable to read various configuration files. > > > > Feb 06 11:01:12 zeta unbound[28647]: [28647:0] error: unable to open > > /var/lib/unbound/root.key for reading: No such file or directory > > Feb 06 11:01:12 zeta package-helper[28648]: [1549468872] > > unbound-checkconf[28651:0] error: Could not open > > /etc/unbound//etc/unbound/unbound.conf: No such file or director > > It seems like chroot'ing to /etc/unbound is attempted. To workaround you > can try this: > > cat << EOF > /etc/unbound/unbound.conf.d/chroot.conf > server: > chroot: "" > EOF > service unbound restart
Automatic chroot'ing has been disabled in the unbound Debian package for a while, by this commit: https://salsa.debian.org/dns-team/unbound/commit/66bb04a0869e315f76c4b4efe8632914d860686c It looks like that change was lost in the 1.9.0-1 upload, compare these two revisions: https://salsa.debian.org/dns-team/unbound/blob/debian/1.8.1-1/util/config_file.c#L163-165 https://salsa.debian.org/dns-team/unbound/blob/debian/1.9.0-1/util/config_file.c#L169-171 Probably it's better to use the --with-chroot-dir= argument to configure rather than directly patching the source to change the default. -- Robert Edmonds edmo...@debian.org
