Unable to complete update, cannot determine OS

The issue I am facing:

I am gettig this error message when I attempt to updte:

"Retrieval of supported OS list failed. dig failed with return code 10.
Unable to determine if the detected OS (Raspbian 9) is supported"

Details about my system:

Nothing special,been running pi-hole on this same Rasberry Pi for years.

What I have changed since installing Pi-hole:

Tried to update via pihole -up and it failed with the error above. Following direction from another topic on here I updatd my resolv.conf to 9.9.9.9 and then ran the update again. Still failed. Then ran the command suggested in the error:

sudo PIHOLE_SKIP_OS_CHECK=true pihole -r

This I chose repair and it ran to completion Going to the admin page I get an error message that DNS service is not running.

Help!

I see FTL is not running, trying to restart just fails. Tried to restart DNS, fails. Output from journalctl below. I see no obvious issue? Other than it won't start.

journalctl -u pihole-FTL --no-pager
-- Logs begin at Thu 2016-11-03 12:16:43 CDT, end at Mon 2022-11-28 17:50:22 CST. --
Nov 28 17:46:04 PiHole systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 28 17:46:04 PiHole pihole-FTL[532]: Not running
Nov 28 17:46:04 PiHole su[578]: Successful su for pihole by root
Nov 28 17:46:04 PiHole su[578]: + ??? root:pihole
Nov 28 17:46:04 PiHole su[578]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 28 17:46:04 PiHole pihole-FTL[532]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.28' not found (required by /usr/bin/pihole-FTL) Nov 28 17:46:04 PiHole systemd[1]: pihole-FTL.service: Control process exited, code=exited status=1 Nov 28 17:46:04 PiHole systemd[1]: Failed to start LSB: pihole-FTL daemon. Nov 28 17:46:04 PiHole systemd[1]: pihole-FTL.service: Unit entered failed state. Nov 28 17:46:04 PiHole systemd[1]: pihole-FTL.service: Failed with result 'exit-code'. Nov 28 17:50:00 PiHole systemd[1]: Starting LSB: pihole-FTL daemon... Nov 28 17:50:00 PiHole pihole-FTL[782]: Not running Nov 28 17:50:00 PiHole su[798]: Successful su for pihole by root Nov 28 17:50:00 PiHole su[798]: + ??? root:pihole Nov 28 17:50:00 PiHole su[798]: pam_unix(su:session): session opened for user pihole by (uid=0) Nov 28 17:50:00 PiHole pihole-FTL[782]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version GLIBC_2.28' not found (required by /usr/bin/pihole-FTL)
Nov 28 17:50:00 PiHole systemd[1]: pihole-FTL.service: Control process exited, code=exited status=1
Nov 28 17:50:00 PiHole systemd[1]: Failed to start LSB: pihole-FTL daemon.
Nov 28 17:50:00 PiHole systemd[1]: pihole-FTL.service: Unit entered failed state.
Nov 28 17:50:00 PiHole systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Nov 28 17:50:22 PiHole systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 28 17:50:22 PiHole pihole-FTL[848]: Not running
Nov 28 17:50:22 PiHole su[864]: Successful su for pihole by root
Nov 28 17:50:22 PiHole su[864]: + ??? root:pihole
Nov 28 17:50:22 PiHole su[864]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 28 17:50:22 PiHole pihole-FTL[848]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by /usr/bin/pihole-FTL)
Nov 28 17:50:22 PiHole systemd[1]: pihole-FTL.service: Control process exited, code=exited status=1
Nov 28 17:50:22 PiHole systemd[1]: Failed to start LSB: pihole-FTL daemon.
Nov 28 17:50:22 PiHole systemd[1]: pihole-FTL.service: Unit entered failed state.
Nov 28 17:50:22 PiHole systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.

Now seeing this:
systemctl status pihole-FTL.service

  • pihole-FTL.service - LSB: pihole-FTL daemon
    Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
    Active: failed (Result: exit-code) since Mon 2022-11-28 18:04:46 CST; 13s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 974 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=1/FAILURE)

Nov 28 18:04:46 PiHole systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 28 18:04:46 PiHole pihole-FTL[974]: Not running
Nov 28 18:04:46 PiHole su[990]: Successful su for pihole by root
Nov 28 18:04:46 PiHole su[990]: + ??? root:pihole
Nov 28 18:04:46 PiHole su[990]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 28 18:04:46 PiHole pihole-FTL[974]: /usr/bin/pihole-FTL: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.28' not found (required by /usr/bin/pihole-FTL)
Nov 28 18:04:46 PiHole systemd[1]: pihole-FTL.service: Control process exited, code=exited status=1
Nov 28 18:04:46 PiHole systemd[1]: Failed to start LSB: pihole-FTL daemon.
Nov 28 18:04:46 PiHole systemd[1]: pihole-FTL.service: Unit entered failed state.
Nov 28 18:04:46 PiHole systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.

FTL will not start on Raspbian 9. We noted in the release notes, and a few other places, that Raspbian 9 is no longer supported and can not be used.

There is no GLIBC_2.28 available for Raspbian 9.
Unfortunately, there is no way to install this library on older systems.

There were a few announcements about the end of support for Debian/Raspbian 9 (Stretch):

I unforunately missed that. Just in the process of upgrading to Pi OS and will give the update another try.

After upgrading the OS all seems to be working again. Thanks for the help everyone!

Two comments:

  1. Raspbian 9 (Stretch) is not supported, and there is a hard failure to load Pi-hole due to missing dependencies.

  2. Your nameserver (defined in /etc/resolv.conf) is unable to connect to the internet. What is the output of the following:

cat /etc/resolv.conf

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