Disk shortage (/var/log/pihole/FTL.log) ahead: 99% used

Help Community Help
21

At the moment, there is no indication of any kind of disk issue.

You also said you are using DietPi. DietPi clears logs hourly and the space problem was apparently fixed.

Your new log doesn't show any warnings about Disk shortage. Also, the log doesn't show a loop (at least nothing in the few lines we can see).

As CallMeCurious and Bucking_Horn said before, there was a DNS loop in the first post.

The router was sending the query to Pi-hole (... from 192.168.1.1) and Pi-hole was sending the same query back to the router (... to 192.168.1.1), resulting in a loop and a big log file:

Then you showed some more log lines (11th post) and there was a different loop, between Pi-hole and Unbound:

Apparently your Unbound was using Pi-hole as upstream server, causing a loop.
Did you fix that?

22

Note (unrelated to your issue):

Pi-hole IP is really 192.168.1.217, but in your configuration you have set 192.168.1.215 as Pi-hole's IP address:

*** [ DIAGNOSING ]: Setup variables
(...)
IPV4_ADDRESS=192.168.1.215/24

You need to run pihole -r to reconfigure your Pi-hole to use the correct IP.

23

Is using 127.0.01 5335 in unbound causing the loop? I dont see any reference to my router IP or .217

Running pihole -r to repair, which I have done numerous times, do I need to use the reconfigure option? That will wipe all my settings? thxs

24

Ran the reconfigure option and the .215 IP remains

25

This is causing the normal query (Pi-hole to Unbound):

  • forwarded 100.1.168.192.in-addr.arpa to 127.0.0.1#5335

But I'm not sure how Unbound was sending queries back to Pi-hole, like this:

  • query[PTR] 108.1.168.192.in-addr.arpa from 127.0.0.1
26

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.