Expected Behaviour:
An error appearing on the Pihole Web interface, to appear in sequence within the FTL.log
Actual Behaviour:
There is no entry with same timestamp in the FTL.log; Note that Web shows local time which is GMT+2
Possibly the error entries have been deleted from the log file. It is unclear to me what triggers this log to purge its contents.
Pi-hole diagnosis would aggregate information from many sources, not just FTL.log
.
That connection error would be in pihole.log
.
jfb
March 13, 2025, 5:29pm
3
The diagnosis log also only shows one instance of a repeated warning. You may just be seeing the first time it happened.
Yeah, I got that. But what triggers the FTL.log being purged. It was less than 12hrs that I checked and the data was gone, whereas other times I reckon it keeps data for days.
It's likely not being purged. It's a linux feature called logrotate that archives log files after a configured amount of time in order to not run out of disk space.
If you run ls -la /var/log/pihole
you should see a lot of compressed files with the same names. These are the old logs.
1 Like
jfb
March 13, 2025, 8:55pm
6
The logs rotate per a rotation schedule installed by Pi-hole. Nightly at midnight.
-rw-r----- 1 root root 358 Sep 5 2024 /etc/pihole/logrotate
/var/log/pihole/pihole.log {
su root root
daily
copytruncate
rotate 5
compress
delaycompress
notifempty
nomail
}
/var/log/pihole/FTL.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
/var/log/pihole/webserver.log {
su root root
weekly
copytruncate
rotate 3
compress
delaycompress
notifempty
nomail
}
Your FTL log directory will typically look like this:
ls -lha /var/log/pihole/FTL*
-rw-r----- 1 pihole pihole 0 Mar 13 00:00 /var/log/pihole/FTL.log
-rw-r----- 1 pihole pihole 8.2K Mar 13 00:00 /var/log/pihole/FTL.log.1
-rw-r----- 1 pihole pihole 255 Mar 10 00:00 /var/log/pihole/FTL.log.2.gz
-rw-r----- 1 pihole pihole 1.2K Mar 8 00:00 /var/log/pihole/FTL.log.3.gz
1 Like