| Git Clone URL: | https://aur.archlinux.org/pi-hole-ftl.git (read-only, click to copy) |
|---|---|
| Package Base: | pi-hole-ftl |
| Description: | The Pi-hole FTL engine |
| Upstream URL: | https://github.com/pi-hole/FTL |
| Licenses: | EUPL-1.2 |
| Conflicts: | dnsmasq |
| Provides: | dnsmasq |
| Submitter: | max.bra |
| Maintainer: | max.bra (graysky) |
| Last Packager: | max.bra |
| Votes: | 56 |
| Popularity: | 1.38 |
| First Submitted: | 2017-05-07 15:23 (UTC) |
| Last Updated: | 2024-08-10 09:53 (UTC) |
@max.bra - Upon updating to php 7.4.0-2 I no longer see an "Active/Green Circle" status in the upper left of the web GUI. I see an "Unknown/Orange Circle" although pi-hole seems to behave normally. Using nginx. Any thoughts are welcomed.
EDIT: downgrading to php-fpm-7.3.12-1 and php-sqlite-7.3.12-1 fixed the behavior.
hi HC6505, no that line is not working at all. on first install that line is executed before systemd user creation hook and user pihole is not yet existent.
theoretically the db should be created (if missing) by pihole-FTL on starting and since it is running as user pihole should create it with that owner.
pi-hole-ftl 4.3.1-5
In the build file pi-hole-ftl.install
post_install() {
Shouldn't the last line not be uncommented? After doing it the /etc/pihole/pihole-FTL.db is now being populated
Since switching to pihole user for pihole-FTL - long term data is not retained on my machine.
sir_randomuser said: For some reason account http has expired, which was the root cause. Seems to be due to a recent systemd change: https://bugs.archlinux.org/task/63704
Checking /etc/shadow, the user http had a trailing 1:
$ sudo cat /etc/shadow | grep http
http:!!:18174::::::1:
Removing the expiration date has resolved it:
$ sudo chage --expiredate -1 http
UPD 2: I was able to resolve the problem. For some reason account http has expired, which was the root cause. Seems to be due to a recent systemd change: https://bugs.archlinux.org/task/63704
Oct 11 16:29:29 asgard systemd[1]: Started Lighttpd Web Server.
Oct 11 16:29:29 asgard lighttpd-angel[7108]: 2019-10-11 16:29:29: (server.c.1521) server started (lighttpd/1.4.54)
Oct 11 16:29:32 asgard sudo[7125]: pam_unix(sudo:account): account http has expired (account expired)
Oct 11 16:29:32 asgard sudo[7125]: http : Account expired or PAM config lacks an "account" section for sudo, contact your system administrator ; TTY=unknown ; PWD=/s>
Checking /etc/shadow, the user http had a trailing 1:
$ sudo cat /etc/shadow | grep http
http:!!:18174::::::1:
Removing the expiration date has resolved it:
$ sudo chage --expiredate -1 http
+----------------------------------------------------------+
UPD: I've also tried to download snapshots and build via makepkg instead of using YAY.. alas, did not make any difference.
Since switching to pihole user for pihole-FTL - long term data is not retained on my machine.
I've tried to re-install both the pi-hole-server and pi-hole-ftl packages - deleting the following before re-installing:
/etc/pihole/
/run/pihole
/run/log/pihole/
/run/log/pihole-ftl/
/etc/dnsmasq.d/01-pihole*
Web interface shows "Status: Unknown", however pihole -c shows status as "Active". Not sure what exactly is the root cause. Any suggestions as to what else I should check?
Hostname: asgard (Arch )
Uptime: 00:16:23
Task Load: 0.25 0.28 0.35 (Active: 2 of 99 tasks)
CPU usage: 1% (4x 1.4 GHz @ 322k)
RAM usage: 9% (Used: 628 MB of 7 GB)
HDD usage: 22% (Used: 10 GB of 48 GB)
LAN addr: xxx.xxx.x.xxx (Gateway: xxx.xxx.x.x)
Pi-hole: Active (Blocking: 113432 sites)
Ads Today: 11% (Total: 19 of 179)
Local Qrys: 28% (2 DNS servers)
@max.bra asked at https://archlinuxarm.org/forum/viewtopic.php?f=9&t=14035
so, i.MX6... at the moment i don't have any other clue. Maybe you can ask to the archarm devs about ambient capabilities state?
@max.bra I run pi-hole on ARM with https://archlinuxarm.org/, I think their kernel is recent enough to support this, but I dunno whether it's enabled. I'm not willing keep compiling kernel for ARM myself for this, so, if there isn't another way, I'll fix running as root :/
Specifically it's a Cubox-i, so kernel is linux-imx6 3.14.79-3: https://archlinuxarm.org/packages/armv7h/linux-imx6
@thepasto last patching fix compilation issue after glibc/linux-api-header last update.
pepper_chico's problem seems to be related to his kernel config.
@max.bra Many thanks - fix successful
Pinned Comments
max.bra commented on 2018-02-09 16:46 (UTC) (edited on 2019-10-18 23:13 (UTC) by max.bra)
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.