Pi-Hole and pihole-FTL error after Debian Buster install

Pi-Hole and pihole-FTL error after Debian Buster install

I feel these kinds of posts go along with the VPS theme because I think the Raspberry Pi goes along well with the spirit of low end hardware.

I have a Raspberry Pi A+ (2016) with 512mb of RAM and a single BCM2835 CPU core at 700 Mhz. There are 4 USB ports, the Ethernet is 10/100 and it retails as of right now for about $23 USD on Amazon. I’ve had this RPI for about a year and a half. It never did nothing really other than idle. For $35 USD on Amazon, you can get the Pi 3 A+ which is a quad core 1.4 Ghz CPU with 512mb RAM. For $55 USD on Amazon, you can get the Pi 3B+ which has 1 GB of RAM. Both 3 series have 10/100Mbps Ethernet and also Bluetooth / WiFi while the A+ model I have does not have these features.

I will say even though I don’t have one but I can see the Pi 3A+ being the best in respect to having a RPI just assigned to doing DNS tasks in your home or small business network.

Well to install Pi-Hole you will need a supported OS like the various Raspbian distributions which are built off of the Debian Linux operating system. Next you would run curl -sSL https://install.pi-hole.net | bash to start  the installer. Depending on your hardware it can take awhile but that mainly just applies to the A+ users.

Ok so you have the installation done which doesn’t really need to be discussed other than hitting Enter a bunch of times. Your normal urge is to do some additional configuration of this hardware which may involve installing some third party software or the simple apt updates. You login to Pi-Hole and bam, you get an error that pihole-FTL isn’t running which breaks pihole from doing it’s job.

root@pihole:~# /etc/init.d/pihole-FTL
Usage: /etc/init.d/pihole-FTL {start|stop|restart|reload|status}
root@pihole:~# /etc/init.d/pihole-FTL status
[ ] pihole-FTL is not running
root@pihole:~# /etc/init.d/pihole-FTL start
Not running

/usr/bin/pihole-FTL: error while loading shared libraries: pt: cannot open shared object file: No such file or directory

Now your DNS is broken.

In the bottom right hand corner, a link to pihole-FTL update available might be flashing. You’d need to click that and find what architecture applies for you. For me being ARMv6 as confirmed by /proc/cpuinfo , I cd /usr/bin and ran this command wget -O pihole-FTL1 https://github.com/pi-hole/FTL/releases/download/v4.3.1/pihole-FTL-arm-linux-gnueabi to download a new copy of pihole-FTL as pihole-FTL1

You will need to chmod +x pihole-FTL1 and run it via ./pihole-FTL1

If your architecture is wrong, you’ll get an error and will need to repeat the steps above but with a new URL. It’ll tell you if it is running. Next we need to stop pihole-FTL1 by running killall pihole-FTL1 which will stop it. We delete pihole-FTL via rm -rf pihole-FTL then rename pihole-FTL1 to pihole-FTL via mv pihole-FTL1 pihole-FTL to allow the /etc/init.d/pihole-FTL script to work.

Restart it via /etc/init.d/pihole-FTL restart and it should just work.

Update: no idea why but just eth0 completely disappeared. I’ve had more problems running Pi-Hole on Debian 10/Buster than on Debian 9/Stretch so I’m reverting back to Stretch in the meantime.

Comments are closed.