pihole docker stopped to work

monsen · Jan 22nd 2023

I found my pihole docker stopped working. This might have happened after a last update by Watchtower. Strange is that the log doesnt show anything relevant.

Also i remarked that it should run v5.15 but the env variable shows as version 4.0. No idea why.

Can i somehow activate debug logging without being able to start it to a point where i can access it via GUI?

Here is my log:

Code

  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
  [i] Status: Pending...
  [✓] Status: Retrieval successful
  [i] Analyzed 168834 domains, 15 domains invalid!
      Sample of invalid domains:
      - 0.0.0.0
      - broadcasthost
      - fe
      - ff
  [i] List stayed unchanged
  [i] Target: https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt
  [i] Status: Pending...
  [✓] Status: No changes detected
  [i] Analyzed 2701 domains
  [i] Target: https://reddestdream.github.io/Projects/MinimalHosts/etc/MinimalHostsBlocker/minimalhosts
  [i] Status: Pending...
  [✓] Status: No changes detected
  [i] Analyzed 710 domains
  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/data/KADhosts/hosts
  [i] Status: Pending...
  [✓] Status: Retrieval successful
  [i] Analyzed 90627 domains
  [i] List stayed unchanged
  [i] Target: https://raw.githubusercontent.com/StevenBlack/hosts/master/data/add.Spam/hosts
  [i] Status: Pending...
  [✓] Status: Retrieval successful
  [i] Analyzed 57 domains
  [i] List stayed unchanged
  [i] Target: https://v.firebog.net/hosts/static/w3kbl.txt
  [i] Status: Pending...
  [✓] Status: No changes detected
  [i] Analyzed 356 domains
  [i] Target: https://adaway.org/hosts.txt
  [i] Status: Pending...
  [✓] Status: No changes detected
  [i] Analyzed 7355 domains
  [i] Target: https://raw.githubusercontent.com/buggerman/SwitchBlockerForPiHole/master/Paranoid.txt
  [i] Status: Pending...
  [✓] Status: Retrieval successful
  [i] Analyzed 35 domains, 2 domains invalid!
      Sample of invalid domains:
      - api.accounts.nintendo.com:443
      - snake.sumo-services.co.uk:443
  [i] List stayed unchanged
  [i] Target: https://raw.githubusercontent.com/kboghdady/youTube_ads_4_pi-hole/master/youtubelist.txt
  [i] Status: Pending...
  [✓] Status: Retrieval successful
  [i] Analyzed 16840 domains, 1 domains invalid!
      Sample of invalid domains:

      - head
  [i] List stayed unchanged
  [i] Creating new gravity databases...
  [✓] Creating new gravity databases
  [i] Storing downloaded domains in new gravity database...
  [✓] Storing downloaded domains in new gravity database
  [i] Building tree...
  [✓] Building tree
  [i] Swapping databases...
  [✓] Swapping databases
  [✓] The old database remains available.
  [i] Number of gravity domains: 287497 (186968 unique domains)
  [i] Number of exact blacklisted domains: 51
  [i] Number of regex blacklist filters: 7
  [i] Number of exact whitelisted domains: 61
  [i] Number of regex whitelist filters: 2
  [i] Cleaning up stray matter...
  [✓] Cleaning up stray matter
  [✓] FTL is listening on port 53
     [✓] UDP (IPv4)
     [✓] TCP (IPv4)
     [✓] UDP (IPv6)
     [✓] TCP (IPv6)
  [✓] Pi-hole blocking is enabled
  Pi-hole version is v5.15 (Latest: v5.15)
  AdminLTE version is v5.18.1 (Latest: v5.18.1)
  FTL version is v5.20.1 (Latest: v5.20.1)
  Container tag is: 2023.01
e
s6-rc: info: service lighttpd successfully stopped
s6-rc: info: service pihole-FTL: stopping
Stopping pihole-FTL
s6-rc: info: service pihole-FTL successfully stopped
s6-rc: info: service _startup: stopping
s6-rc: info: service _startup successfully stopped
s6-rc: info: service _uid-gid-changer: stopping
s6-rc: info: service _uid-gid-changer successfully stopped
s6-rc: info: service cron: stopping
Stopping cron
s6-rc: info: service cron successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Display More

raulfg3 · Jan 22nd 2023

easy way: delete current container and redeploy stack with same confog.

monsen · Jan 22nd 2023

How do i migrate my existing config?

I have mapped some volumes for persistence, not sure if that is enough

I have done some config inside of pihole administration that i would like not to lose or do again.

EDIT: if I did read right, the important folder seems to be the /etc/pihole one.

So i assume i just recreate the container with all docker settings and point the volumes to the above on persistent storage (did not do a stack config for it up to here)? Anything else to be aware of?

raulfg3 · Jan 22nd 2023

yes, you only need to reuse persistent storage.

if still do not work , use other path for persistent storage, only DHCP persistent leases are usefull to restore on new path.

monsen · Jan 22nd 2023

My pihole has a fix IP anyways, so that should be fine.

monsen · Jan 22nd 2023

I deleted the old, created a new one. The new container did not appear.

Checking Portainer logs i see this:

Code

2023/01/22 09:43PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:43PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:43PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:44PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:45PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:45PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:45PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:46PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:46PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:46PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:47PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:48PM ERR client/client.go:94 > unexpected status code | status_code=403
2023/01/22 09:49PM ERR client/client.go:94 > unexpected status code | status_code=403

Display More

What is going on here?

All other containers works fine.

monsen · Jan 22nd 2023

Ok, tried again and gave it a new hostname. Now pihole is up and running perfectly fine and all cónfig is there.

Nevertheless Portainer is stuck in the above described loop. Seems like something is stuck with the old container but not visible to me,

monsen · Jan 22nd 2023

Just did a "docker system prune" on CLI which seems to have solved the issue. It removed some containers too that were stopped that i wanted to use again, but nothing really bad.

Seems to be solved!

pihole docker stopped to work

monsen Jan 22nd 2023

monsen Jan 22nd 2023

Participate now!

Similar Threads

AdGuard-Home

Unable to ping domain names when ssh'd into my OMV 5 box

Trying to achieve a few things with limited knowlede and only Google for help / Nextcloud / qBitorrent are examples of things I need direction on

Tags