It would appear that our issue may not get any real love based on this reply.... might be the nail in the coffin for opnsense for me.... Its been a good few years
opnsense-patch 7406a5067f8opnsense-patch a086f40bopnsense-patch 845fbd384fe
/usr/local/sbin/pluginctl -c unbound_start
2024-01-21T01:57:34 Notice kernel: <6>pid 10957 (unbound), jid 0, uid 59: exited on signal 11
os-OPNBEcore 1.2_1os-git-backup 1.0_3os-mdns-repeater 1.1_1os-wireguard 2.5_2os-wol 2.4_2
root@OPNsense:~ # shasum -a 256 /usr/local/opnsense/service/templates/OPNsense/Unbound/core/root.min.hints /var/unbound/root.hints /root/named.roota003be56acb66b2c9f77fb4685919bba36094f631b8b2f9bb6599220ebe31219 /usr/local/opnsense/service/templates/OPNsense/Unbound/core/root.min.hintsa003be56acb66b2c9f77fb4685919bba36094f631b8b2f9bb6599220ebe31219 /var/unbound/root.hintsf91549a77840b2d306fd49ad01facda1f4d4de0795f9f60844d6aea87a156429 /root/named.root
root@OPNsense:~ # md5sum /usr/local/opnsense/service/templates/OPNsense/Unbound/core/root.min.hints /var/unbound/root.hints /root/named.rootd090610a892c2e476d93042dc70dc393 /usr/local/opnsense/service/templates/OPNsense/Unbound/core/root.min.hintsd090610a892c2e476d93042dc70dc393 /var/unbound/root.hintsd22f17ab89749f32679cb1810d4b6109 /root/named.root
root@OPNsense:~ # diff -u /var/unbound/root.hints /root/named.root--- /var/unbound/root.hints 2024-01-21 17:16:17.563320000 +0000+++ /root/named.root 2024-01-21 17:36:08.329604000 +0000@@ -8,10 +8,10 @@ ; file /domain/named.cache ; on server FTP.INTERNIC.NET ; -OR- RS.INTERNIC.NET+;+; last update: December 20, 2023+; related version of root zone: 2023122001 ; -; last update: July 09, 2018 -; related version of root zone: 2018070901-; ; FORMERLY NS.INTERNIC.NET ; . 3600000 NS A.ROOT-SERVERS.NET.@@ -21,8 +21,8 @@ ; FORMERLY NS1.ISI.EDU ; . 3600000 NS B.ROOT-SERVERS.NET.-B.ROOT-SERVERS.NET. 3600000 A 199.9.14.201-B.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:200::b+B.ROOT-SERVERS.NET. 3600000 A 170.247.170.2+B.ROOT-SERVERS.NET. 3600000 AAAA 2801:1b8:10::b ; ; FORMERLY C.PSI.NET ;
/usr/local/sbin/pluginctl -c unbound_stop/usr/local/sbin/pluginctl -c unbound_start
opnsense-patch a086f40bopnsense-patch 845fbd384fe
I don't know which patch. I don't have this issue so I haven't been tracking all of the developments. I just disagree with Josh's perception of things. It appears the OPNsense team is attempting to fix the issue but aren't being provided enough information and testing support to be able to get it fixed. Therefore anyone who has this problem should test the provided patches and provide feedback so the investigation can continue.
Anyone that has this issue with Unbound and 100% CPU on one core: May I ask if each and everyone of you could tell me (and everyone else) which CPU type / Bare metal / Virtualization you are running on? Reason: wonder if it could be a performance kind of thing that is part of this....I'm on Intel i7-8550, 8 threads and 4 cores (yea I know I say 8 cores all the time - but that is another story...). Baremetal, 16GB.Edit: And also, let me know if any of the interfaces has a direct connection to the OPNsense, for example a PC connected direct to LAN interface (the one used for setup for example) without any switch or anything between?
There appear to be others here who understand under the hood a lot more than I. I am unsure on what other logs are required, apart from the one within unbound? I can happily provide.
Here is the promised patch:https://github.com/opnsense/core/commit/a086f40b# opnsense-patch a086f40bCheers,Franco
Quotehttps://github.com/opnsense/core/commit/845fbd384fe# opnsense-patch 845fbd384feThis patch significantly changed the situation.Unbound is not crashing anymore, while without this patch Unbound was crashing daily.I'm testing it for several days. The settings were chosen to trigger crash as much as possible (no debugging logging, parallel threads).Probably without this patch the file is created in parallel with normal Unbound startup. With this patch the file is created always before the start of Unbound.
https://github.com/opnsense/core/commit/845fbd384fe# opnsense-patch 845fbd384fe
root@OPNsense:~ # cd /rootroot@OPNsense:~ # /usr/local/bin/curl https://github.com/opnsense/core/commit/7406a5067f8.patch -o 7406a5067f8.patchroot@OPNsense:~ # /usr/local/bin/curl https://github.com/opnsense/core/commit/a086f40b.patch -o a086f40b.patchroot@OPNsense:~ # /usr/local/bin/curl https://github.com/opnsense/core/commit/845fbd384fe.patch -o 845fbd384fe.patch
root@OPNsense:~ # /usr/bin/patch --dry-run --backup --directory /usr/local --strip 2 --unified --version-control numbered < 7406a5067f8.patchroot@OPNsense:~ # /usr/bin/patch --dry-run --backup --directory /usr/local --strip 2 --unified --version-control numbered < a086f40b.patchroot@OPNsense:~ # /usr/bin/patch --dry-run --backup --directory /usr/local --strip 2 --unified --version-control numbered < 845fbd384fe.patch
root@OPNsense:~ # patch --dry-run --backup --directory /usr/local --strip 2 --unified --version-control numbered < 845fbd384fe.patch Hmm... Looks like a unified diff to me...The text leading up to this was:--------------------------|From 845fbd384fe564a8b436a5a6475952f90183c188 Mon Sep 17 00:00:00 2001|From: Franco Fichtner <franco@opnsense.org>|Date: Fri, 13 Oct 2023 12:54:09 +0200|Subject: [PATCH] unbound: diagnose tool for strange unbound issue||PR: https://forum.opnsense.org/index.php?topic=36425.0|---| src/etc/inc/plugins.inc.d/unbound.inc | 6 +++++-| 1 file changed, 5 insertions(+), 1 deletion(-)||diff --git a/src/etc/inc/plugins.inc.d/unbound.inc b/src/etc/inc/plugins.inc.d/unbound.inc|index f74ba58e78b..0b77f131c13 100644|--- a/src/etc/inc/plugins.inc.d/unbound.inc|+++ b/src/etc/inc/plugins.inc.d/unbound.inc--------------------------Patching file etc/inc/plugins.inc.d/unbound.inc using Plan A...Hunk #1 succeeded at 143.Hunk #2 succeeded at 287.done
I decided to try and reduce power consumption around my place so I have today moved to a Intel 8500T dell micro setup with an m.2 to intel ethernet setup, 16gb ram. Also may as well try a switch from AMD to Intel to see if that makes any difference at all.