Detection of ARM device failed during upgrade of FTL version 4 to 5

Help Community Help
1

I decided to upgrade from 4 to version 5 executing pihole -up and it went fine except for the FTL upgrade.
Somehow it was not able to detect the pi as an ARM device and I solved it by manually changing the involved script file which is sourced:
/etc/.pihole/automated install/basic-install.sh

Following line in the script returned 2 lines where 1 line was intended:
lib=$(ldd /bin/ls | grep -E '^\s*/lib' | awk '{ print $1 }')
l/lib/libarmmem.so
/lib/ld-linux-armhf.so.3

I changed it into:
lib=$(ldd /bin/ls | grep -E '^\s*/lib/ld' | awk '{ print $1 }')

This change excludes the first returned result so that only the second line is returned.
After this installation went fine for FTL 5.0.

Right now I don't know if there is an error in the script or if the file
l/lib/libarmmem.so is not supposed to exist in the directory.

  1. Does anybody know if there is a bug or something wrong with my installation?

  2. After the upgrade, the pihole dashboard is not showing any stats anymore; this was working in pihole 4.3.7 Any idea to resolve this?
    Clearing cache, using different browser or running pihole -r does not fix it...

Although unsupported, I have successfully been running pihole on the pi for some years.
My setup:
Raspberry pi 3b+
XBIAN distribution with debian based kernel 5.4.40+
Webserver Apache 2.4.38 instead of the standard lighttpd

2

I dont run Pi-hole on Xbian anymore but seems your assumption is correct about returning only a single line:

xbian@avr ~ $ ldd /bin/ls | grep -E '^\s*/lib' | awk '{ print $1 }'
/lib/libarmmem.so
/lib/ld-linux-armhf.so.3

Also does below symlink exist on your XBian version ?

xbian@avr ~ $ readlink -f /lib/ld-linux-armhf.so.3
/lib/arm-linux-gnueabihf/ld-2.28.so

xbian@avr ~ $ dpkg -S /lib/arm-linux-gnueabihf/ld-2.28.so
libc6:armhf: /lib/arm-linux-gnueabihf/ld-2.28.so

Latest Xbian does have but older versions needed to symlink:

I believe this to be apache2 related like wrong config and/or PHP mods missing.
Search discourse here for apache2 related threads.

EDIT: Ps. you can default the web files with below if necessary:

3

Yes symlink does exist; I get same results returned on command line.

I am not so sure about this. The Dashboard page worked fine in 4.3.7 and I have not changed anything in the apache2 configuration. Only if FTL 5.0 needs extra requirements of the web server, then it would be plausible...

I also tried the repair setting the web interface to default, but no visual changes detected to what I had before.