FTL keeps going offline after update to 3.0

Help
1

My FTL keeps going offline -- I'm not seeing a faster Web interface at all. When I check settings it says Pi-hole FTL (Not running).

Rebooting the Pi several times, and flushing the logs (5X) via the WebIF doesn't seem to help. The WebIF reports the following:
Pi-hole Version v3.0 Web Interface Version v3.0 FTL Version v2.6

2

Does FTL work for any amount of time or is it offline to begin with? Let's start by generating a debug log and we can take a look once you tell us the debug token.

3

Amazing support, as always, Jacob!

FTL was working for the first few minutes after a reboot, but the WebIF seemed slow. After refreshing the page, I can see the FTL offline red dot and the bottom corner says not running.

I re-flushed the logs using the button at the bottom (System Administration). The first time, I flushed the logs using the button at the top ("Query Logging"). Seems to be running currently after doing this. Not sure if there's a difference in these flush functions.

I generated a debug log anyway: l2kgss3uvz

4

So it's working right now?

I do see a PHP error in your log, but I'm not too privy to the Web side of things. @Mcat12 or @DL6ER can probably be of more use.

5

8 posts were split to a new topic: FTL offline on pihole -up

6

FTL down again.
Debug log: fipbivx9p2

7

What does sudo netstat -tulpn show? We're looking for the ports the FTL engine is working on for your installation.

8

Hello!

I am having the same issue with the FTL.

Debug: fyljvtj5wa
Netstat -tulpn results:
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 609/vncserver-x11-c
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 735/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 665/dnsmasq
tcp6 0 0 :::5900 :::* LISTEN 609/vncserver-x11-c
tcp6 0 0 :::80 :::* LISTEN 735/lighttpd
tcp6 0 0 :::53 :::* LISTEN 665/dnsmasq
udp 0 0 0.0.0.0:53 0.0.0.0:* 665/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:* 430/dhcpcd
udp 0 0 192.168.1.20:123 0.0.0.0:* 608/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 608/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 608/ntpd
udp 0 0 0.0.0.0:47294 0.0.0.0:* 412/avahi-daemon: r
udp 0 0 0.0.0.0:5353 0.0.0.0:* 412/avahi-daemon: r
udp6 0 0 :::546 :::* 430/dhcpcd
udp6 0 0 :::53 :::* 665/dnsmasq
udp6 0 0 fe80::d2dd:df8f:269:123 :::* 608/ntpd
udp6 0 0 ::1:123 :::* 608/ntpd
udp6 0 0 :::123 :::* 608/ntpd
udp6 0 0 :::44217 :::* 412/avahi-daemon: r
udp6 0 0 :::5353 :::* 412/avahi-daemon: r

edit Ran a repair. FTL spun up, then went offline.

Hope this helps!
Thanks!

9

Here goes...

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN 766/Xtightvnc
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2150/lighttpd
tcp 0 0 0.0.0.0:6001 0.0.0.0:* LISTEN 766/Xtightvnc
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 2938/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 848/sshd
tcp6 0 0 :::80 :::* LISTEN 2150/lighttpd
tcp6 0 0 :::53 :::* LISTEN 2938/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 848/sshd
udp 0 0 0.0.0.0:53 0.0.0.0:* 2938/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:* 841/dhcpcd
udp 0 0 192.168.86.2:123 0.0.0.0:* 928/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 928/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 928/ntpd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 423/avahi-daemon: r
udp 0 0 0.0.0.0:34837 0.0.0.0:* 423/avahi-daemon: r
udp6 0 0 :::53 :::* 2938/dnsmasq
udp6 0 0 fe80::115:e953:655b:123 :::* 928/ntpd
udp6 0 0 fe80::ba27:ebff:fee:123 :::* 928/ntpd
udp6 0 0 ::1:123 :::* 928/ntpd
udp6 0 0 :::123 :::* 928/ntpd
udp6 0 0 :::5353 :::* 423/avahi-daemon: r
udp6 0 0 :::58292 :::* 423/avahi-daemon: r

10

@Salmar can you get us the token from a pihole -d run please? Thank you.

Edit, apologies, did not notice the token from your post. Will take a look.

11

@SteveW25561 researching the issue now.

12

Can you both post copies of your /var/log/pihole-FTL.log files. If you can drop the on pastebin and post the links, or cat /var/log/pihole-FTL.log | nc tricorder.pi-hole.net 9999 and post the tokens so we can check the logs.

13

The original token was: fyljvtj5wa

After the repair function, the new token is: 4619ornzev

Thank you!

14

Here's my token for the posted log file: q7pqex691a
(I hope I did that correctly!)

15

Thanks, reviewing that log now.

1 Like
16

I am also having a problem with FTL not spinning up. Here is my log code tzb5hs974v.

I see this error which may be of relevance to the discussion here.

::: ---= Daemon Process Information
::: Checking 4711 port for pihole-FTL listener.
::: Failure: IPv4 Port not in use

17

@thadiyan Could you also send us the token from

cat /var/log/pihole-FTL.log | nc tricorder.pi-hole.net 9999
18

Here you go: ui1y0aq9ix

after my first comment, I manually started up pihole-FTL and now it seems to have started up. I did an upgrade with pihole -up and further totally rebooted the machine.

When I do a status on pihole-FTL I get the following.

root@storage:/etc/init.d# /etc/init.d/pihole-FTL status
status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

19

So does FTL appear to be running even with that output from pihole-FTL status?

20

Here you go:
5h1dnwtj0d