DNS service not running FTL offline

Help Community Help
1

Dear Pi-Hole Community.

I had Pi-Hole Running. Then I installed RaspAP but then identified and read online, that they don't coexist well. I then uninstalled RaspAP and installed Pi-Hole again, but since then, the DNS service is not running anymore.

I searched the forum and tried several things, but nothing worked. Hope anybody can help and find the issue.

Thanks!

Expected Behaviour:

Pi-Hole should work and block my traffic.

  • Raspbian GNU/Linux Buster (10)
  • Node.js Version|v14.15.0|
  • Npm Version|v6.14.8|
  • Raspberry Pi 4

Actual Behaviour:

DNS service is NOT running
The FTL service is offline!

Debug Token:

https://tricorder.pi-hole.net/ml0zkkmnrq
(Moderator edit: Explicit debug log removed, the token is enough.)

pi@homebridge:~ $ sudo ss -tulpn
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("node",pid=3151,fd=36))
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("node",pid=3151,fd=31))
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("node",pid=3091,fd=20))
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* users:(("avahi-daemon",pid=337,fd=12))
udp UNCONN 0 0 0.0.0.0:1900 0.0.0.0:* users:(("node",pid=3151,fd=28))
udp UNCONN 0 0 0.0.0.0:1900 0.0.0.0:* users:(("deCONZ",pid=447,fd=13))
udp UNCONN 0 0 0.0.0.0:48135 0.0.0.0:* users:(("avahi-daemon",pid=337,fd=14))
udp UNCONN 0 0 0.0.0.0:68 0.0.0.0:* users:(("dhclient",pid=607,fd=6))
udp UNCONN 0 0 0.0.0.0:631 0.0.0.0:* users:(("cups-browsed",pid=487,fd=7))
udp UNCONN 0 0 :53906 : users:(("avahi-daemon",pid=337,fd=15))
udp UNCONN 0 0 :5353 : users:(("avahi-daemon",pid=337,fd=13))
tcp LISTEN 0 5 0.0.0.0:5900 0.0.0.0: users:(("vncserver-x11-c",pid=527,fd=12))
tcp LISTEN 0 50 0.0.0.0:80 0.0.0.0: users:(("deCONZ",pid=447,fd=7))
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=536,fd=3))
tcp LISTEN 0 5 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=430,fd=7))
tcp LISTEN 0 20 127.0.0.1:25 0.0.0.0:* users:(("exim4",pid=1060,fd=3))
tcp LISTEN 0 100 0.0.0.0:1883 0.0.0.0:* users:(("mosquitto",pid=754,fd=5))
tcp LISTEN 0 50 0.0.0.0:443 0.0.0.0:* users:(("deCONZ",pid=447,fd=12))
tcp LISTEN 0 1024 0.0.0.0:8093 0.0.0.0:* users:(("lighttpd",pid=26772,fd=4))
tcp LISTEN 0 511 192.168.0.186:43581 0.0.0.0:* users:(("node",pid=3151,fd=25))
tcp LISTEN 0 511 *:8581 : users:(("node",pid=3091,fd=22))
tcp LISTEN 0 511 *:39399 : users:(("node",pid=3151,fd=21))
tcp LISTEN 0 511 :51785 : users:(("node",pid=3151,fd=32))
tcp LISTEN 0 5 [::]:5900 [::]: users:(("vncserver-x11-c",pid=527,fd=11))
tcp LISTEN 0 511 *:44495 : users:(("node",pid=3151,fd=23))
tcp LISTEN 0 511 :45327 : users:(("node",pid=3151,fd=19))
tcp LISTEN 0 511 :46033 : users:(("node",pid=3151,fd=26))
tcp LISTEN 0 511 :33107 : users:(("node",pid=3151,fd=41))
tcp LISTEN 0 511 :44211 : users:(("node",pid=3151,fd=57))
tcp LISTEN 0 128 [::]:22 [::]: users:(("sshd",pid=536,fd=4))
tcp LISTEN 0 511 :37687 : users:(("node",pid=3151,fd=44))
tcp LISTEN 0 5 [::1]:631 [::]: users:(("cupsd",pid=430,fd=6))
tcp LISTEN 0 100 [::1]:8888 [::]: users:(("pigpiod",pid=427,fd=0))
tcp LISTEN 0 511 :33017 : users:(("node",pid=3151,fd=64))
tcp LISTEN 0 20 [::1]:25 [::]: users:(("exim4",pid=1060,fd=4))
tcp LISTEN 0 100 [::]:1883 [::]: users:(("mosquitto",pid=754,fd=6))
tcp LISTEN 0 1024 [::]:8093 [::]: users:(("lighttpd",pid=26772,fd=5))
tcp LISTEN 0 511 *:42301 : users:(("node",pid=3151,fd=60))
tcp LISTEN 0 511 *:33085 : users:(("node",pid=3151,fd=49))
tcp LISTEN 0 511 *:44895 : users:(("node",pid=3151,fd=46))

pi@homebridge:~ $ sudo systemctl status --full --no-pager pihole-FTL.service
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Tue 2020-11-17 21:01:25 CET; 11s ago
Docs: man:systemd-sysv-generator(8)
Process: 21680 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

Nov 17 21:01:24 homebridge systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 17 21:01:25 homebridge pihole-FTL[21680]: Not running
Nov 17 21:01:25 homebridge su[21698]: (to pihole) root on none
Nov 17 21:01:25 homebridge su[21698]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 17 21:01:25 homebridge pihole-FTL[21680]: dnsmasq: cannot read /etc/raspap/adblock/domains.txt: No such file or directory
Nov 17 21:01:25 homebridge su[21698]: pam_unix(su:session): session closed for user pihole
Nov 17 21:01:25 homebridge systemd[1]: Started LSB: pihole-FTL daemon.

2

Some remainders of your raspAP installation still interfere.

Get rid of the file that references /etc/raspap/adblock/domains.txt.

The following commands may help:

ls -lah /etc/dnsmasq.d/

grep -nRv '^#\|^$' /etc/dnsmasq.d
3

Guess I found the file. Should I just delete the file /etc/dnsmasq.d/090_adblock.conf? Or just delete the content of it?

pi@homebridge:~ $ grep -nRv '^#|^$' /etc/dnsmasq.d
/etc/dnsmasq.d/01-pihole.conf:21:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:22:addn-hosts=/etc/pihole/custom.list
/etc/dnsmasq.d/01-pihole.conf:25:localise-queries
/etc/dnsmasq.d/01-pihole.conf:28:no-resolv
/etc/dnsmasq.d/01-pihole.conf:32:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:34:log-queries
/etc/dnsmasq.d/01-pihole.conf:35:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:37:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:39:log-async
/etc/dnsmasq.d/01-pihole.conf:40:server=1.1.1.1
/etc/dnsmasq.d/01-pihole.conf:41:server=1.0.0.1
/etc/dnsmasq.d/01-pihole.conf:42:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:43:server=/use-application-dns.net/
/etc/dnsmasq.d/090_adblock.conf:1:conf-file=/etc/raspap/adblock/domains.txt
/etc/dnsmasq.d/090_adblock.conf:2:addn-hosts=/etc/raspap/adblock/hostnames.txt
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:1:dhcp-host=DC:A6:32:4B:36:46,192.168.0.186,raspi

4

That's it. Solved it with...

sudo rm /etc/dnsmasq.d/090_adblock.conf

Thanks for the quick help!

5

090_adblock.conf is not a Pi-hole file.
Pi-hole's own dnsmasq files follow the naming pattern 0x-pihole-something.conf.

If no other software (like RaspAP) depends on that file, it should be safe to remove it.

6

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