MoJo2600 / pihole-kubernetes

PiHole on kubernetes
507 stars 178 forks source link

Liveness probe failure #57

Closed 11jwolfe2 closed 4 years ago

11jwolfe2 commented 4 years ago

I have been using version 4.4 of pi-hole for awhile now and went to update to version 5. When running on my cluster I get this error, that keeps pihole from starting.

kubelet, kube-worker-1 Readiness probe failed: Get http://10.42.1.14:80/admin.index.php: dial tcp 10.42.1.14:80: connect: connection refused

However If I uninstall the failed version 5 and roll back to 4.4, simply only changing the app version in values.yaml. It runs without issue.

I will provide any more details as needed. Just trying to figure out this issue.

MoJo2600 commented 4 years ago

Can you paste the output of the container log? I have version 5 running and it is working for me. I think there is a error during startup of the container.

11jwolfe2 commented 4 years ago

kubectl logs pihole-65466fd47f-l5xlc -n pihole -p

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole OK: Checks passed for /etc/resolv.conf DNS servers

nameserver 127.0.0.1 nameserver 8.8.8.8 [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u7

[i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf chown: changing ownership of '/etc/pihole/pihole-FTL.conf': Operation not permitted chown: cannot access '': No such file or directory chmod: cannot access '': No such file or directory chown: changing ownership of '/etc/pihole': Operation not permitted chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Using default DNS servers: 8.8.8.8 & 8.8.4.4 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "0.0.0.0", "VIRTUAL_HOST" => "pi.hole", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete [i] Neutrino emissions detected... [✓] Pulling blocklist source list into range

[✓] Preparing new gravity database [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts [✓] Status: Retrieval successful [i] Received 57380 domains

[i] Target: https://mirror1.malwaredomains.com/files/justdomains [✓] Status: No changes detected [i] Received 26854 domains

[i] Target: http://sysctl.org/cameleon/hosts [✓] Status: No changes detected [i] Received 20567 domains

[i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt [✓] Status: No changes detected [i] Received 38 domains, 3 domains invalid! Sample of invalid domains:

11jwolfe2 commented 4 years ago

This is what I get when I simply change 5.0 to 4.4 in the pihole.values.yml file and use helm install.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole OK: Checks passed for /etc/resolv.conf DNS servers

nameserver 127.0.0.1 nameserver 8.8.8.8 [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u7

[i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf chown: changing ownership of '/etc/pihole/pihole-FTL.conf': Operation not permitted chown: changing ownership of '/etc/pihole/regex.list': Operation not permitted chown: changing ownership of '/etc/pihole': Operation not permitted chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Using default DNS servers: 8.8.8.8 & 8.8.4.4 DNSMasq binding to default interface: eth0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "0.0.0.0", "VIRTUAL_HOST" => "pi.hole", Using IPv4 and IPv6 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete [i] Pi-hole blocking is enabled [i] Neutrino emissions detected... [✓] Pulling blocklist source list into range

[i] Target: raw.githubusercontent.com (hosts) [✓] Status: Retrieval successful

[i] Target: mirror1.malwaredomains.com (justdomains) [✓] Status: No changes detected

[i] Target: s3.amazonaws.com (simple_tracking.txt) [✓] Status: No changes detected

[i] Target: s3.amazonaws.com (simple_ad.txt) [✓] Status: No changes detected

[✓] Consolidating blocklists [✓] Extracting domains from blocklists [i] Number of domains being pulled in by gravity: 84217 [✓] Removing duplicate domains [i] Number of unique domains trapped in the Event Horizon: 84115 [i] Nothing to whitelist! [i] Number of regex filters: 0 [✓] Parsing domains into hosts format [✓] Cleaning up stray matter

[✓] DNS service is running [✓] Pi-hole blocking is Enabled [cont-init.d] 20-start.sh: exited 0. [cont-init.d] done. [services.d] starting services Starting pihole-FTL (no-daemon) as root Starting lighttpd [services.d] done. Starting crond

11jwolfe2 commented 4 years ago

you can close this issue, I found that is you add to many lists it breaks my set up, limiting them made it install properly I am also having the issue shown in issue #39 though.

MoJo2600 commented 4 years ago

Good to know