I recently swapped to using Unbound with my PiHole and it's been working great. Since then, I've noticed my router being rate limited (pihole shows rate limit on 192.168.1.1) with the default rate of 1,000; I'm assuming it's because everything is going through the router and there's a lot of stuff running, so I just need to increase that. I went to my query log and clicked the button to show all to inspect what had been going on, and it failed with an error. At that moment, my DNS completely died network-wide for around 3 minutes. It seems to be working now.
I'm not going to paste the entire log because it's just this single line over and over (after some of the rate limiting lines, which will be further down in this post):
[2023-07-12 23:29:27.088 21178/T21179] WARN: Could not write() everything in getAllQueries() [src/api/api.c:1074]: Broken pipe
Another support post here referencing "broken pipe" ended with the solution of not piping commands to echo; I'm not doing that, though, this is just happening when I attempt to load all queries (are you guys piping something during that process?) I don't know if that error led to the DNS issue, or the DNS outage led to that error.
In addition, the rate limiting in my router is more ridiculous than I'd expected. I have over 2,000 entries in a row of the error below:
These are peppered between every 20-50 instances of the error (with slightly different values each time):
[2023-07-12 23:18:35.275 21178M] Resizing "FTL-queries" from 38535168 to (692224 * 56) == 38764544 (/dev/shm: 39.3MB used, 4.1GB total, FTL uses 39.3MB)
[2023-07-12 01:27:05.904 21178M] Resizing "FTL-dns-cache" from 81920 to (5376 * 16) == 86016 (/dev/shm: 38.4MB used, 4.1GB total, FTL uses 38.4MB)
And the error:
[2023-07-12 00:02:53.664 21178M] Rate-limiting 192.168.1.1 for at least 27 seconds
[2023-07-12 00:03:20.868 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:03:45.858 21178M] Rate-limiting 192.168.1.1 for at least 35 seconds
[2023-07-12 00:04:20.930 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:05:06.047 21178M] Rate-limiting 192.168.1.1 for at least 14 seconds
[2023-07-12 00:05:20.992 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:12:17.376 21178M] Rate-limiting 192.168.1.1 for at least 3 seconds
[2023-07-12 00:12:20.483 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:12:40.709 21178M] Rate-limiting 192.168.1.1 for at least 40 seconds
[2023-07-12 00:13:20.546 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:13:56.446 21178M] Rate-limiting 192.168.1.1 for at least 24 seconds
[2023-07-12 00:14:20.608 21178/T21195] Ending rate-limitation of 192.168.1.1
[2023-07-12 00:14:45.607 21178M] Rate-limiting 192.168.1.1 for at least 35 seconds
...and so on. Seriously, my log file consists entire of that rate limiting section (but much longer), then the single line from above, followed by the pipe error spamming the rest of the file. That's all there is, which is the only reason I'm not linking it.
Is this something I should be worried about, or should I just increase my rate limit (to what, 5,000? Is there a way to increase it just for one device?) and forget this happened?
- No weird quirks or modifications to my PiHole. Everything is set up identically to the official guides and has been functioning perfectly for months. The only change was setting up Unbound a few days ago, and that's been working fine as well.
- Debug Token: https://tricorder.pi-hole.net/vFrh2W0l/