Trimming the FTL.log

My pi hole is complaining about a full disk, only there is no full disk. So I installed ncdu to find the issue, and there are non, but did find FTL.log is 22gig, how does one trim or delete the log.

Thanks in advance.

Raspberry Pi 4 Model B Rev 1.4
8gig
64 gig sd

The log should rotate nightly. Please post the output of the following command from the Pi terminal:

ls -lha /var/log/pihole/*.*

pi@raspberrypi:~ $ ls -lha /var/log/pihole/*.*

-rw-r----- 1 pihole pihole 24G May 16 08:05 /var/log/pihole/FTL.log
-rw-r----- 1 pihole pihole 117M May 14 00:00 /var/log/pihole/FTL.log.3.gz
-rw-r----- 1 pihole pihole 3.8K May 13 00:00 /var/log/pihole/FTL.log.4.gz
-rw-r----- 1 pihole pihole 9.7M May 14 14:54 /var/log/pihole/pihole_debug.log
-rw-r----- 1 pihole pihole 320K May 16 08:05 /var/log/pihole/pihole.log
-rw-r----- 1 pihole pihole 156K May 16 00:00 /var/log/pihole/pihole.log.1
-rw-r----- 1 pihole pihole 752K May 15 00:00 /var/log/pihole/pihole.log.2.gz
-rw-r----- 1 pihole pihole 429K May 14 00:00 /var/log/pihole/pihole.log.3.gz
-rw-r----- 1 pihole pihole 494K May 13 00:00 /var/log/pihole/pihole.log.4.gz
-rw-r----- 1 pihole pihole 513K May 12 00:00 /var/log/pihole/pihole.log.5.gz
-rw-r----- 1 pihole pihole 6.3K May 12 03:44 /var/log/pihole/pihole_updateGravity.log
-rw-r----- 1 pihole pihole 2.2K May 16 07:33 /var/log/pihole/webserver.log

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

https://tricorder.pi-hole.net/4pmB5Gf9/

It appears that at one time, you had regex debugging turned on, and about 17,000 regex entries (I didn't count, but there are a LOT of them).

-rw-r----- 1 pihole pihole 24G May 16 10:06 /var/log/pihole/FTL.log
   -----head of FTL.log------
   2024-05-14 00:15:48.453 [694M] WARNING: Connection error (::ffff:127.0.0.1#53): failed to send UDP request (Network unreachable)
   2024-05-14 00:25:50.254 [694M] WARNING: Connection error (::ffff:127.0.0.1#53): failed to send UDP request (Network unreachable)
   2024-05-14 00:38:21.114 [694M] WARNING: Connection error (::ffff:127.0.0.1#53): failed to send UDP request (Network unreachable)
   2024-05-14 00:38:21.164 [694M] DEBUG_REGEX: Regex: 462208 (database) -> 12359 (internal)
   2024-05-14 00:38:21.166 [694M] DEBUG_REGEX: Regex: 462208 (database) -> 12359 (internal)
   2024-05-14 00:38:21.172 [694M] DEBUG_REGEX: Regex allow (FTL 0, DB 179358) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?blokada\.org$" (regex)
   2024-05-14 00:38:21.172 [694M] DEBUG_REGEX: Regex allow (FTL 1, DB 179359) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?brave-http-only\.com$" (regex)
   2024-05-14 00:38:21.172 [694M] DEBUG_REGEX: Regex allow (FTL 2, DB 179363) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?mozillazine\.org$" (regex)
   2024-05-14 00:38:21.172 [694M] DEBUG_REGEX: Regex allow (FTL 3, DB 179364) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?mozit\.cloud$" (regex)
   2024-05-14 00:38:21.173 [694M] DEBUG_REGEX: Regex allow (FTL 4, DB 179365) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?moz\.works$" (regex)
   2024-05-14 00:38:21.174 [694M] DEBUG_REGEX: Regex allow (FTL 5, DB 179366) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?onion$" (regex)
   2024-05-14 00:38:21.174 [694M] DEBUG_REGEX: Regex allow (FTL 6, DB 179369) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?services\.mozaws\.net$" (regex)
   2024-05-14 00:38:21.174 [694M] DEBUG_REGEX: Regex allow (FTL 7, DB 179371) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?torproject\.org$" (regex)
   2024-05-14 00:38:21.174 [694M] DEBUG_REGEX: Regex allow (FTL 8, DB 179373) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?webservices\.mozgcp\.net$" (regex)
   2024-05-14 00:38:21.174 [694M] DEBUG_REGEX: Regex allow (FTL 9, DB 179374) NO match: "1-courier.push.apple.com" (input) vs. "^(.*\.)?wpengine\.com$" (regex)

This will quickly fill up your FTL log.

Found it after I sent that, anyway to trim this.

Stop FTL, delete the log, restart FTL.

sudo service pihole-FTL stop

sudo rm /var/log/pihole/FTL.log

sudo service pihole-FTL start

Thank you for your help.