Pihole FTP offline after power outage

Help
1

Expected Behaviour:

FTL Offline... My breaker tripped and then Pihole stopped working. I logged onto the admin browser from my laptop and found that the FTL is offline.
A few steps I took in no particular order. Uninstalled pihole, sudo apt update, sudo apt upgrade, reinstall pihole, pihole -r (repair and reconfigure), reboot, reinstall git + curl, and the FTL is still offline. dnsmasq, pihole-FTL, and lighttpd seem to fail to run.

Actual Behaviour:

pihole status
DNS Service is running
Pi-hole blocking is Enabled
FTL Offline

sudo service pihole-FTL start
systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated)
   Active: active (exited) since Fri 2020-09-18 15:31:10 PDT; 24min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2987 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SU

Sep 18 15:31:10 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Sep 18 15:31:10 raspberrypi pihole-FTL[2987]: Not running
Sep 18 15:31:10 raspberrypi su[3005]: (to pihole) root on none
Sep 18 15:31:10 raspberrypi su[3005]: pam_unix(su:session): session opened for u
Sep 18 15:31:10 raspberrypi pihole-FTL[2987]: dnsmasq: failed to create listenin
Sep 18 15:31:10 raspberrypi su[3005]: pam_unix(su:session): session closed for u
Sep 18 15:31:10 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.

pi@ra

systemctl status lighttpd
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset:
   Active: active (running) since Fri 2020-09-18 15:31:02 PDT; 27min ago
 Main PID: 2724 (lighttpd)
    Tasks: 6 (limit: 3862)
   CGroup: /system.slice/lighttpd.service
           ├─2724 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
           ├─2736 /usr/bin/php-cgi
           ├─2746 /usr/bin/php-cgi
           ├─2748 /usr/bin/php-cgi
           ├─2750 /usr/bin/php-cgi
           └─2752 /usr/bin/php-cgi

Sep 18 15:31:52 raspberrypi sudo[3855]: pam_unix(sudo:session): session closed f
Sep 18 15:31:53 raspberrypi sudo[3870]: www-data : TTY=unknown ; PWD=/var/www/ht
Sep 18 15:31:53 raspberrypi sudo[3870]: pam_unix(sudo:session): session opened f
Sep 18 15:31:53 raspberrypi sudo[3870]: pam_unix(sudo:session): session closed f
Sep 18 15:31:53 raspberrypi sudo[3902]: www-data : TTY=unknown ; PWD=/var/www/ht
Sep 18 15:31:53 raspberrypi sudo[3902]: pam_unix(sudo:session): session opened f
Sep 18 15:31:53 raspberrypi sudo[3902]: pam_unix(sudo:session): session closed f
Sep 18 15:37:00 raspberrypi sudo[5338]: www-data : TTY=unknown ; PWD=/var/www/ht
Sep 18 15:37:00 raspberrypi sudo[5338]: pam_unix(sudo:session): session opened f
Sep 18 15:37:00 raspberrypi sudo[5338]: pam_unix(sudo:session): session closed f

systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
   Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset:
   Active: inactive (dead)

Debug Token:

https://tricorder.pi-hole.net/1rv68w8gnp

2
3

I ended up reformatting my OS and will be installing Pihole again. You can delete this post.

6

I know you already are operational again, but maybe users with similar messages can still benefit.

Look at your error messages:

This would have been your issue.

The error message is incomplete, but likely, another DNS server like BIND or unbound did compete with pihole-FTL for port 53.
Resolving that conflict quite probably would have fixed it without a complete reinstall.

9

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