I don’t know if this is the right place for this, but I did a debug and it said to upload it here with the token.
What errors do you see that are of concern?
Sorry, I deleted them. I thought the log would show? I get about 6 a week. I’ll try reporting again as soon as I see them.
Thank you.
Are you referring to these warnings?
*** [ DIAGNOSING ]: Pi-hole diagnosis messages
count last timestamp type message blob1 blob2 blob3 blob4 blob5
------ ------------------- -------------------- ------------------------------------------------------------ -------------------- -------------------- -------------------- -------------------- --------------------
1 2022-07-14 11:57:30 DNSMASQ_WARN ignoring query from non-local network 71.202.52.118 (logged
only once)
1 2022-07-17 17:03:04 DNSMASQ_WARN no address range available for DHCP request via lo
1 2022-07-17 17:03:04 DNSMASQ_WARN not using configured address 192.168.0.51 because it is in u
se by the server or relay
3 2022-07-15 12:31:47 DNSMASQ_WARN reducing DNS packet size for nameserver 127.0.0.1 to 1232
1 2022-07-17 00:20:27 LOAD excessive load 4.44 4
1 2022-07-16 23:12:06 RATE_LIMIT 192.168.0.53 1000 60
Yes, especially the reducing DNS packet size and the excessive load.
I don’t know how a “non-local network” could get to my raspberry pi.
And I am assuming that the overload is due to some website trying to slam me with requests?
Take a look at our dnsmasq warnings page. It will explain these messages, with the exception of the load and rate limits.
https://docs.pi-hole.net/ftldns/dnsmasq_warn/
Look in your query log for a query from that first IP. It's a comcast IP, likely from your router, which is not normally a concern.
nslookup 71.202.52.118
118.52.202.71.in-addr.arpa name = c-71-202-52-118.hsd1.ca.comcast.net.
Excessive load can be something as simple as you running a gravity update. On a low-powered system, this can max out the CPU. You can disable that check if you don't want to see this warning:
https://docs.pi-hole.net/ftldns/configfile/#check_load
The rate limit shows that the client at IP 53 exceeded the default rate limit of 1000 queries in 60 seconds. This limit is also adjustable, and is discussed here:
Thank you very much! You have been extremely helpful!
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.