Unbound occasionally crashing



  • 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…



  • 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
    


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



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



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


Log in to reply