Arch Linux User Repository

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.

First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

@max.bra - I downgraded to 5.3.1-3 when I found my web interface on 5.3.1-4 to be in a busy state. None of the menu items works and the banners across the top were displaying the animation for getting data. Pihole continued to process queries.

@compiler1413 thanks for the heads up.
hopefully pihole 6 will be released soon and all of this problems will fade away.

Just had hell of a time getting updated server to work properly. Arch Linux ARM, 5.11.2-1-ARCH #1 SMP PREEMPT Sun Feb 28 22:03:25 UTC 2021 armv7l

PHP8 is apparently not supported with the latest pi-hole-server so I downgraded to php7. This introduces an issue with SQLITE3.

lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:PHP Warning:  Use of undefined constant SQLITE3_OPEN_READONLY - assumed 'SQLITE3_OPEN_READONLY' (this will throw an Error in a future version of PHP) in /srv/http/pihole/admin/scripts/pi-hole/php/database.php on line 61
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:PHP Fatal error:  Uncaught Error: Class 'SQLite3' not found in /srv/http/pihole/admin/scripts/pi-hole/php/database.php:42
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:Stack trace:
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:#0 /srv/http/pihole/admin/scripts/pi-hole/php/database.php(65): SQLite3_connect_try()
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:#1 /srv/http/pihole/admin/api_db.php(56): SQLite3_connect()
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:#2 {main}
lighttpd-angel[263]:mod_fastcgi.c.487) FastCGI-stderr:  thrown in /srv/http/pihole/admin/scripts/pi-hole/php/database.php on line 42

So I installed:

pacman -S php7 php7-cgi php7-sqlite php7-fpm

Recompiled pi-hole-server and pi-hole-ftl:

yay -S --aur pi-hole-server pi-hole-ftl

Made manual symlinks for php7 stuff:

ln -s /usr/bin/php-cgi7 /usr/bin/php-cgi
ln -s /usr/bin/php-config7 /usr/bin/php-config
ln -s /usr/bin/php7 /usr/bin/php
ln -s /usr/bin/phpize7 /usr/bin/phpize
ln -s /usr/bin/phar7 /usr/bin/phar
ln -s /usr/bin/php-fpm7 /usr/bin/php-fpm
ln -s /etc/php7 /etc/php
ln -s /usr/lib/php7 /usr/lib/php

Edited /etc/php/php.ini

sed -i "s|\;extension=pdo_sqlite|extension=pdo_sqlite|g;s|\;extension=sqlite3|extension=sqlite3|g;s|\;extension=sockets|extension=sockets|g" /etc/php/php.ini

Set immutable on php.ini because for some reason, after rebooting the settings were reverted

chattr +i /etc/php/php.ini

Restart lighttpd

sudo systemctl restart lighttpd

Everything is working as before now!

local/php7 7.4.20-1
local/php7-cgi 7.4.20-1
local/php7-fpm 7.4.20-1
local/php7-sqlite 7.4.20-1
local/pi-hole-ftl 5.8.1-1
local/pi-hole-server 5.3.1-3

And maybe I made an error or did something unnecessary here so please point that out for me if I did. Thanks!

@max.bra, ok, thanks for the fix. I just thought that maybe other excerpts could need rebase reviewing, not only this special case. Maybe not.

@pepper_chico oh! now i get it.
do you mean that our mimic_basic-install.sh functions are not the same of upstream ones?
ok, it's true. thanks for reporting.
small oversight sorry, but this is not a job for anyone here. if you find a problem, report it and it will be fixed, if possible, ASAP.

@pepper_chico i really don't understand

It seems forked sources here may need review & update. For example, I'm facing an issue that has been long fixed uptream, and should have been fixed here too, but isn't, because forked sources are not tracking upstream. See this fix present on 5.1.2 for example:

https://github.com/pi-hole/pi-hole/commit/643d2c0f3ea7871b64f9eaa2c9a5a2060d9ad14e

Nevermind, deleting /etc/pihole/pihole-FTL.db and restarting the service fixed it.

My long term data is not populating. Noticing some errors in the service when I run sudo systemctl status pihole-FTL.service:

● pihole-FTL.service - Pi-hole FTLDNS engine
     Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2021-04-16 11:13:00 EDT; 3 weeks 1 days ago
    Process: 352 ExecStartPre=/bin/chown -R pihole:pihole /etc/pihole (code=exited, status=0/SUCCESS)
    Process: 358 ExecStartPre=/bin/chown root:root /etc/pihole/logrotate (code=exited, status=0/SUCCESS)
   Main PID: 359 (pihole-FTL)
      Tasks: 7 (limit: 4915)
        CPU: 213ms
     CGroup: /system.slice/pihole-FTL.service
             └─359 /usr/bin/pihole-FTL no-daemon

Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.431 359M] Finished config file parsing
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.516 359M] Database version is 8
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Updating long-term database to version 9
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: table aliasclient already exists in "CREATE TABLE aliasclient (id INTEGER PRIMARY KEY NOT NULL, name TEXT NOT NULL, comment TEXT);" (1)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] ERROR: SQL query "CREATE TABLE aliasclient (id INTEGER PRIMARY KEY NOT NULL, name TEXT NOT NULL, comment TEXT);" failed: SQL logic error
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] ERROR: create_aliasclients_table() failed!
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Aliasclients table not initialized, database not available
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: API call with invalid database connection pointer (21)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] SQLite3 message: misuse at line 165242 of [5d4c65779d] (21)
Apr 16 11:13:00 alarmpi pihole-FTL[359]: [2021-04-16 11:13:00.517 359M] Error while trying to clos

I know this is getting off track, but I've since enabled IPv6 (within the last hour): All's well on the LAN side, but my ISP does not support IPv6, so I'm limited to to IP4 on the WAN, which is why I see the IPv6 connection errors, I suppose.