DNS Services and FTLDns will not start

Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

After a clean installation on my RPi3 I expect that the software works

Actual Behaviour:

The DNS and FTLDns services will not start. Also not after a reboot, repair, uninstall-install action.

Debug Token:

sqejr9mpmu

2

Which build of Stretch are you using?

3

I’m using the latest version:
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian

4

The problems I've are the same as: After update to 4.1.1 DNS no longer responding - #12 by DL6ER

5

There is an open GitHub issue with FTL and Raspbian image 2018-11-13. You can check that and see if it is related to your specific problem.

https://github.com/pi-hole/pi-hole/issues/2566

6

Yes, this is the same kind of problem I have.

7

I've still the same problem with the latest version.

8

Make a new debug token (pihole -d)

9

Here is the new token: cuyfaqjwnh

I had to fix first my resolv.conf settings befoe I could upload the debug file.

10

I see that your pihole-FTL service was started, didn't crash but still isn't running.

When you run

sudo service pihole-FTL start
sudo service pihole-FTL status

does it report pihole-FTL to be running?

Please also check a few minutes later again if the status command still reports it it as being active.

11

This is what I see:
pi@raspberrypi:~ $ sudo service pihole-FTL start

pi@raspberrypi:~ $ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2019-02-05 17:08:04 CET; 3h 17min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 355 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUC
   CGroup: /system.slice/pihole-FTL.service

feb 05 17:07:50 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
feb 05 17:07:50 raspberrypi pihole-FTL[355]: Not running
feb 05 17:08:04 raspberrypi su[945]: Successful su for pihole by root
feb 05 17:08:04 raspberrypi su[945]: + ??? root:pihole
feb 05 17:08:04 raspberrypi su[945]: pam_unix(su:session): session opened for us
feb 05 17:08:04 raspberrypi pihole-FTL[355]: dnsmasq: cannot open or create leas
feb 05 17:08:04 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pi@raspberrypi:~ $ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2019-02-05 17:08:04 CET; 3h 22min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 355 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCC
   CGroup: /system.slice/pihole-FTL.service

feb 05 17:07:50 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
feb 05 17:07:50 raspberrypi pihole-FTL[355]: Not running
feb 05 17:08:04 raspberrypi su[945]: Successful su for pihole by root
feb 05 17:08:04 raspberrypi su[945]: + ??? root:pihole
feb 05 17:08:04 raspberrypi su[945]: pam_unix(su:session): session opened for use
feb 05 17:08:04 raspberrypi pihole-FTL[355]: dnsmasq: cannot open or create lease
feb 05 17:08:04 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
13

This line got ellipsized.

Please run

journalctl -u pihole-FTL

Afterwards, we can provide the solution to the issue you're seeing.

16

Here is the output from both commnands:
pi@raspberrypi:~ $ sudo netstat -nltup | grep 'Proto|:53 |:67 |:80 |:471'
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 635/lighttpd
tcp6 0 0 :::80 :::* LISTEN 635/lighttpd

pi@raspberrypi:~ $ journalctl -u pihole-FTL
-- Logs begin at Thu 2016-11-03 18:16:43 CET, end at Tue 2019-02-05 21:25:04 CET.
feb 05 17:07:50 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
feb 05 17:07:50 raspberrypi pihole-FTL[355]: Not running
feb 05 17:08:04 raspberrypi su[945]: Successful su for pihole by root
feb 05 17:08:04 raspberrypi su[945]: + ??? root:pihole
feb 05 17:08:04 raspberrypi su[945]: pam_unix(su:session): session opened for use
feb 05 17:08:04 raspberrypi pihole-FTL[355]: dnsmasq: cannot open or create lease
feb 05 17:08:04 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pi@raspberrypi:~ $

17

Are you sure you copied the complete lines? Can you try enlarging your terminal windows such that the line

doesn't get cropped?

18

-- Logs begin at Thu 2016-11-03 18:16:43 CET, end at Tue 2019-02-05 21:30:01 CET. --
feb 05 17:07:50 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
feb 05 17:07:50 raspberrypi pihole-FTL[355]: Not running
feb 05 17:08:04 raspberrypi su[945]: Successful su for pihole by root
feb 05 17:08:04 raspberrypi su[945]: + ??? root:pihole
feb 05 17:08:04 raspberrypi su[945]: pam_unix(su:session): session opened for user pihole by (uid=0)
feb 05 17:08:04 raspberrypi pihole-FTL[355]: dnsmasq: cannot open or create lease file /var/lib/misc/dnsmasq.leases: Permission denied
feb 05 17:08:04 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
~

19

Thanks, please run

sudo touch /var/lib/misc/dnsmasq.leases
sudo chown pihole:pihole /var/lib/misc/dnsmasq.leases
sudo service pihole-FTL restart

And check again:

sudo service pihole-FTL status

Please also run and post the output of

grep -v '#\|^$' -R /etc/dnsmasq.*
20 
pi@raspberrypi:~ $ sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
   Active: active (exited) since Tue 2019-02-05 21:45:33 CET; 45s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3240 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 3305 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

feb 05 21:45:22 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
feb 05 21:45:22 raspberrypi pihole-FTL[3305]: Not running
feb 05 21:45:32 raspberrypi su[3368]: Successful su for pihole by root
feb 05 21:45:32 raspberrypi su[3368]: + ??? root:pihole
feb 05 21:45:32 raspberrypi su[3368]: pam_unix(su:session): session opened for user pihole by (uid=0)
feb 05 21:45:32 raspberrypi pihole-FTL[3305]: FTL started!
feb 05 21:45:33 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.


pi@raspberrypi:~ $ grep -v '#\|^$' -R /etc/dnsmasq.*
/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.conf.old:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/gravity.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/black.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:dhcp-name-match=set:wpad-ignore,wpad
/etc/dnsmasq.d/01-pihole.conf:dhcp-ignore-names=tag:wpad-ignore
/etc/dnsmasq.d/01-pihole.conf:server=208.67.222.222
/etc/dnsmasq.d/01-pihole.conf:server=208.67.220.220
/etc/dnsmasq.d/01-pihole.conf:server=2620:0:ccc::2
/etc/dnsmasq.d/01-pihole.conf:server=2620:0:ccd::2
/etc/dnsmasq.d/01-pihole.conf:domain-needed
/etc/dnsmasq.d/01-pihole.conf:bogus-priv
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:server=/fritz.box/192.168.178.1
/etc/dnsmasq.d/01-pihole.conf:server=/178.168.192.in-addr.arpa/192.168.178.1
/etc/dnsmasq.d/aiy-usb-gadget.conf:interface=usb0
/etc/dnsmasq.d/aiy-usb-gadget.conf:dhcp-range=192.168.11.50,192.168.11.100,255.255.255.0,2h
/etc/dnsmasq.d/aiy-usb-gadget.conf:dhcp-option=3
/etc/dnsmasq.d/aiy-usb-gadget.conf:dhcp-option=6

pi@raspberrypi:~ $

21

It looks for me if everything works fine now.

22

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