A few of my deb and dev machines upgraded to unbound 1.9,
which completely failed.
After some effort I confirmed that it is calling chroot("/etc/unbound")
and therefore is unable to read /var/lib/unbound/root.key and thus exits.
There is no chroot setting in unbound.conf (including in its includes).
I was forced manually to downgrade back to 1.8.1 to get things to work
Is that default chroot(2) call an upstream change?
-JimC
This is Debian bug #921538, not a bug in upstream Unbound.
Hello,
Idézem/Quoting Simon Deziel via Unbound-users <unbound-users@nlnetlabs.nl>:
Hello,
A few of my deb and dev machines upgraded to unbound 1.9,
which completely failed.This is a known issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921538
Regards,
Simon
My strategy on major version change is as follows:
wait for bugs to be discovered.
So 1.9.1 is the first install candidate.
SZÉPE Viktor, honlap üzemeltetés / Running your application
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md
The stable branch didn't get that regression as 1.9.0 was only uploaded
to unstable.
Regards,
Simon