Unbound crashes periodically with signal 11
-
There isn't a good way to do that from the GUI, but you could run
pkg upgrade -fy unboundfrom Diagnostics > Command Prompt. Be sure to restart the Unbound service from Status > Services after.From the CLI the easiest way to do both is
pkg upgrade -fy unbound; pfSsh.php playback svc restart unbound -
@jimp : I can confirm that the new version fixes it for us.
-
@salander27-0 fixed it for me too... thank you
-
thank you Jim.
This open and direct communication is really awesome! -
Fixed for me too, 24hrs with no unbound restarts...
-
Hi
After installing unbound-1.13.1 my unbound is still restarting from time to time.
My system have been unstable for a long time, but I haven't had the time to dig into it. Last week I figured out that it was the unbound which is restarting. So I updated to version 2.5. But still having issues.
I have "DHCP Registration", "Static DHCP" and "OpenVPN Clients" enabled in my DNS Resolver settings.
I will try to test further and report back
Kind regards
Jens M. Kofoed -
@salander27-0 said in Unbound crashes periodically with signal 11:
(you should see that it is installing unbound-1.13.1)
hmmm - running 21.02, figured hey why not upgrade unbound. Even though not seeing this issue.. But I don't see it updating to 1.13.1
[21.02-RELEASE][admin@sg4860.local.lan]/root: pkg upgrade -fy unbound Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: unbound-1.13.0_2 [pfSense] Number of packages to be reinstalled: 1 1 MiB to be downloaded. [1/1] Fetching unbound-1.13.0_2.txz: 100% 1 MiB 1.2MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Reinstalling unbound-1.13.0_2... ===> Creating groups. Using existing group 'unbound'. ===> Creating users Using existing user 'unbound'. [1/1] Extracting unbound-1.13.0_2: 100% [21.02-RELEASE][admin@sg4860.local.lan]/root: pfSsh.php playback svc restart unbound Attempting to issue restart to unbound service... unbound has been restarted. [21.02-RELEASE][admin@sg4860.local.lan]/root:upon restart and looking in log - still seems to be 1.30.0
Feb 23 08:51:43 unbound 90907 [90907:0] info: start of service (unbound 1.13.0).
edit:
Didn't seem to update to 1.13.1[21.02-RELEASE][admin@sg4860.local.lan]/root: unbound-control -c /var/unbound/unbound.conf status version: 1.13.0 verbosity: 1 threads: 4 modules: 2 [ validator iterator ] uptime: 502 seconds options: control(ssl) unbound (pid 79734) is running... [21.02-RELEASE][admin@sg4860.local.lan]/root:An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 25.07 | Lab VMs 2.8, 25.07 -
@jimp This (upgrade of unbound to 1.13.1) sad fully does NOT fix the issue on my system. Disabling DHCP leases fixed the restarts... but this package upgrade to 1.13.1 (and restart and re-enabling DHCP leases) brought the old behaviour back (restart of unbound about every 10 minutes in my case).
So actually 1.13.1 at least seems to not fully fix the problem for all systems.
UPDATE: but again also disabling DHCP leases again for/with 1.13.1 unbound fixes it again -
The symptom fixed by 1.13.1 is the crash/segfault.
"Restarting" is not a symptom of a problem, it's a side effect of using DHCP lease integration and is normal.
-
Upgraded unbound from the sable repo as described earlier, and still getting DNS Server crashes, not automatically restarting
Next time it happens I'll try and grab a log to post
-
@johnpoz said in Unbound crashes periodically with signal 11:
Didn't seem to update to 1.13.1
[2.5.0-RELEASE][root@priv.some-pfsense-local-network.net]/root: pkg upgrade unbound Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: unbound: 1.13.0_2 -> 1.13.1 [pfSense] Number of packages to be upgraded: 1 1 MiB to be downloaded. Broadcast Message from root@priv.brit-hotel-fumel.net (no tty) at 21:34 CET... Communications with UPS ups@10.0.0.4 lost y Broadcast Message from root@priv.brit-hotel-fumel.net (no tty) at 21:34 CET... Communications with UPS ups@10.0.0.4 established [1/1] Fetching unbound-1.13.1.txz: 100% 1 MiB 297.0kB/s 00:04 Checking integrity... done (0 conflicting) [1/1] Upgrading unbound from 1.13.0_2 to 1.13.1... ===> Creating groups. Using existing group 'unbound'. ===> Creating users Using existing user 'unbound'. [1/1] Extracting unbound-1.13.1: 100%..... and then I restarted unbound.
Btw : sorry : my UPS went to the toilet or something like that.
-
@johnpoz said in Unbound crashes periodically with signal 11:
Didn't seem to update to 1.13.1
I am seeing the same on my SG-1100 where the package is not updating.
[21.02-RELEASE]/root: pkg upgrade -fy unbound Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: unbound-1.13.0_2 [pfSense] Number of packages to be reinstalled: 1 [1/1] Reinstalling unbound-1.13.0_2... ===> Creating groups. Using existing group 'unbound'. ===> Creating users Using existing user 'unbound'. [1/1] Extracting unbound-1.13.0_2: 100% -
Yeah not seeing this available, still
I have
[21.02-RELEASE][admin@sg4860.local.lan]/root: pkg info unbound unbound-1.13.0_2 Name : unbound Version : 1.13.0_2 Installed on : Tue Feb 23 08:53:42 2021 CST Origin : dns/unboundIf do upgrade unbound says nothing to do
WWW: https://www.nlnetlabs.nl/projects/unbound [21.02-RELEASE][admin@sg4860.local.lan]/root: pkg upgrade unbound Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) Your packages are up to date. [21.02-RELEASE][admin@sg4860.local.lan]/root:@Gertjan your on 2.5, I'm on 21.02
Take it this was only released for 2.5 and not 21.02
-
I think the common factor here is that both @johnpoz and @LostInIgnorance are using ARM devices here which presumably uses a different stable repository with ARM-specific packages.
Unfortunately I know little about this but perhaps @jimp can chime in with if/when an updated package can be expected to be available for that architecture.
-
@salander27-0 I am using a SG-5100 (not ARM) with 21.02 and no Unbound update is visible.
-
I'm on a sg-4860.. That is not arm either..
I do have some 3100's - but they are not even on 2.4.5p1 - since covid had already hit when that came out.. And sure wasn't going to update them when nobody in the office, etc.
-
I thought I already responded in this thread, might have been another. It's not up yet for 21.02, just 2.5.0.
The Plus repos are locked down while we work on the immediate fix needed for SG-3100. It'll be updated soon.
-
I'm getting unbound crashes with signal 8 - using unbound 1.13.1
-
That is unlikely to be the same issue as this, I'd keep that in its own thread.
-
Jim has it ever been considered to put unbound as a package in the package manager instead of only updating it with pfSense updates?
