Fresh install, reinstalled also. On armel/kirkwood Debian.
Most parts of webif work correctly, dns blocking works fine, graphs/stats, etc all good.
Broken:
webif for gravity update (shows no output)
webif for diagnostics (shows no output)
odd specific parts... e.g. Temperature choice (C, K, F) shows dropdown menu, can choose F or K, but webif doesn't change it. I actually changed it via CLI to F, but webif shows C still.
Clues:
php version is 8.2.26; on another similar device (backup/failover pihole) 8.2.24 is still there, and works fine... not sure if there is a problem with 8.2.26, but couldn't see anything in change log that would point to that
in /var/log/lighttpd/error-pihole.log : 2024-12-08 09:36:23: (mod_fastcgi.c.449) FastCGI-stderr:PHP Warning: Executing sudo pihole -a -c failed. in /var/www/html/admin/scripts/pi-hole/php/func.php on line 173
I was able to use the command line just fine to change C to F, and also (obviously) to run debug and upload...
Is there some sort of cache for php/fastcgi that I can delete?
I suspect that it could be some odd permissions error, but I don't know where to look exactly...
2024-12-08 09:32:41: (gw_backend.c.1583) invalid "bin-path" => "/usr/bin/php-cgi" (check that file exists, is regular file, and is executable by lighttpd)
Can you check sudo which php-cgi and show the contents of the lighttpd configuration for fastcgi sudo can /etc/lighttpd/conf-available/10-fastcgi.conf please? I see an additional 99-unconfigured.conf file in that same conf-available director that does not look familiar to me.
root@PiHole1-B388:/etc# ls -la /run/lighttpd
total 0
drwxr-x--- 2 www-data www-data 60 Dec 8 16:41 .
drwxr-xr-x 17 root root 760 Dec 31 1969 ..
srwxr-xr-x 1 www-data www-data 0 Dec 8 16:41 pihole-php-fastcgi.socket-0
With a freshly formatted SSD, using a fresh tarball of the rootfs that I've used from the last few years (Debian Bookworm armel), I reproduced the exact same error.
For now, I'm leaving it as is. All the CLI operations seem to work just fine, but something between the webif and fastcgi seems to be borked.
If Pihole 6 does come out, any php considerations would probably be moot... I've searched for some mention of "armel", "debian", "php8.2.26-1", "pihole", but I've not come up with anything.
At this point I'll probably also try to debootstrap a Debian "Trixy" image and give that a go. Not sure what else to try...
$ update-alternatives --display php-cgi
php-cgi - auto mode
link best version is /usr/bin/php-cgi7.3
link currently points to /usr/bin/php-cgi7.3
link php-cgi is /usr/bin/php-cgi
slave php-cgi.1.gz is /usr/share/man/man1/php-cgi.1.gz
/usr/bin/php-cgi7.3 - priority 73
slave php-cgi.1.gz: /usr/share/man/man1/php-cgi7.3.1.gz
You can set/configure alternatives with below if there are any:
It looks like 7.3 is from Bullseye, not available in Bookworm. Also, the "sister" pihole server is running php8.2.24, and it works correctly. I don't want to get into the whole thing of apt-pinning or and alternate source... gonna let this as is for now. Thanks.
That's a good idea, but apparmor/SE are not applied/present on these boxes.
They are running armel (Kirkwood SoC) Debian - 32 bit ARM. This SoC was popular 15 years ago - draws only about 3-5 watts, so they are great for embedded applications. Downside is that they are no longer made - fewer and fewer people use them, so they not as well supported/tested as they used to be.
Probably time for me to get a 5-10$ raspberry pi 64bit look-alike and try out one of those. More modern means often better supported/tested.
After you've installed v5 and before switching to the v6 development branch (checkout), dont forget to disable and stop lighttpd first with below if you dont use it for anything else:
sudo systemctl disable --now lighttpd.service
If not, lighttpd will keep on running after the switch and the pihole-FTL daemon will be configured to listen on port 8080 for HTTP instead of 80 where lighttpd will still be listening!
Am not sure if pihole checkout development is sufficient to switch.
But am sure @DanSchaper can tell
EDIT: Oh blast, after typing above, I realised there is no armel pre-compiled binary available for your Pogo:
