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
1 Like
mibere
March 26, 2018, 2:23pm
2
Hello,
the named file is optional. It only exists (after your manual creation) if you would like to change some of the default settings:
The Pi-hole FTL engine
But maybe the devs should check if this is however an issue.
Thanks for the reply. Yeah it doesn't seem to be causing any issues, and I'm happy to ignore it (or even created an empty file). Just figured it might be worth reporting since this is beta for the new FTLDNS.
1 Like
The file is indeed option, but FTL never complained about it prior. Perhaps @DL6ER wants to check that.
DL6ER
March 27, 2018, 6:11pm
5
It doesn't seem like FTL complained. but rather that pihole -f
complained. I agree, this warning should be silenced. It seems to be present in development
as well. I think it is this line @jacob.salmela :
# Please see LICENSE file for your rights under this license.
colfile="/opt/pihole/COL_TABLE"
source ${colfile}
readonly PI_HOLE_SCRIPT_DIR="/opt/pihole"
utilsfile="${PI_HOLE_SCRIPT_DIR}/utils.sh"
source "${utilsfile}"
# In case we're running at the same time as a system logrotate, use a
# separate logrotate state file to prevent stepping on each other's
# toes.
STATEFILE="/var/lib/logrotate/pihole"
# Determine database location
DBFILE=$(getFTLConfigValue "files.database")
if [ -z "$DBFILE" ]; then
DBFILE="/etc/pihole/pihole-FTL.db"
fi
# Determine log file location
2 Likes
DL6ER
April 5, 2018, 8:32pm
6
2 Likes
system
Closed
April 26, 2018, 8:32pm
7
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.