Unbound crashes periodically with signal 11

hans109h

@salander27-0 I'm having similar results that you report. DHCP registration is turned back on, and no crashes so far. 1.13.1 seems to be an upstream solution.

noviceiii

I had a stable unbound service again after flushing all DHCP leases.

SOLUTION (in my case): FLUSH DHCP Leases

Details/ Follow-up is here:
https://forum.netgate.com/topic/161092/2-5-0-dns-service-stopping-randomly/5?_=1613861976462

(sorry, if we may have opened a very similar thread to this topic)

khuynh

@salander27-0 Thanks! This was really helpful. Seems to be working perfectly now.

noviceiii

@khuynh very well. Glad to help. Hit „like“ on the solution and spread the news.

fivetoedslothbear

@salander27-0 Thanks! That fixed it. I forced short leases to cause a lot of renewals, and since I installed unbound-1.13.1, I've had no crashes going on 18 hours now.

Salander27 0

@fivetoedslothbear Yeah, I'm just past 24 hours myself without any crashes.

Also, to anyone who installed 1.13.1 please continue to follow this thread as you may need to manually install the patched unbound from the stable repositories if/when a patched version is pushed.

Dexypher

@salander27-0 Been having the same issue for the last 24 hours -- will try this solution and see if it works for me. I appreciate it mate. Have a good one.

slu

I see that also on two 2.5.0 CE machines.
Disable "Register DHCP leases in the DNS Resolver" now and will have an eye on it.

cnaumer

@salander27-0 :I tried this. Will report back. However, I never had "Register DHCP leases in the DNS Resolver" set.

jimp

Since the new version of Unbound fixes it, it's unlikely to actually be related to just that one setting (DHCP lease registration), but that is the fastest way to trigger it for some people.

I imagine others are/were hitting it as well in different ways. So there isn't a need to keep tracking potential causes now that we know the upgrade fixes it.

Salander27 0

@jimp So is the plan then to push 1.13.1 to the stable repo or to try to bisect through the 1.13.1 release in order to find out which patch specifically fixes the issue and just apply that patch to the version in stable?

jimp

@salander27-0 said in Unbound crashes periodically with signal 11:

@jimp So is the plan then to push 1.13.1 to the stable repo or to try to bisect through the 1.13.1 release in order to find out which patch specifically fixes the issue and just apply that patch to the version in stable?

We'll bring in 1.13.1, there isn't a compelling case to do all the legwork to pick in partial changes at this point. 1.13.1 is a minor patch/bug fix release and the impact is low other than the fix for this which is highly beneficial.

Salander27 0

@jimp Speak of the devil, looks like it's already been added to the stable repos.

For anyone coming into this thread now, you can run the following command to pull unbound 1.13.1 from the stable/2.5.x repo (I am unsure of how to update system packages from the UI, hopefully someone can chime in there):

pkg upgrade -f unbound

(you should see that it is installing unbound-1.13.1)
Make sure to restart unbound after this package installation.

It is probably a good idea for those who have installed the devel package to do this as well just to ensure that your systems are not a mix of devel and stable packages.

jimp

There isn't a good way to do that from the GUI, but you could run

pkg upgrade -fy unbound from 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

cnaumer

@jimp : I can confirm that the new version fixes it for us.

gorgonbert

@salander27-0 fixed it for me too... thank you

slu

@jimp

thank you Jim.
This open and direct communication is really awesome!

johnt

Fixed for me too, 24hrs with no unbound restarts...

jmkofoed

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

johnpoz

@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: