fail: the anchor is NOT ok and could not be fixed

[Gil Levy]

Anyone?
Still couldn't fix this on boot.
Appreciate your help.

On Fri, 23 Oct 2020 at 13:51, Gil Levy <just.gil at gmail.com> wrote:

> After a system reboot, I get the following message when I run
> #> sudo systemctl status unbound
>
> Oct 23 13:31:38 raspberrypi systemd[1]: Starting Unbound DNS server...
> Oct 23 13:31:39 raspberrypi package-helper[513]: /var/lib/unbound/root.key
> has content
> Oct 23 13:31:39 raspberrypi package-helper[513]: *fail: the anchor is NOT
> ok and could not be fixed*
> Oct 23 13:31:39 raspberrypi systemd[1]: Started Unbound DNS server.
>
> If I then issue:
> #> sudo systemctl restart unbound
> #> sudo systemctl status unbound
>
> Oct 23 13:48:30 raspberrypi systemd[1]: Starting Unbound DNS server...
> Oct 23 13:48:30 raspberrypi package-helper[1294]:
> /var/lib/unbound/root.key has content
> Oct 23 13:48:30 raspberrypi package-helper[1294]: *success: the anchor is
> ok*
> Oct 23 13:48:31 raspberrypi systemd[1]: Started Unbound DNS server.
>
> Why is that?
> Running unbound 1.9.0 on Debian.
>
> Thanks.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20201027/ee2ef009/attachment.htm>