Package Details: pi-hole-ftl 6.1-1

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)

Required by (66)

Sources (5)

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.

Latest Comments

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 46 Next › Last »

hakayova commented on 2018-12-31 22:13 (UTC)

I am not sure how long has this problem existed, but I cannot seem to start pihole-FTL service anymore:

$ sudo systemctl start pihole-FTL.service $ 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: failed (Result: exit-code) since Mon 2018-12-31 16:04:03 CST; 3min 45s ago Process: 17651 ExecStart=/usr/bin/pihole-FTL no-daemon (code=exited, status=1/FAILURE) Main PID: 17651 (code=exited, status=1/FAILURE)

Dec 31 16:04:03 xxxx systemd[1]: pihole-FTL.service: Service RestartSec=100ms expired, scheduling restart. Dec 31 16:04:03 xxxx systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5. Dec 31 16:04:03 xxxx systemd[1]: Stopped Pi-hole FTLDNS engine. Dec 31 16:04:03 xxxx systemd[1]: pihole-FTL.service: Start request repeated too quickly. Dec 31 16:04:03 xxxx systemd[1]: pihole-FTL.service: Failed with result 'exit-code'. Dec 31 16:04:03 xxxx systemd[1]: Failed to start Pi-hole FTLDNS engine.

There was a recent upgrade that may have broken it. The last time I checked, it was working, probably about a month ago. I have originally set it up using Arch Wiki about a year ago. I have also been using the FTL service > 4.0 without difficulty up until recently. I haven't changed any config files recently either.

The status command output above is not very informative. Any pointers will be greatly appreciated.

max.bra commented on 2018-12-22 19:27 (UTC)

@Splith Hi Splith, there is a small problem: ftl really conflicts with dnsmasq and literally replaces it by sharing its configuration files. with this premise it is difficult to make them coexist without dramatically patching the application, that does not concern us. and more, pihole(-admin) without ftl does not work ...

if you have a good idea to propose we are all available for discussion.

for your knowledge: ftl execute a dnsmasq process for real. maybe you are not in need to directly call it.

graysky commented on 2018-12-22 12:03 (UTC)

Since ftl is a fork of dnsmasq I think the conflicts= is accurate. As to the /etc/dnsmasq.conf being owned by this package... that is unrelated to the Arch-tweaks; upstream does that so that should be a decision upstream made see FTL-4.1.2/dnsmasq/config.h for example.

I can't speak for @max.bra, but my opinion would be to do the minimal amount of patching to get the code to run on Arch.

Splith commented on 2018-12-22 10:03 (UTC)

Please fix conflict with dnsmasq by renaming the /etc/dnsmasq.conf file you install to /etc/dnsmasq-pi.conf or similar, there is NO conflict with dnsmasq and you are now breaking other packgages that rely on using dnsmasq e.g. create_ap since you are saying this package provides dnsmasq but there is no longer a dnsmasq executable.

graysky commented on 2018-12-09 22:25 (UTC)

@max.bra - I updated both packages for 4.1 just now. Minor tweaks to FTL as you see in the commit. Please review and comment if needed. Seems to be working for me as-is.

graysky commented on 2018-11-30 00:58 (UTC) (edited on 2018-11-30 01:00 (UTC) by graysky)

Yep. I can push it: https://aur.archlinux.org/cgit/aur.git/commit/?h=pi-hole-ftl&id=adc30d5a00f0

max.bra commented on 2018-11-29 22:56 (UTC)

@graysky yes of course, no problem for me! Have you already a PKGBUILD for that?

graysky commented on 2018-11-29 22:12 (UTC)

The following patch is scheduled to be included in 4.1. It causes pihole-FTL.db to get written when pihole-ftl.service is stopped. In my case, I keep the DBINTERVAL=180 so if I reboot, I lose up to 180 min of data. Adding this patch now fixes that. Shall we include it and bump to 4.0-10?

https://patch-diff.githubusercontent.com/raw/pi-hole/FTL/pull/378.patch

max.bra commented on 2018-09-18 07:15 (UTC)

@tsago updated without version bump. thanks for reporting.

tsago commented on 2018-09-17 20:15 (UTC) (edited on 2018-09-17 20:15 (UTC) by tsago)

"Cosmetic" point: During install, there's a note saying:
==> Please read the instructions on the project page: https://github.com/pi-hole/FTL#ftls-config-file

That link is no longer pointing to config documentation.
Should probably be changed to https://docs.pi-hole.net/ftldns/configfile/ (referenced by /etc/pihole/pihole-FTL.conf).

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 46 Next › Last »