Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-10 Thread James Cloos
Package: unbound Followup-For: Bug #921538 I found the that problem is that 1.9.0-1 does a chroot("/etc/unbound") even though there is no chroot option in the config files. Once that occurs, it cannot see files like /var/lib/unbound/root.key et alia. -- System Information: Debian Release:

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-09 Thread Robert Edmonds
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

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-09 Thread Simon Deziel
On 2019-02-09 8:28 p.m., Robert Edmonds wrote: > Probably it's better to use the --with-chroot-dir= argument to configure > rather than directly patching the source to change the default. Indeed and that's what's being proposed in the merge request. Regards, Simon

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-08 Thread Simon Deziel
On 2019-02-08 7:26 a.m., Kepi wrote: > Chroot workaround is working for me too. Good. > Anyway in the long term would it be better to have chroot setup > automatically again? I found out that it was working before, at least > some work was done in #579622 for auto support. The auto-chroot setup

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-08 Thread Kepi
Chroot workaround is working for me too. It should probably be uploaded as soon as possible to save more networks :) Anyway in the long term would it be better to have chroot setup automatically again? I found out that it was working before, at least some work was done in #579622 for auto

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-07 Thread Ryan Kavanagh
Hi Simon, I too can confirm that disabling chroot'ing works. Best, Ryan -- |)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Trout, Diane E.
> > 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 This fix worked for me.

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Simon Deziel
Here is a merge request [*] to disable chroot'ing again like it has been since version 1.0.0-3 Regards, Simon *: https://salsa.debian.org/dns-team/unbound/merge_requests/3 signature.asc Description: OpenPGP digital signature

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Simon Deziel
Hi Ryan, 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]:

Bug#921538: Fails to start since upgrade to 1.9.0-1

2019-02-06 Thread Ryan Kavanagh
Package: unbound Version: 1.9.0-1 Severity: grave 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]