Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unbound crashes periodically with signal 11

    2.5 Development Snapshots (Retired)
    36
    105
    24.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • jimpJ
      jimp Rebel Alliance Developer Netgate @chrcoluk
      last edited by

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

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      F 1 Reply Last reply Reply Quote 3
      • C
        ccb056
        last edited by ccb056

        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 11

        Feb 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.
        1 Reply Last reply Reply Quote 0
        • S
          Smoothrunnings @jkv
          last edited by

          @jkv

          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. :)

          1 Reply Last reply Reply Quote 0
          • F
            fibrewire @jimp
            last edited by 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

            1 Reply Last reply Reply Quote 0
            • aaronsshA
              aaronssh
              last edited by

              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!

              F 1 Reply Last reply Reply Quote 1
              • F
                fibrewire @aaronssh
                last edited by

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

                1 Reply Last reply Reply Quote 0
                • L
                  LamaZ @Salander27 0
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • R
                    RckF3
                    last edited by

                    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.

                    H 1 Reply Last reply Reply Quote 1
                    • H
                      hans109h @RckF3
                      last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • M
                        MoonSire
                        last edited by

                        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.
                        M 1 Reply Last reply Reply Quote 0
                        • M
                          MoonSire @MoonSire
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • R
                            RckF3
                            last edited by

                            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.

                            1 Reply Last reply Reply Quote 0
                            • jimpJ
                              jimp Rebel Alliance Developer Netgate
                              last edited by

                              For this particular issue it would be the same on both

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • GertjanG Gertjan referenced this topic on
                              • P popcorn9499 referenced this topic on
                              • P popcorn9499 referenced this topic on
                              • First post
                                Last post