Fonta
July 26, 2018, 10:09pm
1
Expected Behaviour:
No error email
Actual Behaviour:
Getting an email with error during scheduled flush:
sed: can't read /etc/pihole/pihole-FTL.conf: No such file or directory
And also when you perform a manual flush:
Debug Token:
d73rkshxsy
There were previous topics about this same error, but since I upgraded yesterday I started receiving these emails.
See:
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
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
Debug Token: bbji1t5mo6
"Directory /etc/pihole/pihole-FTL.conf: no such file or directory"
TFL seems runing becouse he found it on ID XXX and the permission to kill it is denied.
I want to fix my problem with the auto flush logs by do a adit of the f´config file but its missing.
I've fixed my own install with the command "sudo touch /etc/pihole/pihole-FTL.conf", but I guess that shouldn't be the way to go.
jfb
July 26, 2018, 10:19pm
2
What was upgraded?
Did you update your OS, was it an update to Pi-Hole through pihole -up
, or did you move to a different branch of Pi-Hole?
Fonta
July 26, 2018, 10:51pm
3
I simply did a pihole -up.
Mcat12
July 27, 2018, 1:39am
5
2 Likes
system
Closed
August 17, 2018, 1:39am
6
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.