PiHole - Cannot Start PiHole

Product support
1

Hello,

First I would say thanks for building such a great set of tools ! I discovered Balena via HackerNews and the Air Quality monitoring project (Which I followed and is working great since 2 weeks) .

I wanted to try to set up the piHole thingy, following your guide . But I can’t seem to make it work :frowning:

Here are the logs for PiHole service :

16.04.19 22:59:53 (+0200) pihole [cont-finish.d] done.
16.04.19 22:59:53 (+0200) pihole [s6-finish] syncing disks.
16.04.19 22:59:53 (+0200) pihole [s6-finish] sending all processes the TERM signal.
16.04.19 22:59:56 (+0200) pihole [s6-finish] sending all processes the KILL signal and exiting.
16.04.19 22:59:59 (+0200) Service exited ‘pihole sha256:19dcad5f4557fb66c88373ed05fadca88cd068cf9557bbf0abf812b3988a0cd2’
16.04.19 22:58:45 (+0200) pihole [s6-finish] sending all processes the KILL signal and exiting.
16.04.19 22:58:48 (+0200) Service exited ‘pihole sha256:19dcad5f4557fb66c88373ed05fadca88cd068cf9557bbf0abf812b3988a0cd2’

It seems like the service is restarting in a loop .

When I try to access the public url I get :

tunneling socket could not be established: socket hang up

What did I miss ? ^^

4

Hello,

I was able to reproduce the issue you’re experiencing. I’d recommend posting an issue on the GitHub repository with the Pi-Hole project code to get this resolved. In my case, I actually found an earlier error from dnsmasq, which points to an unknown network interface eth0. I don’t have ethernet plugged in, so I’m not sure why this is showing up.

17.04.19 09:57:26 (-0700)  pihole  ::: Testing pihole-FTL DNS: sudo: unable to resolve host 519c2bf
17.04.19 09:57:27 (-0700)  pihole  
17.04.19 09:57:27 (-0700)  pihole  dnsmasq: unknown interface eth0
17.04.19 09:57:27 (-0700)  pihole  [cont-init.d] 20-start.sh: exited 1.
17.04.19 09:57:27 (-0700)  pihole  [cont-finish.d] executing container finish scripts...
17.04.19 09:57:27 (-0700)  pihole  [cont-finish.d] done.
17.04.19 09:57:27 (-0700)  pihole  [s6-finish] syncing disks.
17.04.19 09:57:27 (-0700)  pihole  [s6-finish] sending all processes the TERM signal.
17.04.19 09:57:30 (-0700)  pihole  [s6-finish] sending all processes the KILL signal and exiting.
17.04.19 09:57:31 (-0700) Service exited 'pihole sha256:75c7e05445d6f010e63af119a95a4a683c129beba1fc764929115a8704b2fc77'

Cheers,
Trevor Sullivan

5

@pcgeek86 @gh_tbrunain just checking: if you’re not using the wired ethernet interface did you use wlan0 instead of eth0 in the DNSMASQ_LISTENING service variable?

P.S. welcome to the forums and thank you for the compliments @gh_tbrunain!

6

@chrisys I set that variable and restarted the container, but still see the same results.

7

Hello @pcgeek86, @chrisys, same issue here.
Followed the same guide, and I get this:

18.04.19 02:19:00 (+0200) Restarting service 'pihole sha256:04872edd40f6ccfe9369f7ef9b31810b5c2525fdf89fedd68a390f8f2aac5dc4'
18.04.19 02:19:00 (+0200) <pihole> [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
18.04.19 02:19:01 (+0200) <pihole> [s6-init] ensuring user provided files have correct perms...exited 0.
18.04.19 02:19:01 (+0200) <pihole> [fix-attrs.d] applying ownership & permissions fixes...
18.04.19 02:19:01 (+0200) <pihole> [fix-attrs.d] 01-resolver-resolv: applying... 
18.04.19 02:19:02 (+0200) <pihole> [fix-attrs.d] 01-resolver-resolv: exited 0.
18.04.19 02:19:02 (+0200) <pihole> [fix-attrs.d] done.
18.04.19 02:19:02 (+0200) <pihole> [cont-init.d] executing container initialization scripts...
18.04.19 02:19:02 (+0200) <pihole> [cont-init.d] 20-start.sh: executing... 
18.04.19 02:19:02 (+0200) <pihole> [cont-init.d] 20-start.sh: exited 267.
18.04.19 02:19:02 (+0200) <pihole> [cont-finish.d] executing container finish scripts...
18.04.19 02:19:02 (+0200) <pihole> [cont-finish.d] done.
18.04.19 02:19:02 (+0200) <pihole> [s6-finish] syncing disks.
18.04.19 02:19:03 (+0200) <pihole> [s6-finish] sending all processes the TERM signal.
18.04.19 02:19:06 (+0200) <pihole> [s6-finish] sending all processes the KILL signal and exiting.
18.04.19 02:19:13 (+0200) Service exited 'pihole sha256:04872edd40f6ccfe9369f7ef9b31810b5c2525fdf89fedd68a390f8f2aac5dc4'
18.04.19 02:19:20 (+0200) Restarting service 'pihole sha256:04872edd40f6ccfe9369f7ef9b31810b5c2525fdf89fedd68a390f8f2aac5dc4'

I don’t know what [cont-init.d] 20-start.sh: exited 267 means, but I suppose that there’s something wrong in start.sh…?
By the way, I am running this application on Raspberry Pi version 1 and I have double checked the variables, that seem ok.

Any suggestion?