Thank you for the help narrowing this issue down.
Running dpkg, whereis, & stat all resulted in 'no results'. I ran apt-get for the libc6 package and it reported I already had the latest version installed.
I found another command (ldd) that pointed toward a similarly named library ld-linux.so.2 located in /lib/. Could this be what we're looking for?
Dont need to lookup dependencies for the "cat" command.
Its the library "ld-linux-x86-64.so.2", the 64 bits version, what the pi-hole-FTL binary wants.
Am not sure if you can run binaries intended for a 64 bit system on a 32 bit (i386) distro but dont think so.
What distro did you install and did you add that foreign architecture "amd64" and what for ?
Dont know if a 32 bit pi-hole-FTL version exists.
If its a fresh install, you could try re-install on the 64 bit version of that distro.
Maybe the @developers can shed some light ?
ok, thanks. Didn't know pi-hole was 64-bit only but more importantly I didn't know I had installed a 32-bit distro. I'll go back and get the right version of Stretch and try this all again.
Am not sure how that 64 bit binary got onto a 32 bit distro but maybe that foreign architecture "amd64" fooled the Pi-hole installer into believing it is a 64 bit system ??? Maybe it suffices to just remove that architecture and try re-install Pi-hole.
You can remove that "amd64" architecture with:
sudo dpkg --remove-architecture amd64
Or add it again with:
sudo dpkg --add-architecture amd64
I didnt say that and @Mcat12 just confirmed that a 32 bit version exists also.
Forget removing or adding amd64 architecture, it seems the installer decides on what system architecture is detected and doesnt look at distro architecture.
From the install script:
# Store architecture in a variable
machine=$(uname -m)
.
.
elif [[ "${machine}" == "x86_64" ]]; then
# 64bit
echo -e "${OVER} ${TICK} Detected x86_64 architecture"
# set the binary to be used
binary="pihole-FTL-linux-x86_64"
So the only fix left is try install the 64 bit distro version ... I think
The installer script messes things up on my system (32bit). The script assumes a lot, while it simply should ask the user what they want. It currently blindly overwrites pihole-FTL with the wrong version.
I strongly disagree. Many users use Pi-hole as their first Raspberry Pi, sometimes even as their first Linux experiment. Even if we'd ask them which architecture they are running on, that might already be too much. The Pi-hole installer is constructed to make the installation as simple and straightforward as possible.
Please be more specific. Does that mean you are running a 32bit on 64bit capable hardware? If so, why? If not, what is the problem you are seeing?