FTL not running after Update

[Wytoo]

Expected Behaviour:

After Upgrading Pihole with sudo PIHOLE_SKIP_OS_CHECK=true pihole -r as the normal procedure fails since a couple of updates I realized that nothing's working anymore, from client side. on the Web Admin GUI I saw that the DNS is not running.

A
pi@raspberrypi:~ $ systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-09-06 13:30:59 CEST; 4min 25s ago
Docs: man:systemd-sysv-generator(8)
Process: 8477 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=1/FAILURE)

Sep 06 13:30:59 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Sep 06 13:30:59 raspberrypi pihole-FTL[8477]: Not running
Sep 06 13:30:59 raspberrypi su[8499]: Successful su for pihole by root
Sep 06 13:30:59 raspberrypi su[8499]: + ??? root:pihole
Sep 06 13:30:59 raspberrypi su[8499]: pam_unix(su:session): session opened for user pihole by (uid=0)
Sep 06 13:30:59 raspberrypi pihole-FTL[8477]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not foun
Sep 06 13:30:59 raspberrypi systemd[1]: pihole-FTL.service: Control process exited, code=exited status=1
Sep 06 13:30:59 raspberrypi systemd[1]: Failed to start LSB: pihole-FTL daemon.
Sep 06 13:30:59 raspberrypi systemd[1]: pihole-FTL.service: Unit entered failed state.
Sep 06 13:30:59 raspberrypi systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.

Tried to reconfigure it but with the same error.

Actual Behaviour:

After trying to reconfigure it now the webui is also missing.

Debug Token:

https://tricorder.pi-hole.net/E56oPXDB/

[NGr]

@Wytoo

PIHOLE_SKIP_OS_CHECK=true pihole -r

@Wytoo

Sep 06 13:30:59 raspberrypi pihole-FTL[8477]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not foun

Which OS and version are you running? Could be that it's out of support and not receiving updates.

[Wytoo]

pi@raspberrypi:~ $ pihole -v
Current Pi-hole version is v5.12
Current AdminLTE version is v5.14.2
pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.28' not found (required by pihole-FTL) pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.28' not found (required by pihole-FTL)
Invalid Option! Try 'pihole -v --help' for more information.
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="RaspbianForums - Raspbian"
BUG_REPORT_URL="RaspbianBugs - Raspbian"
pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch

[NGr]

@Wytoo

"Raspbian GNU/Linux 9 (stretch)"

There's your problem, see:

Bye Bye Debian Stretch :: Looking for testers

Bye Bye Debian Stretch :: Looking for testers We're going to upgrade Pi-hole's CI workflows used for generating the pre-compiled FTL binaries with the next release. We do this to install important upgrades in the build environment. We update not only libraries but also the entire compiler suite. By this update, the minimum required operating system is changed from Debian Stretch (9) to Buster (10). Debian 9 was initially released on 2017-06-17. It was superseded by Debian Buster on 2019-07-06…

[Wytoo]

Hi there

I've just updated the Raspberry Pi to 11.

pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

But even after pihole -r I still get an error with FTL.

pi@raspberrypi:~ $ systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
     Loaded: loaded (/etc/init.d/pihole-FTL; generated)
     Active: failed (Result: exit-code) since Tue 2022-09-06 17:17:23 CEST; 5s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 4679 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=2)
        CPU: 102ms

Sep 06 17:17:20 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Sep 06 17:17:20 raspberrypi pihole-FTL[4679]: Not running
Sep 06 17:17:20 raspberrypi su[4701]: (to pihole) root on none
Sep 06 17:17:20 raspberrypi su[4701]: pam_unix(su:session): session opened for user pihole(uid=999) by (uid=0)
Sep 06 17:17:23 raspberrypi systemd[1]: pihole-FTL.service: Control process exited, code=exited, status=2/INVALIDARG>
Sep 06 17:17:23 raspberrypi systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Sep 06 17:17:23 raspberrypi systemd[1]: Failed to start LSB: pihole-FTL daemon.

The WebInterface also says

There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47

[Wytoo]

Seems to have fixed the issue:

FTL failed to start due to failed to create listening socket for port 53: Address already in use

You will also need to prevent connmand from starting in the future, or you will have the same problem on the next reboot.

[Bucking_Horn]

You have another DNS server running on port 53, which prevents pihole-FTL from binding on that port.

*** [ DIAGNOSING ]: Pi-hole diagnosis messages
   count   last timestamp       type                  message                                                       blob1                 blob2                 blob3                 blob4                 blob5               
   ------  -------------------  --------------------  ------------------------------------------------------------  --------------------  --------------------  --------------------  --------------------  --------------------
   1       2022-09-06 17:28:37  DNSMASQ_CONFIG        failed to create listening socket for port 53: Die Adresse w                                                                                                              
                                                      ird bereits verwendet

*** [ DIAGNOSING ]: Ports in use
[✗] udp:127.0.0.1:53 is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)
[✗] tcp:127.0.0.1:53 is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)

You will need to stop and disable connmand.

Your upgrade to Bullseye also enabled predictable interface names.
You may want to run

pihole -r

and choose Reconfigure.