pfb_dnsnl (pfBlockerNG DNSBL) service won't start

jrey

Awesome !

I feel sorry about your efforts.

No problem, it was nice we could troubleshoot down to the actual cause of the DNSBL service not starting.

Even though the DNSBL was by all accounts "running", the service itself didn't show as started. The inability of the start to actually record/report on the lighttpd startup failure. Seems like a problem.

That of course is a completely different issue..

Have a great day!

bobslee

@jrey Indeed, it sometimes takes a few hurdles to find the actual cause is somewhere else.

I don't whether the DNSBL was actually operational, because now the browser responds with pfBNG page when I request the VIP.

Thanks and enjoy your day ! :)

jrey

@bobslee said in pfb_dnsnl (pfBlockerNG DNSBL) service won't start:

I don't whether the DNSBL was actually operational, because now the browser responds with pfBNG

I believe it was running because your screen capture of the dashboard showed packets and your provided DNS response showed 0.0.0.0 as the IP.

But what wasn't working was the web server to display the page if required.
(ie also a silent failure IMHO)

part of the service start sequence it to start lighttpd (but with that failing hard) the start service script saw that as a failure and showed the DNSBL status as stopped.

Needs work. Seems to me the error.log may have been an appropriate place for that hard failure to have been recorded.

Cheers

bobslee

@jrey I agree with your explanation.
My previous conclusion was silly here.. sorry (need a vacation).

The Lighttpd webserver (for WebGUI purpose) indeed isn't the same as the actual DNSBL service.
Thanks for sharpen my brain!