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

    Unbound occasionally crashing

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 3 Posters 1.3k Views
    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.
    • J
      Justin53
      last edited by

      I'm running pfSense 2.3.2, unbound will sometimes crash after my OpenVPN client acquires a new IP address. I've checked the systemlogs & unbound logs and I can't see what maybe causing this to happen…

      1 Reply Last reply Reply Quote 0
      • J
        Justin53
        last edited by

        I believe this maybe the error that could be causing it?

        php-fpm 	93864 	/rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1470845134] unbound[23702:0] error: bind: address already in use [1470845134] unbound[23702:0] fatal error: could not open ports
        
        1 Reply Last reply Reply Quote 0
        • luckman212L
          luckman212 LAYER 8
          last edited by

          Do you run the Service Watchdog package by any chance?

          That error looks like a race condition where something tried to trigger Unbound to launch but it was already running, hence the 2nd instance could not bind to port 53 and failed to start.  Probably a harmless error and not indicative of a crash.  There are probably a lot of race conditions like this still in pfSense. My very uninformed understanding is that some of that will be improved for the 3.x releases (still a long way off) which aim to eliminate PHP. I could be quite wrong about this.

          1 Reply Last reply Reply Quote 0
          • P
            pfcode
            last edited by

            If you have pfBlockerNG installed and have DNSBL enabled. That will be causing it. Its not a package issue but pfSense.

            Release: pfSense 2.4.3(amd64)
            M/B: Supermicro A1SRi-2558F
            HDD: Intel X25-M 160G
            RAM: 2x8Gb Kingston ECC ValueRAM
            AP: Netgear R7000 (XWRT), Unifi AC Pro

            1 Reply Last reply Reply Quote 0
            • J
              Justin53
              last edited by

              @pfcode:

              If you have pfBlockerNG installed and have DNSBL enabled. That will be causing it. Its not a package issue but pfSense.

              I do have PfBlockerNG installed however DNSBL is disabled. Also I'm not using service watchdog.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.