Pihole ignores MAXLOGAGE parameter in pihole-FTL.conf

Hi folks,

I'm running pihole on a Raspberry 3B since several months. OS is Raspbian-Stretch with latest updates.

Today I upgraded pihole from version (v4.1.1-0-g8d85d46 v4.1.1-0-gde7aa5a3 v4.1.2) to version (v4.2.2-0-gba1e94d v4.2-0-g347994d v4.2.3).

In the old and new version I had the parameter MAXLOGAGE in pihole-FTL.conf:
MAXLOGAGE=96.0

Under the old version I could see in /var/log/pihole-FTL.log the following entry:
[2019-03-04 23:58:32.981] MAXLOGAGE: Importing up to 96.0 hours of log data

Additionally on pihole's dashboard the title of the first broad box was: Queries over last 96 hours. And indeed pihole showed the last 96 hours of queries.

BUT under the new version I could see in /var/log/pihole-FTL.log the following entry:
[2019-03-09 14:10:39.717 4067] MAXLOGAGE: Importing up to 24.0 hours of log data

Curiously on pihole's dashboard the title of the first broad box is: Queries over last 96 hours. Because I upgraded today pihole just shows the queries of the last few hours. So at this moment for me it's not clear, whether it's just a display problem in the log file or query box or whether pihole indeed ignores the MAXLOGAGE parameter. I'll complete my report in a few days.

The inconsistent info in pihole-FTL.log and in the dashboard is definitely an error.

Thanks for reading and have a nice day.

Barney

Per the documentation for FTLDNS configuration (Configuration - Pi-hole documentation), the maximum value is 24 hours.

From v4.2.3 on, we simplified the code in a number of places to remove some of the most complex code structures. It turned out that they were a major player in the instability some users have seen with the v4.2 release.

Unfortunately, this simplification results in having to hard-code the maximum value for MAXLOGAGE and we chose 24 for obvious reasons. If you want to change it back to 96 hours, that should be possible but you'll have to compile pihole-FTL locally yourself (with a changed compile-time value). We can assist you with what you'd need to change and how to compile locally if you are interested.

2 Likes

@jfb Thanks for your reply.

The info related to MAXLOGAGE I found on different places in the internet were inconsistent: some cite a maximum of 31 days or 744 hours, some others 24 hours.

Based on the reply of DL6ER I assume 31 days / 744 hours is valid for versions before v4.2.3, 24 hours valid for v4.2.3 and later.

1 Like

@DL6ER Thanks for your reply and explanation.

My need for a MAXLOGAGE value of 96 (or any other value higher than 24) is not urgent. It's more kind of "nice to have". Nevertheless thanks for your offered support in compiling a custom version of pihole-FTL.

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