Bug #11126
closed
DNS Resolver service not running after updating the pfBlockerNG-devel package
Added by Craig Leres over 4 years ago.
Updated over 4 years ago.
Description
I'm using 2.4.5_1 and the last several times I've updated the pfBlockerNG-devel package using web gui I've had to manually start the DNS Resolver service. It looks like unbound is stopped and started several times during the pfBlockerNG-devel upgrade process but is not running at completion.
I'll attach some log files.
Files
There isn't a lot that's useful in those logs unfortunately. The error on there seems to indicate an issue creating the DNSBL certificate during the upgrade. I would try removing and installing the package again. Then try recreating the issue and post the corresponding logs.
- Status changed from New to Closed
I just upgraded from 3.0.0_3 to 3.0.0_5 and when this process completed no unbound was running and I had to start one manually.
I uninstalled pfSense-pkg-pfBlockerNG-devel and had to manually start unbound.
Finally I reinstalled pfSense-pkg-pfBlockerNG-devel I had to restart unbound again.
I don't think the "Remove /var/unbound from pkg since it's part of core" is relevant, reinstalling or uninstalling pfSense-pkg-pfBlockerNG-devel does not remove that directory since it contains files.
This issue is still unresolved...
Just updated from 3.0.0_5 to 3.0.0_6 and was again left with no unbound running. (Should I open a completely new bug report?)
Also available in: Atom
PDF