Unbound crashes periodically with signal 11
-
@salander27-0 I can confirm this as well, I have this option set with a handful of static mappings with hostname specified.
-
confirmed
-
@jimp I have successfully downloaded and installed unbound-1.13.1 from the devel repo now that the package has been built. No crashes yet, but none of the DHCP leases of my static leases (with hostname) have expired yet so I wouldn't expect crashes yet. I will update in a few hours once those leases start expiring.
OBSOLETE PLEASE SEE https://forum.netgate.com/post/966915
For anyone else who wishes to try unbound 1.13.1 (normal caveats about this being unsupported and at your own risk) I simplified the install command to the following:
pkg add -f https://files01.netgate.com/packages/pfSense_master_amd64-pfSense_devel/All/unbound-1.13.1.txzYou can roll back with:
pkg install -f unboundAfter either of these commands you will need to restart the unbound service to pick up on the new binary.
OBSOLETE PLEASE SEE https://forum.netgate.com/post/966915
-
@salander27-0 been running 1.13.1 for ~2hrs, no crashes yet!
1.13.0 crashed way more often, as evidenced in my earlier message -
Alright, it's been about 2 and a half hours since I installed unbound-1.13.1 on my system. I have stress-tested it by reducing the DHCP lease time to 120 seconds and have since seen hundreds of DHCP renewals (and subsequent unbound HUPs). Were this unbound 1.13.0 I would have likely seen dozens of crashes, however unbound 1.13.1 has been completely stable in that time.
At this point I believe the best course of option is for additional people to test to see if their issue is resolved with the updated version. If you are willing to take system backups and accept the (IMO very low) risk that you may need to reinstall pfSense completely if something goes wrong (so don't do this on your prod systems) then please follow the instructions in my previous comment to install unbound-1.13.1.
-
@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.
-
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)
-
@salander27-0 Thanks! This was really helpful. Seems to be working perfectly now.
-
@khuynh very well. Glad to help. Hit „like“ on the solution and spread the news.
-
@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.
-
@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.
-
@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.
-
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. -
@salander27-0 :I tried this. Will report back. However, I never had "Register DHCP leases in the DNS Resolver" set.
-
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.
-
@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?
-
@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.
-
@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.
-
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.
