Can't fix: Stopping pihole-FTL pihole-FTL: no process found #1414
Comments
|
Just tried to replicate from scratch without custom config I had before and still it will start failing after approximately 10-12 hours of running without issues. Does anybody have any clue? My setup was running okay for over a year and suddenly version: "3.7"
services:
pihole:
container_name: default.dns.pihole
image: pihole/pihole:latest
restart: always
hostname: pihole
ports:
- 53:53/tcp
- 53:53/udp
- 67:67/udp
- 50009:80/tcp
cap_add:
- NET_ADMIN
volumes:
- $PWD/pihole/etc-pihole/:/etc/pihole/
- $PWD/pihole/etc-dnsmasq.d/:/etc/dnsmasq.d/
- $PWD/custom.list:/etc/pihole/custom.list
- $PWD/resolv.conf:/etc/resolv.conf
environment:
- TZ=${TZ}
- DNSMASQ_USER=root
- WEBPASSWORD=*
- DNS1=1.1.1.1
- DNS2=no |
|
Are you able to see if there is anything helpful in |
|
Looks suspicious. Is this style supported? If you don't want to set a second DNS server, just remove the line. |
Not explicitly, but it is just ignored/converted to the correct format docker-pi-hole/src/s6/debian-root/usr/local/bin/bash_functions.sh Lines 262 to 268 in ca7b911 The container only used to support having |
Seems issue with the DB.. However I tried from scratch and deleted EDIT: |
|
I wonder if it's to do with the available SHM size (64MB by default in Docker), though I'm surprised that it is filling up that quickly TBH. How many clients use your Pi-hole / How many queries are you seeing (per day/hour/minute!) As a band-aid, try increasing the amount of shared memory available to the container and seeing if it lasts for longer: https://datawookie.dev/blog/2021/11/shared-memory-docker/ I say band-aid, because really it's kicking the can down the road. Maybe there is something else wrong here, too. |
Not much.. its just for the home use for about 8-15 clients regular use. (OR not, I have just noticed that one service for online radio called sinusbot might be stuck in DNS querying - look at
Used this command for the docker-compose: FTL.log pihole.log |
And here is the root cause of your issue, Are you running sinusbot in a container? If so, and you want it to stop spamming your Pi-hole logs, just point the DNS somehwere else. I do this with a couple of other containers that don't really need blocking in them. I think in compose you can juse do |
Thanks for the help! |
|
I have the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Like a week ago my pihole container started to be unreliable. I have noticed many logs of:
This happens sooner or later.. Now I cant get rid of this behavior. You notice that my setup is using Bind as the only upstream DNS forwarder, which then is using something public like Cloudflare. I ruled out issues with Bind using Couldflare servers directly..
Things I tried in order:
pihole-FTL.dbpihole-FTL.confto force its default configcustom.listHow to reproduce the issue
These common fixes didn't work for my issue
docker runexample(s) in the readme (removing any customizations I added)The text was updated successfully, but these errors were encountered: