And yes, the Pi will use /etc/resolv.conf for it's internal resolver, but that file is dynamically generated, and when dhcpcd5 is added to the mix that file will change depending on the status of the daemon. But we install a new resolver dnsmasq and that's the one that clients use, we actually want the Pi-hole to use another resolver so it's not circularly depending on itself to resolve. If dnsmasq is down for restart, the Pi is deaf to the world for a second and that could be the wrong second for things to go down.
Thanks for the nice explanations, Dan.
Sorry to hear the RPi is so ideosyncratic, I had hoped to use this opportunity to actually begin learning how to live with systemd.
I started over, without disabling dhcp, nor updating my installation prior to installing pi-hole. Things went a lot better, and the script did complete this time - I was wrong about it finishing on the previous attempt.
It does work, and continues to work even after the upgrade, with its new kernel! Sorry to extend this thread after a posted solution.
No problem at all, it's a strange oddity and one that we're trying to see about working around. Glad to hear it's working and if there are any other issues let us know and we'll see about trying to fix them for you.
Sorry to bring this old thread back to live (well, not that old)...but I am bumping into the same issue too:
Here is my debug toke:
Your debug token is : bjthr781u0
I am on Jessie as well:
> No LSB modules are available.
> Distributor ID: Raspbian
> Description: Raspbian GNU/Linux 8.0 (jessie)
> Release: 8.0
> Codename: jessie
I am just wondering if this means the only way we have to resolve this issue is we have to do a refresh install of NOOBS (format the SDCard, load NOOBS and then reimage and run pi-hole install BEFORE the dist-upgrade?
I have done quite a bit of configuration on the pi (it is used for other purposes as well) and it just seem to be a of trouble to reinstall this.
Would appreciate if there is an alternative solution that does not require fresh install.
Please post your install log (/etc/pihole/install.log) and another debug log (we recently had to do some maintenance on the server, so there currently aren't any logs).
Thanks a lot for your quick reply, here is the output of the install.log (I have already run a pihole -r since that was suggested so unfortunately this wasn't the most original log:
pihole -d (debug log):
and pihole -g output:
pihole -g
:::
::: WARNING: /etc/pihole/setupVars.conf missing. Possible installation failure.
::: Please run 'pihole -r', and choose the 'reconfigure' option to reconfigure.
and the /etc/pihole folder:
ls -l /etc/pihole
total 8
-rw-r--r-- 1 root root 599 Nov 19 13:11 install.log
-rw-r--r-- 1 root root 248 Nov 19 13:12 whitelist.txt
Since you are missing the setupVars.conf file, there are no settings to save. Try curl -sSL https://install.pi-hole.net | bash again and see if the installer still fails at the firewall configuration.
Interesting, I just did a rpi-update and now this seem to work!
This is my pi-hole -c output:
average: 0.25, 0.17, 0.10
0 days, 1 hours, 25 minutes.Blocking: 205388
Queries: 2662
Pi-holed: 67 (2.51%)
So for anyone who runs into this problem in future, run a rpi-update to update to the newest version and then run pi-hole -r to reinstall.
It's good that the issue is fixed upstream, but I wouldn't generally do an rpi-update as that will get you bleeding edge kernel without the support. Raspbian used to update that way but now it's just a testing ground for new features.
1 Like
Ah I see...so rpi-update is no longer updating to production but to beta heh? That's why hardly anymore mentioned that.
Thanks a lot once again for your quick reply, especially over the weekend!
One more irrelevant question (and perhaps I should start a new thread for this), how can I use Pi-Hole without messing up things like eBates and all those cashback programs? Or Pi-Hole shouldn't be breaking those?
Those are harder to block as they are usually served directly from the same domain. So unless the host is using ads.ebates.com instead of ebates.com to serve things, then it's an all or nothing approach. We work better when combined with an in-brower solution for that kind of thing. Whitelist ebates.com and then use a browser extension to catch the things we'll be missing. And there's always somebody around to answer questions, sometimes more.
Thanks, I've been getting the same issue after reinstalling pi-hole on Jessie Lite. I'll reflash and try again.