Hey guys would be great if we get some basic Information about FTL how to activate... What it does exactly...
BTW do to the FTL option on the Web interface the option to see the temperature is gone
thanks for any help
1 Like
Yeah, the information that FTL is not running seemed more important than the temperature. However, we like to leave the load and the memory still there, so it might be obvious why FTL is not running (like extraordinary high load of 99% memory consumption etc.).
I tried it yesterday evening and it is perfectly fine to switch to the full FTL branch by just doing (this is on a fresh installation):
- Install Pi-hole as usual
- Run
pihole checkout dev
What steps did you do to get to this screenshot you showed?
i just went on my web interface and logged in took a screen
so did i get that right the option FTL is not available now?
you say install pi-hole as usual do you mean like this?
curl -sSL https://install.pi-hole.net | bash
or in the comandline
pihole -r
Yeah, FTL will only be installed by switching the core repo to development and running pihole -r + Repair afterwards or using the new checkout feature
i went on dev yesterday but okay i'll try pihole -r thanks
- fresh install raspbian jessie lite march 2017
- installed dnsmasq v2.77test4
- installed dnscrypt 1.9.4 with four (4) resolvers
- installed (fresh) pihole v2.13.2
- ran pihole checkout dev
- ran pihole -r
- removed resolvers from /etc/dnsmasq.d/01-pihole.conf
- added four (4) dnscrypt resovers to /etc/dnsmasq.d/04-dnscrypt.conf
- removed resolvers from /etc/pihole/setupVars.conf
- reboot
- ran pihole -f
- ran sudo apt-get update && sudo apt-get -y upgrade
dashboard results (2 undefined resolvers)
Hmm, please tell me what
http://pi.hole/admin/api.php?overTimeDataForwards&getForwardDestinationNames
says.
{"over_time":{"1489575900":[1,1,4,1,0,0],"1489576500":[1,1,6,1,0,0],"1489577100":[1,1,6,1,0,0],"1489578300":[11,5,16,5,0,0],"1489578900":[13,13,28,13,0,0],"1489579500":[4,4,4,4,0,0],"1489580100":[5,5,6,5,0,0],"1489580700":[28,43,28,43,0,0],"1489581300":[9,12,9,9,0,0],"1489582500":[52,89,43,81,0,0],"1489583100":[37,62,15,16,0,0],"1489583700":[29,27,16,43,0,0],"1489584300":[14,14,14,14,0,0]}}
And
pihole-FTL version
?
Should be at least v1.5. Otherwise, please run pihole -up
pihole-FTL version
v1.5
pihole -up
::: Checking for updates...
::: Pi-hole Core: up to date
::: FTL: update available
:::
::: FTL out of date
:::
::: Downloading latest version of FTL...
::: Detected ARM-hf architecture (armv7+)
::: Installing FTL... transferred... done.
:::
::: Web Interface: up to date
:::
::: FTL version is now at v1.5.1
:::
::: Starting pihole-FTL service... done.
:::
::: Enabling pihole-FTL service to start on reboot... done.
solved ...
Well, that is good, although nothing changed in between v1.5 to v1.5.1 at this part of the code.
I reinstalled everything again, after the problem was gone. This time I got FTL 1.5.1 from the start, no upgrade required. Initially the graph showed 6 resolvers, witch seamed normal, because you have to select some resolvers during installation. I chose OpenDNS and the resolvers were even listed by name.
I then removed the resolvers from /etc/dnsmasq.d/01-pihole.conf and /etc/pihole/setupVars.conf. The graph still showed 6 resolvers, but the name of the OpenDNS servers changed into undefined.
I ran pi-hole -f, no change, but after a reboot the undefined resolvers were gone.
How do you clear the FTL cached data?
Does pihole -f also clears the FTL cached data?
Yes, but only indirectly, it will reparse your log after flushing. But keep in mind that it will also scan through pihole.log.1 if you have FTL running on default settings (no config file), so flushing once is not sufficient to drag the data out of FTL's view.
New setup, so there is no pihole.log.1. Yet, the first time, the undefined resolvers did NOT go away with pihole -f.
I'm testing all of this on a test pi, powered down over night.
I've just started it up and ran pihole-FTL:
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
Make sure it exists
however, that log exists, with yesterdays timestamp, I can't find any logrotate instructions, so I assume it isn't rotated (yet)?
What should (could) be the content of the FTL-pihole conf file (where and what)?
Check again if there is no pihole.log.1 file. It will be created when you flush or when logrotation happens.
Who is the owner and what about the rights?
me@nanoPi:~# ls -lh /var/log/pihole-FTL.log
-rw-r--r-- 1 pihole pihole 13M Mar 16 07:53 /var/log/pihole-FTL.log
I'll wirte an FAQ for this soon, currently there is no clean documentation for this since the config file exists only since two days and there is a lot of changes still going on.
ls -lh /var/log/pihole-FTL.log
-rw-r--r-- 1 pihole pihole 13K Mar 16 08:52 /var/log/pihole-FTL.log
so this is correct
about pihole -f (= really logrotate)
I think both You and I forgot about this
Witch implies pihole -f doesn't do anything (if logrotate is available) unless it's really a new day.
There is a pihole.log.1 today, but there wasn't yesterday, despite all the pihole -f commands.
The pihole-FTL error remains, although everything seems to be working...
Have you tried starting pihole-FTL as some user or have you used the command sudo service pihole-FTL start? Only the latter one will take care that pihole-FTL is also started with UID of the user pihole.
Well, that should not happen. pihole -f forces the rotation, no matter how much time has passed. I already thought about removing it altogether because it was used to heal a sitation that you won't encounter with FTL anymore. We have had a test setup running on a small server with 4GB of memory and it worked quite fine until reaching about 50 millions DNS queries.
Not sure what you mean. pihole -f adds the --force flag to the command.
pihole-FTL
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
Make sure it exists
sudo service pihole-FTL stop
sudo service pihole-FTL start
pihole-FTL
FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed!
Make sure it exists
sudo pihole-FTL
FATAL: Another FTL process is already running! Exiting...