@MartB - I believe /etc/pihole was root:root under 2.11.x as well as the files within it.
Search Criteria
Package Details: pi-hole-ftl 6.1-1
Package Actions
| 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: | 59 |
| Popularity: | 0.86 |
| First Submitted: | 2017-05-07 15:23 (UTC) |
| Last Updated: | 2025-03-30 17:00 (UTC) |
Dependencies (6)
- gmp (gmp-hgAUR)
- mbedtls (mbedtls-gitAUR, mbedtls-dtlsAUR)
- nettle (nettle-gitAUR)
- pi-hole-webAUR
- cmake (cmake-gitAUR, cmake3AUR) (make)
- xxd (vim-minimal-gitAUR, gvim-gitAUR, vim-cli-gitAUR, gvim-wayland-lilydjwg-gitAUR, gvim-gtk2AUR, gvim, tinyxxd, vim) (make)
Required by (66)
- adhocspot-script-git (requires dnsmasq)
- airgeddon (requires dnsmasq) (optional)
- anti-ad-dnsmasq-git (requires dnsmasq)
- appgate-sdp (requires dnsmasq) (optional)
- appgate-sdp-headless (requires dnsmasq) (optional)
- archpxe (requires dnsmasq)
- berate_ap-git (requires dnsmasq)
- blueman-git (requires dnsmasq) (optional)
- corplink-bin (requires dnsmasq)
- create_ap (requires dnsmasq)
- create_ap-git (requires dnsmasq)
- cuttlefish-base-git (requires dnsmasq)
- dns-zone-blacklist-git (requires dnsmasq) (optional)
- dnsmasq-china-list-git (requires dnsmasq)
- dnsmasq-openrc (requires dnsmasq)
- docker-dnsmasq (requires dnsmasq)
- docker-machine-driver-kvm2 (requires dnsmasq)
- easywifi-git (requires dnsmasq) (optional)
- ethoscope-device (requires dnsmasq)
- ethoscope-node (requires dnsmasq)
- Show 46 more...
Sources (5)
graysky commented on 2017-12-11 20:33 (UTC)
MartB commented on 2017-12-11 20:19 (UTC) (edited on 2017-12-11 20:19 (UTC) by MartB)
There is an issue with this package the /etc/pihole directory is under root:root it should be under pihole:pihole for the database file to work correctly.
graysky commented on 2017-12-08 12:01 (UTC)
Not out-of-date: 2.12 is the current upstream stable.
graysky commented on 2017-09-30 21:25 (UTC) (edited on 2017-10-01 14:13 (UTC) by graysky)
I found the problem. It was with writing to the log ftl uses for the statistics. Long story short, https://github.com/graysky2/lxc-snapshots/commit/295fa23be84600860c4ef6877084ba73f2e1935d
graysky commented on 2017-09-30 20:32 (UTC)
OK... I have confirmed the problem is not with the package but with something in the container. Sorry for all the noise.
graysky commented on 2017-09-30 19:42 (UTC)
I am running pihole in an linux container... that might be the issue. I need to dig deeper. Version 2.10-1 is fine though.
graysky commented on 2017-09-30 19:41 (UTC)
Yes, it does:
% status pi-hole-ftl
● pi-hole-ftl.service - Pi-hole FTL engine
Loaded: loaded (/usr/lib/systemd/system/pi-hole-ftl.service; disabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Sat 2017-09-30 15:41:05 EDT; 1s ago
Process: 139 ExecStart=/usr/bin/pihole-FTL no-daemon (code=dumped, signal=ABRT)
Main PID: 139 (code=dumped, signal=ABRT)
Sep 30 15:41:04 rs-pihole systemd[1]: pi-hole-ftl.service: Unit entered failed state.
Sep 30 15:41:04 rs-pihole systemd[1]: pi-hole-ftl.service: Failed with result 'core-dump'.
Sep 30 15:41:05 rs-pihole systemd[1]: pi-hole-ftl.service: Service hold-off time over, scheduling restart.
Sep 30 15:41:05 rs-pihole systemd[1]: Stopped Pi-hole FTL engine.
Sep 30 15:41:05 rs-pihole systemd[1]: pi-hole-ftl.service: Start request repeated too quickly.
Sep 30 15:41:05 rs-pihole systemd[1]: Failed to start Pi-hole FTL engine.
Sep 30 15:41:05 rs-pihole systemd[1]: pi-hole-ftl.service: Unit entered failed state.
Sep 30 15:41:05 rs-pihole systemd[1]: pi-hole-ftl.service: Failed with result 'core-dump'.
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.