Unbound crashes periodically with signal 11

Smoothrunnings

Are you running pfBlockerNG-Devel 3.0.0_10?

I was trying to run this this week and my pfSense kept rebooting every hour or so too. I have since removed it and am running 2.1.4 or whatever the latest is in pfSenese 2.5.0 and its not crashing...yet. :)

fibrewire

@jimp thanks for all your help through the years!

I have a few systems that show something interesting on the serial console and believe it to be the same issue. Made us think it was a hardware fault of some sort, but entering the boot loader and starting with kernel.old seems to bypass the issue.

I'll try the dnsresolver update and see if it fixes the issue.

https://forum.netgate.com/topic/150515/enable-vga-on-serial-memstick-install/17

aaronssh

My Unbound was crashing every hour or two for several days since the upgrade to pfSense 2.5. After manually updating Unbound to the latest version, I haven't had a single Unbound reboot for the last 24 hours. That fixed it!

fibrewire

@aaronssh awesome man! May i ask what hardware you are running? CPU / Chipset would be helpful.

LamaZ

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

unbound-1.13.1

Upgrade to unbound-1.13.1 fixed this issue for me. 48 hours later no more crashes. Thanks!

I followed @jimp's suggested syntax.

RckF3

Hi all,

Was wondering if anyone had this issue after upgrading unbound-1.13.1?

I thought I was good for a few days..but a week later I'm having it drop again overnight.

pid 22784 (unbound), jid 0, uid 59: exited on signal 11

Haven't dug much further .. was just wondering before I did so. My DHCP registration is enabled but may disable for now. Shoudln't affect people other than me anyway.

hans109h

@rckf3 I upgraded to 1.13.1 as soon as I could and haven't had the service crash since.

MoonSire

I am still experiencing this problem since the update to 21.02-RELEASE-p1 (arm) last weekend. I am using a Netgate SG-1000.

I have tried updating unbound, but it was already at the version specified so it only triggered a reinstall:

Mar 15 15:57:56	pkg	28723	unbound reinstalled: 1.13.1 -> 1.13.1

This can still be seen in the log:

Last 50 General Log Entries. (Maximum 50)
Mar 16 08:56:07	dhcpleases	42059	Could not deliver signal HUP to process 46780: No such process.
Mar 16 08:55:42	dhcpleases	42059	Could not deliver signal HUP to process 46780: No such process.
Mar 16 08:55:30	dhcpleases	42059	Could not deliver signal HUP to process 46780: No such process.
Mar 16 08:46:54	dhcpleases	42059	Could not deliver signal HUP to process 46780: No such process.
Mar 16 08:46:14	dhcpleases	42059	Could not deliver signal HUP to process 46780: No such process.
Mar 16 08:42:55	kernel			pid 46780 (unbound), jid 0, uid 59: exited on signal 11
Mar 15 15:58:05	dhcpleases	42059	Could not deliver signal HUP to process 80983: No such process.
Mar 15 15:57:56	pkg		28723	unbound reinstalled: 1.13.1 -> 1.13.1
Mar 15 15:49:42	dhcpleases	75008	Could not deliver signal HUP to process 70437: No such process.

MoonSire

@jimp I only see reports based on pfSense 2.5 and not 21.02. Is this the correct place to report this or do you have another place for pfSense plus?

RckF3

I know you’re on 21.02 and not 2.5 but seems most folks here had the unbound fixed with 1.13. Even though I’m on 2.5, I’m glad (for my sake, not yours!) that i’m not the only one that still has this problem post updating unbound to 1.13. Turning off registering DHCP is a temporary fix for me but will possibly have to downgrade if I can’t find anything else.

jimp

For this particular issue it would be the same on both