Kebert Martin wrote:
> Applied '0001-Apply-a-series-of-fixes-for-Unbound-1.9.0-suggested-.patch'
>
> Result:
> Oct 28 20:24:28 debian systemd[1]: Starting Unbound DNS server...
> Oct 28 20:24:28 debian package-helper[464]: /var/lib/unbound/root.key has
> content
> Oct 28 20:24:28 debian package-helper[464]: fail: the anchor is NOT ok and
> could not be fixed
> Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 0: subnet
> Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 1: validator
> Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 2: iterator
> Oct 28 20:24:28 debian systemd[1]: Started Unbound DNS server.
> Oct 28 20:24:28 debian unbound[468]: [468:0] info: start of service (unbound
> 1.9.0).
> ...
> Oct 28 20:31:31 debian kernel: unbound[470]: segfault at 1b0 ip
> 00007fdb28876e48 sp 00007fdb26fd6cf0 error 4 in libevent-2.1.so.6.0.2
> [7fdb28857000+54000]
> [...]
Hi, Kebert:
Thanks for checking that. Sorry it didn't work, and apologies for the
delay in getting back to you.
We're now looking into the possibility of updating the version of
unbound in buster to a newer upstream release that most likely already
includes the right combination of fixes for this issue, rather than
trying to backport the right set of fixes needed to the 1.9.0 release.
If you have an opportunity, could you give the candidate unbound package
available here a try?
https://people.debian.org/~edmonds/unbound/1.9.6-0+deb10u0/
Thanks!
--
Robert Edmonds
[email protected]
