FTL is offline after update to 4.0

Nach dem update aud 4.0 ist der FLT service offline.

Ich hab die gesamten anleitungen und foren tips durchsucht und die genannten schritte unternommen --> kein erfolg :frowning:

Hat irgend jemand ne Idee ?
Raspi stretch, standard installation mit pivpn und samba

Danke,
setze jetzt erstmal auf die version 3 zurück

Was ist die ausgabe von

sudo systemctl status pihole-FTL.service

I have the same problem.

The output of your command:

● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Fri 2018-08-10 10:24:07 CEST; 3min 39s ago
Docs: man:systemd-sysv-generator(8)
Process: 311 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service

Aug 10 10:23:57 MockbaPi systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 10 10:23:57 MockbaPi pihole-FTL[311]: Not running
Aug 10 10:23:57 MockbaPi pihole-FTL[311]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Aug 10 10:24:07 MockbaPi su[607]: Successful su for pihole by root
Aug 10 10:24:07 MockbaPi su[607]: + ??? root:pihole
Aug 10 10:24:07 MockbaPi su[607]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 10 10:24:07 MockbaPi pihole-FTL[311]: dnsmasq: failed to create listening socket for port 53: Address already in use
Aug 10 10:24:07 MockbaPi systemd[1]: Started LSB: pihole-FTL daemon.

I have tried to restart the system, repair and after that reconfigure pihole, nothing worked.

The output of netstat -tupln
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 590/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 484/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 581/sshd
tcp6 0 0 :::80 :::* LISTEN 590/lighttpd
tcp6 0 0 :::53 :::* LISTEN 484/dnsmasq
tcp6 0 0 :::22 :::* LISTEN 581/sshd
udp 0 0 0.0.0.0:44963 0.0.0.0:* 363/avahi-daemon: r
udp 0 0 0.0.0.0:53 0.0.0.0:* 484/dnsmasq
udp 0 0 0.0.0.0:68 0.0.0.0:* 564/dhcpcd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 363/avahi-daemon: r
udp6 0 0 :::53 :::* 484/dnsmasq
udp6 0 0 :::45630 :::* 363/avahi-daemon: r
udp6 0 0 :::5353 :::* 363/avahi-daemon: r

Any help would be greatly appreciated!

thx for the fast reply :slight_smile:
I am until Monday evening not at home and have therefore the version v3.3.1 again installed.
Will try to create the output of "sudo systemctl status pihole-FTL.service" on Monday evening.

I am having the same issue with FTL 4.0 being offline line. Adddionally I have run pihole -d to debug and I do recieve output via the cli and via pihole web, but after each attempt I do not get a token only "use netcat" ad the log in /var/log/ is empty. The time stamp does seem to update after each run. But it is not updated which leads me to believe there is a perms issue. The debug long indicated after Pi-Hole log that "cat write error" . I can gladly upload the file I created from a copy and paste by unfortunately I do not have a token. Please advise. PLease note like others my pie hole status states DNS service is running and Pihole blocking is enabled. How ever pihole FTL status reads {1868} :dnsmasq failed to create listening socket for port 53 :persmission denied. Also not i have been through number pihole -r iterations. Also note I have statically set my eth0 int in the /etc/network.interfaces.d . Your assistance is greatly appreciated.

I have managed to create a debug token:
1y9eixc22u

Looks for me that dnsmasq is still running. After upgrade to V4 dnsmasq is implemented in FTLDNS.

Check to see if dnsmasq is running with

sudo systemctl status dnsmasq

It should say


If dnsmasq is active you need to stop it and restart FTLDNS in order for the DNS resolution to work properly.

sudo systemctl stop dnsmasq
sudo systemctl restart pihole-FTL.service

Once you have done this, you need to find out why dnsmasq is starting.

If you don’t use dnsmasq in your own setup, it is safe to uninstall it if you so chose to do so.

sudo apt remove dnsmasq however since it’s a dependency of Network Manager, it MIGHT be re-installed if your environment is set-up for auto updates and it will break FTLDNS again. (C to ramset)

Thank you for your quick reply.

Yes dnsmasq was still running (I don't know why), but uninstalling it did the trick. Thank you again! :slight_smile:

EDIT: I have updated my father's system (same config as mine, dedicated Rpi2 with Raspian Stretch Lite) and I have got the same error (so I removed dnsmasq there as well and everything is working now). I have also updated the pihole at my workplace, which is slightly different (Rpi3 instead of 2) and it is working without any extra magic. Do you think this error message has to do something with Rpi2?

Hello should I start a new thread to receive support? It does not seem my inability to generate a debug log or token? Please see my comments above.

3 posts were split to a new topic: Wifi Bridge With Dnsmasq

seems removing dnsmasq doesn't fix the issue (Pi B+ / 512MB RAM).

had to reinstall (uninstall and install).

phew.

also no solution for me

The output of "sudo systemctl status pihole-FTL.service":

pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2018-08-14 21:53:38 CEST; 7min ago
Docs: man:systemd-sysv-generator(8)
Process: 356 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUC
CGroup: /system.slice/pihole-FTL.service

Aug 14 21:53:26 matrix-sever systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 14 21:53:26 matrix-sever pihole-FTL[356]: Not running
Aug 14 21:53:27 matrix-sever pihole-FTL[356]: chown: cannot access '/etc/pihole/
Aug 14 21:53:38 matrix-sever su[1142]: Successful su for pihole by root
Aug 14 21:53:38 matrix-sever su[1142]: + ??? root:pihole
Aug 14 21:53:38 matrix-sever su[1142]: pam_unix(su:session): session opened for
Aug 14 21:53:38 matrix-sever pihole-FTL[356]: dnsmasq: cannot open or create lea
Aug 14 21:53:38 matrix-sever systemd[1]: Started LSB: pihole-FTL daemon.
lines 1-15/15 (END)

In order to upload a debug in your situation please try the following steps

  1. sudo nano /etc/resolv.conf
  2. change 127.0.0.1 to 9.9.9.9
  3. save
  4. run pihole -d

@mon_dieu Please try

sudo touch /etc/pihole/dhcp.leases
sudo service pihole-FTL restart

After complete new installation with Stretch, RaspAP and pihole
FTL offline
then
sudo touch /etc/pihole/dhcp.leases
sudo service pihole-FTL restart:
Failed to restart pihole-FTL.sevice: Unit pihole-FTL.service not found

Does the file

/etc/init.d/pihole-FTL

exist?

The file

/etc/init.d/pihole-FTL

doesn't exist.

Also
/usr/bin/pihole-FTL
doesn’t exist.

Output pihole -v
Pi-hole version is v4.0 (Latest: v4.0) AdminLTE version is v4.0 (Latest: v4.0) /opt/pihole/version.sh: line 19: pihole-FTL: command not found Latest FTL version is v4.0

Your installation is somehow broken, can you run pihole -r once again and post any suspiciously looking output (i.e., if it crashes)

@mon_dieu,
Can you confirm same output for the status command as in the other thread ?

If so, the pihole-FTL binary probably cant access that file anymore as its running with user "pihole" privileges now instead of root privies like dnsmasq did before the Pi-hole version 4 update.
And that file is not part of the normal basic Pi-hole install.

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

?

EDIT: Owh first get it to work again with pihole -r like @DL6ER instructed :wink:

EDIT2: I just read this bit that you could try: