FTL is offline

Help
1

Description

I've upgraded Pi-hole 4.x to 5.0 on my Raspberry Pi B. Unfortunately, the web interfaces says that FTL is offline. I've read many articles about similar problem descriptions, and whatever I tried didn't help (start manually, change permission on log files, restart Rasperry, etc.). I'm completely stuck with this problem.

If you are Experiencing issues with a Pi-hole install that has non-standard elements

I'm using a Pi-hole 5.0 standard installation, with apache/php as webserver. I've two Raspberry Pi in my network (Raspberry Pi 2 with IP .18, Raspberry Pi 3 with IP .19), and the problem occurs on both devices. Both should act as DNS (and later as properly configured DHCP server, but DHCP is disabled on both devices at the moment). All of the data in this question is from Raspberry Pi 3 with IP .19.

Expected Behaviour:

FTL is online and DNS resolution is working.

Actual Behaviour:

FTL is reported offline and DNS resolution is not working.

Debug Token:

https://tricorder.pi-hole.net/3st282k2hi

Thanks for your help!

3

What is the output of the following commands from the Pi terminal:

sudo service pihole-FTL status

sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:5335 \|:8953 \|:67 \|:80 \|:471'

4

First of all, thank you for your quick reply!!!

pi@raspberrypi:/var/log $ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated)
   Active: active (exited) since Sat 2020-05-16 12:09:39 CEST; 1 day 4h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 8712 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SU

Mai 16 12:09:38 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Mai 16 12:09:39 raspberrypi pihole-FTL[8712]: Not running
Mai 16 12:09:39 raspberrypi su[8737]: (to pihole) root on none
Mai 16 12:09:39 raspberrypi su[8737]: pam_unix(su:session): session opened for u
Mai 16 12:09:39 raspberrypi pihole-FTL[8712]: dnsmasq: bad DHCP host name at lin
Mai 16 12:09:39 raspberrypi su[8737]: pam_unix(su:session): session closed for u
Mai 16 12:09:39 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.

pi@raspberrypi:/var/log $ sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:5335 \|:8953 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp6       0      0 :::80                   :::*                    LISTEN      544/apache2         
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1160/chromium-brows 
udp        0      0 224.0.0.251:5353        0.0.0.0:*                           1108/libpepflashpla 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           316/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                316/avahi-daemon: r
5

3 posts were split to a new topic: Watchtower automatic upgrade to Pi-hole v5

6

This is the problem. The line is truncated, so we can't see the whole error. What is the ouput of these commands from the Pi terminal:

pihole-FTL dnsmasq-test

sudo grep -v '#\|^$' -R /etc/dnsmasq.*

8

You have an old file in there that appears to be causing problems. Delete it with this:

sudo rm /etc/dnsmasq.conf.old

Also, in /etc/dnsmasq.conf, this line is not needed - edit the file and delete that line.

user=root

After these changes are made, then run sudo service lighttpd restart and see if things are working.

9

Thank you so much, that was the decisive hint!

I had generated the file 04-pihole-static-dhcp.conf.sav in Microsoft Excel on a windows system (by formula, in order to prevent typos), and this file had Windows line breaks (CR/LF) instead of Linux line breaks (CR).

Could you please tell me where the file 04-pihole-static-dhcp.conf (I had renamed it to 04-pihole-static-dhcp.conf.sav in order to avoid errors due to typos - obviously didn't work out that well) is referred to?

10

A post was merged into an existing topic: Watchtower automatic upgrade to Pi-hole v5 —- not sure if watchtower did this. Don’t see log

11

This is used if you are using Pi-hole as DHCP server, and with static leases.

12

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.