@max.bra Great, thanks :) I will try that this eve. Any idea on what could be causing the issue I’m seeing? Should I report it upstream to pihole devs?
Search Criteria
Package Details: pi-hole-ftl 5.25.2-2
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: | 54 |
| Popularity: | 0.011271 |
| First Submitted: | 2017-05-07 15:23 (UTC) |
| Last Updated: | 2024-08-10 09:53 (UTC) |
Dependencies (6)
- gmp (gmp-hgAUR)
- libidn (libidn-gitAUR)
- nettle (nettle-gitAUR)
- cmake (cmake-gitAUR) (make)
- sqlite (sqlite-fossilAUR) (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)
- feishu-bin (requires dnsmasq)
- gnome-network-displays (requires dnsmasq)
- gnome-network-displays-git (requires dnsmasq)
- holodev (requires dnsmasq)
- holodev-git (requires dnsmasq)
- hostsblock (requires dnsmasq) (optional)
- incus-git (requires dnsmasq)
- incus-tools-git (requires dnsmasq)
- libnm-git (requires dnsmasq) (make)
- libnm-iwd (requires dnsmasq) (make)
- libvirt-git (requires dnsmasq) (make)
- libvirt-git (requires dnsmasq) (optional)
- libvirt-xen (requires dnsmasq) (make)
- libvirt-xen (requires dnsmasq) (optional)
- linux-router (requires dnsmasq)
- linux-wifi-hotspot (requires dnsmasq) (optional)
- linux-wifi-hotspot-bin (requires dnsmasq) (optional)
- lxc-git (requires dnsmasq) (optional)
- lxc-selinux (requires dnsmasq) (optional)
- lxd-git (requires dnsmasq)
- lxd516 (requires dnsmasq)
- minimega (requires dnsmasq) (optional)
- netns-helper-git (requires dnsmasq) (optional)
- networkmanager-git (requires dnsmasq) (make)
- networkmanager-git (requires dnsmasq) (optional)
- networkmanager-iwd (requires dnsmasq) (make)
- networkmanager-iwd (requires dnsmasq) (optional)
- networkmanager-support (requires dnsmasq)
- nm-cloud-setup-git (requires dnsmasq) (make)
- nm-iwd-cloud-setup (requires dnsmasq) (make)
- overture (requires dnsmasq) (optional)
- p-rout-git (requires dnsmasq)
- pi-hole-server
- pi-hole-standalone
- pinephone-dev-tools (requires dnsmasq)
- podman-dnsname-git (requires dnsmasq)
- rbenv-vagrant-setup-git (requires dnsmasq) (optional)
- simonpi (requires dnsmasq)
- simonpi-git (requires dnsmasq)
- ss-tproxy (requires dnsmasq)
- ss-tproxy-git (requires dnsmasq)
- vagrant-git (requires dnsmasq) (optional)
- virter (requires dnsmasq) (optional)
- waydroid (requires dnsmasq)
- waydroid-git (requires dnsmasq)
Sources (6)
gecko commented on 2019-02-05 15:02 (UTC)
max.bra commented on 2019-02-05 14:25 (UTC) (edited on 2019-02-05 14:32 (UTC) by max.bra)
@gecko yes of course: browse for git modifications and download 4.1.2 tar snapshot
gecko commented on 2019-02-05 14:10 (UTC) (edited on 2019-02-05 14:20 (UTC) by gecko)
Since updating to 4.2.1 my pihole is completely broken. Journalctl shows the following on a loop: Started Pi-hole FTLDNS engine. Feb 05 15:05:00 pi systemd[1]: pihole-FTL.service: Main process exited, code=killed, status=6/ABRT Feb 05 15:05:00 pi systemd[1]: pihole-FTL.service: Failed with result 'signal'. Feb 05 15:05:00 pi systemd[1]: pihole-FTL.service: Service RestartSec=100ms expired, scheduling restart. Feb 05 15:05:00 pi systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 181.
With the restart increasing by 1 each time. The pihole-FTL daemon is also pegging one of the cores on the pi at 100% and has 30% usage of RAM.
Before the 4.2.1 update my pihole had been running without issue for months. This update was using exactly the same config as before. I tried uninstalling package completely, wiping all mentions of pihole, restarting pi, and then reinstalling, but no luck, the problem still persists. Is there a possibility to downgrade this package to the previous version?
max.bra commented on 2019-01-30 10:27 (UTC) (edited on 2019-01-30 10:29 (UTC) by max.bra)
@graysky @pepper sorry for the noise, but this from ALARM (https://archlinuxarm.org/packages/any/fake-hwclock/files) is deeply different from that in our AUR. is smarter everywhere: service start modus and moment, refresh...
it works for me! i don't have any data loss on reboot.
i thought they were the same package (stable and development) but it does not
graysky commented on 2019-01-26 18:22 (UTC)
Didn't work for me...
max.bra commented on 2019-01-26 16:49 (UTC)
@graysky @pepper any luck with fake-hwclock-git? always used it for reasons not related to pihole, never had any data loss...
graysky commented on 2019-01-25 19:33 (UTC) (edited on 2019-01-26 12:04 (UTC) by graysky)
@pepper - glad you got it working... seems like the reliance on the RTC is a design flaw but perhaps that is required for the database. I had to buy an add-on card for my ARM device to prevent data loss on reboot as well.
I added this to the wiki to help others: https://wiki.archlinux.org/index.php?title=Pi-hole&type=revision&diff=564821&oldid=557706
pepper_chico commented on 2019-01-25 15:13 (UTC) (edited on 2019-01-25 15:25 (UTC) by pepper_chico)
oh, thanks @graysky! my RTC was reporting a wrong date, sudo hwclock -w fixed it, and it survives reboots. From what I can tell, this seems to have fixed the issue :) It seems I missed the "hwclock --systohc" step in the ArchLinux setup.
pepper_chico commented on 2019-01-25 14:37 (UTC)
@graysky it's a Cubox-i 4x4
graysky commented on 2019-01-25 09:46 (UTC)
@pepper-what device? On my ODROID-C2 that lacks a RTC, this would happen even if I force write the batabase prior.
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.