On reboot, I am consistently getting issues where it seems that FTL won't start properly.
Trying to restart FTL or the DNS server both hang.
pihole -r hangs on restarting FTL
systemctl restart pihole-FTL hangs
pihole restartdns hangs
I was able to somehow get things working again without a full wipe (not sure what did the trick), but another reboot caused the same issues to reoccur
I am also using Padd and I get the following output
This is likely the source of your problem. You have an enormous number of queries in the past 24 hours (~22 million). All of these are stored in the long term database and when you restart Pi-hole the most recent 24 hours is read to populate the query log. Your Pi-hole is likely not able to process this volume.
[2021-10-30 12:13:06.221 3912M] Imported 22175799 queries from the long-term database
[2021-10-30 12:13:06.221 3912M] -> Total DNS queries: 22175799
[2021-10-30 12:13:06.221 3912M] -> Cached DNS queries: 7128
[2021-10-30 12:13:06.221 3912M] -> Forwarded DNS queries: 22164558
[2021-10-30 12:13:06.221 3912M] -> Blocked DNS queries: 2199
[2021-10-30 12:13:06.221 3912M] -> Unknown DNS queries: 221
[2021-10-30 12:13:06.221 3912M] -> Unique domains: 2916
[2021-10-30 12:13:06.222 3912M] -> Unique clients: 25
Conditional forwarding likely has created a DNS loop that is multiplying queries. Your pihole.log shows the following (repeated many times). The router sent a request, and the request is sent back to the router for resolution. In this case, it's a DNS Discovery Service request.
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 128M Oct 30 12:37 /var/log/pihole.log
-----head of pihole.log------
Oct 30 00:08:29 dnsmasq[572]: query[PTR] b._dns-sd._udp.0.1.168.192.in-addr.arpa from 192.168.1.1
Oct 30 00:08:30 dnsmasq[572]: forwarded b._dns-sd._udp.0.1.168.192.in-addr.arpa to 192.168.1.1
Do these things to clear this and get Pi-hole restarted.
Disable conditional forwarding.
Run these commands to move the existing database to a new file name and create a fresh database. This will avoid pihole-FTL having to load all that data.
sudo service pihole-FTL stop
sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db
sudo service pihole-FTL start
Thanks for the clear explanation. I am still learning about networking so I wasn't sure what a typical volume of queries is.
It looks like clearing the logs did the trick. I will disable conditional forwarding and see if it holds up
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.