Unbound just hit 100% CPU on one core again...

[lar.hed]

Unbound not runnning...

This time it seems to have been triggered by med switching on my LAN PC, at least it is about the same time, but there is NO lines in the Unbound log that says anything usefull for me, except fatal error (which of course is something bad?):

Code Select Expand

2024-02-22T13:50:58 Critical unbound [43239:3] fatal error: Could not initialize thread
2024-02-22T13:50:58 Critical unbound [43239:2] fatal error: Could not initialize thread

It would be lovely if I knew why - just telling me the above gives no clue. The general log has some more details maybe, but I can not interpret what is going on:

Code Select Expand

2024-02-22T13:50:58 Notice kernel <6>pid 43239 (unbound), jid 0, uid 59: exited on signal 11
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns (execute task : unbound_configure_do())
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dns ()
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure dhcp ()
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure ipsec (execute task : ipsec_configure_do(,opt2))
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: plugins_configure ipsec (,opt2)
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: ROUTING: entering configure using 'opt2'
2024-02-22T13:50:43 Notice opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt2(igb2)
2024-02-22T13:50:43 Notice kernel <6>igb2: link state changed to UP

[lar.hed]

If anyone cares: Had another 100% CPU from Unbound. This time around there was NO interface / link going up or down - my LAN PC had been turned off for hours before this incident.

So here I give up, the Monit script works by running kill -9 and then restart. It would be nice if this gets solved some day, but I have very low fate in that to happen. There does not seem to be anything to work on, no interface dependes, no blocklist, no DoT, no DNSSEC or anything - it just freaks out. Someone has made a change, and my prediction is that this will get worse.

[joshndroid]

If anyone cares: Had another 100% CPU from Unbound. This time around there was NO interface / link going up or down - my LAN PC had been turned off for hours before this incident.

So here I give up, the Monit script works by running kill -9 and then restart. It would be nice if this gets solved some day, but I have very low fate in that to happen. There does not seem to be anything to work on, no interface dependes, no blocklist, no DoT, no DNSSEC or anything - it just freaks out. Someone has made a change, and my prediction is that this will get worse.

I gave up as well...

Disabled unbound and moved over to the adguard plugin package... almost drop in replacement in the end.
Still get to keep all my router rules/settings, still get to keep my upsteam DOT/DOH. Just had to put the DNS server values as upstream into adguard and I was off...
Was even able to clean up some of my rewrites in the process.

Its been days since any sort of internet issue.

[Fenixz]

Having the same issue. Everything is smooth until I would try and look at unbound log files and get stuck 'working...' then it would instantly jump to 100% and stay there. Not sure if it the same cause for others but cleared out log files and instantly dropped back to normal and no issues so far. Pretty new to OPNsense but figured I'd share my experience in hope to help narrow it down. Running log level verbosity 2, blocklist, DoT if that helps any. Not sure if verbosity level would be causing issues with the log size or something maybe?