Expected Behaviour:
DNS service to be running.
Actual Behaviour:
Linux papayapi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
I've made a self-inflicted mess of my pihole setup.
I was on Debian 9 and the pihole upgrade aborted initially as Debian 9 is no longer supported, so I did something very unwise and forced the upgrade.
Pihole then failed to start because of a GLIBC_2.28 not found error, and I thought I could resolve that by upgrading to Debian 10 (buster).
After upgrading to Debian 10 sudo pihole status returns:
[✗] DNS service is NOT running
and sudo systemctl status pihole-FTL.service shows:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: failed (Result: exit-code) since Sat 2023-02-18 11:55:01 UTC; 10s ago
Docs: man:systemd-sysv-generator(8)
Process: 12136 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=1/FAILURE)
Feb 18 11:55:01 papayapi pihole-FTL[12136]: Not running
Feb 18 11:55:01 papayapi pihole-FTL[12136]: sh: 0: Can't open /opt/pihole/pihole-FTL-poststop.sh
Feb 18 11:55:01 papayapi pihole-FTL[12136]: sh: 0: Can't open /opt/pihole/pihole-FTL-prestart.sh
Feb 18 11:55:01 papayapi su[12146]: (to pihole) root on none
Feb 18 11:55:01 papayapi su[12146]: pam_unix(su:session): session opened for user pihole by (uid=0)
Feb 18 11:55:01 papayapi su[12146]: pam_unix(su:session): session closed for user pihole
Feb 18 11:55:01 papayapi pihole-FTL[12136]: sh: 0: Can't open /opt/pihole/pihole-FTL-poststop.sh
Feb 18 11:55:01 papayapi systemd[1]: pihole-FTL.service: Control process exited, code=exited, status=1/FAILURE
Feb 18 11:55:01 papayapi systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Feb 18 11:55:01 papayapi systemd[1]: Failed to start LSB: pihole-FTL daemon.
Contents of /opt/pihole are below:
-rwxr-xr-x 1 root root 1177 Oct 4 2021 wildcard_regex_converter.sh
-rwxr-xr-x 1 root root 37914 Feb 17 21:09 gravity.sh
-rwxr-xr-x 1 root root 28396 Feb 17 21:09 webpage.sh
-rwxr-xr-x 1 root root 4958 Feb 17 21:09 version.sh
-rwxr-xr-x 1 root root 4416 Feb 17 21:09 utils.sh
-rwxr-xr-x 1 root root 8291 Feb 17 21:09 update.sh
-rwxr-xr-x 1 root root 4270 Feb 17 21:09 updatecheck.sh
-rwxr-xr-x 1 root root 8827 Feb 17 21:09 query.sh
-rwxr-xr-x 1 root root 823 Feb 17 21:09 pihole-reenable.sh
-rwxr-xr-x 1 root root 2932 Feb 17 21:09 piholeLogFlush.sh
-rwxr-xr-x 1 root root 64895 Feb 17 21:09 piholeDebug.sh
-rwxr-xr-x 1 root root 8538 Feb 17 21:09 piholeCheckout.sh
-rwxr-xr-x 1 root root 1990 Feb 17 21:09 piholeARPTable.sh
-rwxr-xr-x 1 root root 10530 Feb 17 21:09 list.sh
-rwxr-xr-x 1 root root 20889 Feb 17 21:09 chronometer.sh
-rwxr-xr-x 1 root root 9097 Feb 17 21:09 uninstall.sh
drwxr-xr-x 2 root root 4096 Feb 17 21:09 .
-rwxr-xr-x 1 root root 1099 Feb 17 21:09 COL_TABLE
So the two pihole-FTL* files are definitely not there.
I'm really hoping someone can save me from a reinstall and advise on a fix?