Unbound does not start anymore after update to 22.1.5

[hurgler]

Hi,

I updated to 22.1.5 and I am running on FreeBSD 13.0-STABLE / LibreSSL 3.3.6
After turning back from update, unbound was no longer running and could not be started.

• It seems not to be a problem of the blacklists (if I uncheck the "activate" button there it has no effect).
• A reinstall of unbound did not change
• All of my host configurations seem to be los in the web ui (do not know how it is called in english, but in german it reads "Überbrückung"
• On commandline it says "unbound-checkconf /var/unbound/unbound.conf
  unbound-checkconf: no errors in /var/unbound/unbound.conf"
• The same does "configctl unbound check"
• In the /conf/backup/config/* Files there still exists my Hostname overrides I defined earlier in unbound
• A reinstall of older backups (just the unbound part) did not change anything

Is there a way to clear all unbound configuration and reinstall from the backup that part? A way to deinstall unbound and make a fresh reinstall? Seems that unbound is somehow fundamental to opnsense. But I do not know how to go on.
I changed my config so the clients take the DNS from another server and DHCP propagates that Server. So now it works, but I am unhappy with that solution.

In which log file should I expect more hints? The web ui Log just says:
2022-04-12T18:29:53   Notice   unbound   daemonize unbound dhcpd watcher.   

In the /var/log/system/latest.log there is just that line a bit strange, but apart that nothing:
<11>1 2022-04-12T18:30:04+02:00 OPNsense.compeiler.de opnsense 66185 - [meta sequenceId="7"] /status_services.php: warning: ignoring missing default tunable request: debug.pfftpproxy

But a restart makes something but does not lead to a running service. But also does not show any error.

Thanks for any hint...

[Condor]

I have the same problem, even rolling back hadn't help. I think we should wait to 22.1.6 for this week https://forum.opnsense.org/index.php?topic=27846.msg135444#msg135444