OK glad it is not just me. I am running the latest version of all three packages and still cannot update in the web GUI.
Search Criteria
Package Details: pi-hole-ftl 6.0.4-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: | 2.10 |
First Submitted: | 2017-05-07 15:23 (UTC) |
Last Updated: | 2025-03-06 09:44 (UTC) |
Dependencies (6)
- gmp (gmp-hgAUR)
- mbedtls (mbedtls-gitAUR, mbedtls-dtlsAUR)
- nettle (nettle-gitAUR)
- pi-hole-webAUR
- cmake (cmake-gitAUR) (make)
- xxd (vim-minimal-gitAUR, gvim-gitAUR, vim-cli-gitAUR, gvim-wayland-lilydjwg-gitAUR, gvim-gtk2AUR, gvim, tinyxxd, vim) (make)
Required by (65)
- 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 45 more...
Sources (5)
graysky commented on 2025-03-06 13:46 (UTC)
max.bra commented on 2025-03-06 10:03 (UTC)
@graysky hi graysky, sorry for late reply.
it took me a while to update and respond (excluding a few days away from home) because the web-based gravity update no longer works for me. I press the “update” button and the blue run notification band appears for a moment (literally) and everything then goes back to the way it was before the button was pressed. terminal 'pihole -g' execute normally.
I am 99.99% certain that it was working in previous versions: it is one of the things I do to check the “proper functionality” of the web interface along with the creation and removal of blacklisted and whitelisted entries.
The big part of the problem is that I can't see anything in the logs even running pihole-FTL either as root or as a pihole user with debug parameter d: of the web part, practically nothing appears except the port opening notification on startup...
With 6.0.5 and related “children,” does this happen to you too?
graysky commented on 2025-03-01 11:30 (UTC)
@max.bra - if you try to manually update the block list, system>tools>update gravity
do you get this output and failure to update too?
2025-03-01 06:28:35.494 EST [185M] INFO: ########## FTL started on privileged! ##########
2025-03-01 06:28:35.494 EST [185M] INFO: FTL branch: master
2025-03-01 06:28:35.494 EST [185M] INFO: FTL version: v6.0.2
2025-03-01 06:28:35.494 EST [185M] INFO: FTL commit: builtfromreleasetarball
2025-03-01 06:28:35.494 EST [185M] INFO: FTL date: 2025-02-22
2025-03-01 06:28:35.494 EST [185M] INFO: FTL user: pihole
2025-03-01 06:28:35.494 EST [185M] INFO: Compiled for currentarch using currentcompiler
2025-03-01 06:28:35.495 EST [185M] INFO: Wrote config file:
2025-03-01 06:28:35.495 EST [185M] INFO: - 152 total entries
2025-03-01 06:28:35.495 EST [185M] INFO: - 136 entries are default
2025-03-01 06:28:35.495 EST [185M] INFO: - 16 entries are modified
2025-03-01 06:28:35.495 EST [185M] INFO: - 0 entries are forced through environment
2025-03-01 06:28:35.495 EST [185M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-03-01 06:28:35.495 EST [185M] WARNING: Unable to read PID from file: No such file or directory
2025-03-01 06:28:35.495 EST [185M] INFO: PID file does not exist or not readable
2025-03-01 06:28:35.495 EST [185M] INFO: No other running FTL process found.
2025-03-01 06:28:35.496 EST [185M] WARNING: Unable to write PID to file: No such file or directory
2025-03-01 06:28:35.496 EST [185M] INFO: PID of FTL process: 185
max.bra commented on 2025-02-25 16:39 (UTC)
@mrdotx yes it is. thanks for reporting.
mrdotx commented on 2025-02-25 06:31 (UTC)
The pihole-FTL.service sometimes gives a warning:
systemd[1]: /usr/lib/systemd/system/pihole-FTL.service:25: Ignoring unknown escape sequences: "/usr/bin/find /etc/pihole -type d -exec chmod 0755 {} \;"
I guess the backslash at the end should be escaped:
/usr/bin/find /etc/pihole -type d -exec chmod 0755 {} \\;
max.bra commented on 2025-02-24 10:06 (UTC)
i am looking at the commit history: but indeed the dependency was there but i must have done too much cleaning. sorry. restored.
Taijian commented on 2025-02-24 10:00 (UTC)
Yep, after putting 'xxd' into makedepends=(), the PKGBUILD now works in a clean chroot.
max.bra commented on 2025-02-24 10:00 (UTC)
there is also tinyxxd and xxd-standalone
have you time to do some tests?
Taijian commented on 2025-02-24 09:57 (UTC)
My guess would be that the issue is here: https://github.com/pi-hole/FTL/blob/ac500d5f1ff192d087209d6e9b955515c8f35434/src/api/docs/CMakeLists.txt#L52C1-L52C36
Cmake is looking for xxd - (g)vim satifies that makedep, so this might not be an issue on some peoples machines, but it is on other's, because it is not in the PKGBUILD...
max.bra commented on 2025-02-24 09:56 (UTC)
makepkg cannot see cmake... it must be a permission issue...
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.