No startup Unbound

RonpfS

When the widget send an unbound-control stats_noreset during an unbound reload, unbound may hang and may need to be kill -9 .

Change the pfblockerNG Widget DNSBL Resolver Query frequency from 5 sec to 60 or 120 sec.

You can also try to enable DNSBL Live Reload Resync so pfblockerNG wont reload unbound.

Qinn

[2.4.4-RELEASE][root@pfSense.localdomain]/root: sockstat | grep :953
unbound  unbound    63945 22 tcp4   127.0.0.1:953         *:*
?        ?          ?     ?  tcp4   127.0.0.1:953         127.0.0.1:57064

@johnpoz Your guess is as good as mine , only the first line is unbound?

Qinn

@ronpfs said in No startup Unbound:

DNSBL Resolver Query frequency

Thanks RonpfS for stepping in, I can't seem to locate the;

"Change the pfblockerNG Widget DNSBL Resolver Query frequency from 5 sec to 60 or 120 sec."

You've mentioned, of course I will try to enable DNSBL Live Reload Resync and report back.

RonpfS

@qinn said in No startup Unbound:

Thanks RonpfS for stepping in, I can't seem to locate the;
"Change the pfblockerNG Widget DNSBL Resolver Query frequency from 5 sec to 60 or 120 sec."

Click on the Wrench Icon on the pfBlockerNG widget

Qinn

@ronpfs said in No startup Unbound:

@qinn said in No startup Unbound:

Thanks RonpfS for stepping in, I can't seem to locate the;
"Change the pfblockerNG Widget DNSBL Resolver Query frequency from 5 sec to 60 or 120 sec."

Click on the Wrench Icon on the pfBlockerNG widget

Thanks, duhhhh, missed out that one, stupid me. I will try that first and if that don't work the
enable DNSBL Live Reload Resync, but it has to wait for tomorrow as some rsync's are running and after that backups are kickin in, so tomorrow I will try and report back!

Thanks again

Qinn

@RonpfS setting DNSBL Resolver Query frequency to 60 sec, didn't do much. Next tried the *DNSBL Live Reload Resync, but unfortunately it did not do much either. Still unbound is not running after a reboot...

Anyone any idea's?

Cheers Qinn

Gertjan

@qinn said in No startup Unbound:

Anyone any idea's?

Yep.
If you can works a day or two without DNSBL , disable it all together.
Reboot pfSense.
Check.

Doing so will rule out any problems related to DNSBL - or not ....

@qinn said in No startup Unbound:

Still unbound is not running after a reboot...

That is, it should start after a boot. The logs do shows this.
But shortly after that it gets probably restarted, so it stops, and then can't start again.

Qinn

@gertjan I stopped and disabled pfb_dnsbl and pfb_filter and rebooted 3 times, on all of them unbound was running and there were no errors in the General Log concerning Unbound and accessing the GUI/Dashboard after reboot now took a few seconds, instead of minutes. It seems very likely that the culprit has found, pfb_dnsbl and pfb_filter and Unbound don't play well , but now to a solution. I hope that @BBcan177 can shed some light on it.

johnpoz

@qinn said in No startup Unbound:

pfb_dnsbl and pfb_filter and Unbound don't play well

I would concur on this ;) no offense to BBcan177 great work on the package.. But it has become lets call it very complex ;)

Gertjan

@johnpoz said in No startup Unbound:

@qinn said in No startup Unbound:

pfb_dnsbl and pfb_filter and Unbound don't play well

I would concur on this ;) no offense to BBcan177 great work on the package.. But it has become lets call it very complex ;)

@metoo

But the fact is :
pfb_dnsbl import big or can I call them huge - lists.
And when he set them up, it kicks unbound, who starts to parse all these lists using. This needs a lot resources.
I do think a 'correct' setup of pfb_dnsbl would be a good solution.

johnpoz

@gertjan said in No startup Unbound:

pfb_dnsbl import big or can I call them huge - lists.

Yup would concur there as well ;)