Unbound frequently restarting and occasionally crashing
-
I've looked through the forums and google and can't seem to see what could be causing it. Nothing unusual in the logs other than a frequent restart (every 1 to 5 minutes) and then on the occasion a full crash. Uploading full log and a snippet including the crash. Greatly appreciate any pointers for how I can diagnose this.
resolverlog.txt
pfSense 2.5.2-rw-r--r-- 1 root unbound 2220 Oct 8 00:31 unbound.conf unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf
Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: Restart of unbound 1.12.0. Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: init module 0: validator Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: init module 1: iterator Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: start of service (unbound 1.12.0). Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: service stopped (unbound 1.12.0). Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0 Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 2: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0 Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 3: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0 Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: Restart of unbound 1.12.0. Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: init module 0: validator Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] notice: init module 1: iterator Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: start of service (unbound 1.12.0). Oct 7 08:51:58 pfSense unbound[2307]: [2307:3] info: generate keytag query _ta-4f66. NULL IN Oct 7 08:57:23 pfSense unbound[2307]: [2307:0] info: service stopped (unbound 1.12.0).
...
Oct 7 08:57:24 pfSense unbound[2307]: [2307:0] notice: Restart of unbound 1.12.0. Oct 7 08:57:24 pfSense unbound[2307]: [2307:0] fatal error: Could not read config file: /unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf
-
In the same second :
@nazuro said in Unbound frequently restarting and occasionally crashing:
Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: start of service (unbound 1.12.0).
Oct 7 08:51:55 pfSense unbound[2307]: [2307:0] info: start of service (unbound 1.12.0).
that's not good at all. Ones or twice a day ? Ok. Every second is
Many services, not just unbound, well get / can get restarted on "interface" events, for example, when whey go down and up again. See main log.
Or : if a DHCP lease request comes in, see DHCP log.
So, whatsup ? -
@gertjan It seems to average out around 15 restarts per hour. I can't seem to see any interface events in the main log but perhaps I'm looking for the wrong thing.
There are lots of DHCP requests coming in but nothing unusual.
-
This issue has been out there for over a year. At this point, I think it's safe to say
It's not a developer/maintainer priority and may never be fixed. Unchecking Register DHCP leases in the DNS Resolver and unckecking Register DHCP static mappings in the DNS Resolver. Stopped the crashes. Of course you will have to come up with an alternatives to resolve hosts that are local. For me I set up BIND on a linux server. -
@linuxgae said in Unbound frequently restarting and occasionally crashing:
and unckecking Register DHCP static mappings in the DNS Resolver.
That one isn't needed as they are loaded on system start, and only change when the admin adds a static lease, which is not very often.
@linuxgae said in Unbound frequently restarting and occasionally crashing:
Of course you will have to come up with an alternatives to resolve hosts that are local
Give your known local device, the ones you need to talk to, like NASes, printers and other file servers a static MAC lease and you'll be fine.