pfsense 2.5.0 unbound stuck at 99-100% cpu and stop resolving
-
I was using pfsense 2.4.5 and dns resolving was working properly for external host names as well as internal hosts ...
since I upgraded to 2.5.0 about once a week the unbound resolver stops working (internal hostnames as well as external) ...
when this happens :
-top shows the unbound process taking 99% or more of the CPU
-resolver.log does not seem to contain anything suspicious (log activity stops right at about the time the resolver stopped working)
-dhcpd.log contains this line right around the time the problem started- Apr 3 19:53:19 pfSense dhclient[31512]: Creating resolv.conf
-restarting the service through the web console does nothing
-rebooting psfsense fix the issue (resolver works) for about 1 week ...- i upgraded to 2.5.1-RC but the issue persists ...
are there known issues with unbound following a 2.4.5 to 2.5.0 upgrade ?
are there configuration for the resolver (and dhcp ?) that need to be changed when upgrading to 2.5.0 ? -
@pbr6891 I found similar problem: unbound stopped working once after upgrade from 2.4.5 to 2.5.1. When I restarted unbound all worked again. No resolv.conf in dhcpd.log.
-
This post is deleted! -
Same issue here, tried reinstalling because I thought it shat itself during update (again) but it seems it's not just me. I'm running pfsense in kvm if that's relevant to someone