Unbound crashes periodically with signal 11
-
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?
-
@chrcoluk said in Unbound crashes periodically with signal 11:
Jim has it ever been considered to put unbound as a package in the package manager instead of only updating it with pfSense updates?
It isn't an add-on package, so it doesn't belong there.
That said, we are considering ways to trigger updates on items included in the base system, but that's a longer-term goal.
These kinds of out-of-band updates are rare, though.
-
just had an unbound crash with signal 11:
Feb 25 14:45:54 router kernel: pid 38083 (unbound), jid 0, uid 59: exited on signal 11Feb 25 14:45:33 router unbound[38083]: [38083:0] info: start of service (unbound 1.13.1). Feb 25 14:45:34 router unbound[38083]: [38083:0] info: generate keytag query _ta-4f66. NULL IN Feb 25 14:45:54 router unbound[38083]: [38083:0] info: service stopped (unbound 1.13.1). Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 0: 6 queries, 0 answers from cache, 6 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 0: requestlist max 8 avg 2.16667 exceeded 0 jostled 0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: average recursion processing time 0.345135 sec Feb 25 14:45:54 router unbound[38083]: [38083:0] info: histogram of recursion processing times Feb 25 14:45:54 router unbound[38083]: [38083:0] info: [25%]=0.028672 median[50%]=0.196608 [75%]=0.643216 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: lower(secs) upper(secs) recursions Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.016384 0.032768 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.131072 0.262144 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.524288 1.000000 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 1: 3 queries, 0 answers from cache, 3 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 1: requestlist max 2 avg 0.666667 exceeded 0 jostled 0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: average recursion processing time 0.597449 sec Feb 25 14:45:54 router unbound[38083]: [38083:0] info: histogram of recursion processing times Feb 25 14:45:54 router unbound[38083]: [38083:0] info: [25%]=0 median[50%]=0 [75%]=0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: lower(secs) upper(secs) recursions Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.131072 0.262144 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.524288 1.000000 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 2: 1 queries, 0 answers from cache, 1 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: average recursion processing time 0.432144 sec Feb 25 14:45:54 router unbound[38083]: [38083:0] info: histogram of recursion processing times Feb 25 14:45:54 router unbound[38083]: [38083:0] info: [25%]=0 median[50%]=0 [75%]=0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: lower(secs) upper(secs) recursions Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.262144 0.524288 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 3: 8 queries, 0 answers from cache, 8 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 25 14:45:54 router unbound[38083]: [38083:0] info: server stats for thread 3: requestlist max 17 avg 5.625 exceeded 0 jostled 0 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: average recursion processing time 1.124708 sec Feb 25 14:45:54 router unbound[38083]: [38083:0] info: histogram of recursion processing times Feb 25 14:45:54 router unbound[38083]: [38083:0] info: [25%]=0.065536 median[50%]=0.762144 [75%]=1.5 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: lower(secs) upper(secs) recursions Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.000000 0.000001 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.032768 0.065536 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.262144 0.524288 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 0.524288 1.000000 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 1.000000 2.000000 2 Feb 25 14:45:54 router unbound[38083]: [38083:0] info: 2.000000 4.000000 1 Feb 25 14:45:54 router unbound[38083]: [38083:0] notice: Restart of unbound 1.13.1. Feb 25 14:45:54 router unbound[38083]: [38083:0] notice: init module 0: validator Feb 25 14:45:54 router unbound[38083]: [38083:0] notice: init module 1: iterator Feb 25 14:47:48 router filterdns[1478]: failed to resolve host vct.computerbb.org will retry later again. Feb 25 14:48:48 router filterdns[1478]: failed to resolve host vct.computerbb.org will retry later again. -
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. :)
-
@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
-
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!
-
@aaronssh awesome man! May i ask what hardware you are running? CPU / Chipset would be helpful.
-
@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.
-
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.
-
@rckf3 I upgraded to 1.13.1 as soon as I could and haven't had the service crash since.
