Error message while executing cron command pihole flush once quiet

[jpgpi250]

Since version v3.3.1, piholeLogFlush.sh generates an error when there is no FTL configuration file.

sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory

This is because piholeLogFlush.sh contains a sed command to determine the FTL database location, however, it doesn't anticipate there may not be an FTL configuration file (default configuration).

workaround:
Create /etc/pihole-FTL.conf, containing at least one line:

DBFILE=/etc/pihole/pihole-FTL.db

[mibere]

Thanks for the report.

pihole-FTL.conf: No such file or directory

Please follow the below template, it will help us to help you! Expected Behaviour: No warning sent to me via e-mail nightly Actual Behaviour: I'm getting the following e-mail from cron nightly since I upgraded to the new FTLDNS. Cron root@blackhole PATH="$PATH:/usr/local/bin/" pihole flush once quiet sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory Debug Token: s9rvi9huq6

[jacob.salmela]

We should probably just create pihole-FTL.conf on install, even if it's just an empty file. Should reduce confusion of people having to make the file if it doesn't exist when they want to configure the file.

[DL6ER]

The error message should be silenced now

Silence error in log flush subroutine when no pihole-FTL.conf can be found

@jacob.salmela

We should probably just create pihole-FTL.conf on install, even if it’s just an empty file. Should reduce confusion of people having to make the file if it doesn’t exist when they want to configure the file.

I agree, shall we add a dummy file to the repo and copy it over during pihole -r if the conf file does not exist yet?