Package Details: pi-hole-ftl 4.3-1

Git Clone URL: https://aur.archlinux.org/pi-hole-ftl.git (read-only)
Package Base: pi-hole-ftl
Description: The Pi-hole FTL engine
Upstream URL: https://github.com/pi-hole/FTL
Licenses: EUPL-1.1
Conflicts: dnsmasq
Provides: dnsmasq
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 22
Popularity: 0.439082
First Submitted: 2017-05-07 15:23
Last Updated: 2019-05-19 07:06

Required by (58)

Sources (6)

Pinned Comments

max.bra commented on 2018-02-09 16:46

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

1 2 3 4 5 6 ... Next › Last »

graysky commented on 2019-05-19 16:50

@max.bra - Not sure what is causing this (I observed it on 4.2 so it is not unique to 4.3)... what seems to fix it for me is a systemd dropin adding a 2 sec delay:

% cat /etc/systemd/system/pihole-FTL.service.d/override.conf 
[Service]
PIDFile=/run/pihole-ftl/pihole-FTL.pid
ExecPreStart=/usr/bin/sleep 2s

max.bra commented on 2019-05-19 16:20

Stupid question: maybe some pacnew merge / replace re-enable the systemd resolved dns cache?

graysky commented on 2019-05-19 09:43

@max.bra - I wonder if there is some race condition. I find that pihole-FTL fails to start about 1:3 times. In journalctl, the reason is dnsmasq[105]: failed to create listening socket for port 53: Address already in use ... here is a complete section of the log when it fails:

May 19 05:36:22 pihole pihole-FTL[333]: dnsmasq: failed to create listening socket for port 53: Address already in use
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] Using log file /run/log/pihole-ftl/pihole-FTL.log
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] ########## FTL started! ##########
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.198 333] FTL branch: master
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL version: v4.3
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL commit: 61c1f2a
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL date: 2019-05-19
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] FTL user: root
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    SOCKET_LISTENING: only local
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    AAAA_QUERY_ANALYSIS: Hide AAAA queries
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    MAXDBDAYS: max age for stored queries is 365 days
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    RESOLVE_IPV6: Don't resolve IPv6 addresses
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    RESOLVE_IPV4: Resolve IPv4 addresses
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    DBINTERVAL: saving to DB file every 10800 seconds
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    DBFILE: Using /etc/pihole/pihole-FTL.db
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.199 333]    MAXLOGAGE: Importing up to 24.0 hours of log data
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    PRIVACYLEVEL: Set to 0
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    IGNORE_LOCALHOST: Show queries from localhost
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    BLOCKINGMODE: Null IPs for blocked domains
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queri>
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    DBIMPORT: Importing history from database
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    PIDFILE: Using /run/pihole-ftl/pihole-FTL.pid
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    PORTFILE: Using /run/pihole-ftl/pihole-FTL.port
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    SOCKETFILE: Using /run/pihole-ftl/FTL.sock
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    WHITELISTFILE: Using /etc/pihole/whitelist.txt
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    BLACKLISTFILE: Using /etc/pihole/black.list
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.200 333]    GRAVITYFILE: Using /etc/pihole/gravity.list
May 19 05:36:22 pihole pihole-FTL[333]: [2019-05-19 05:36:22.201 333]    REGEXLISTFILE: Using /etc/pihole/regex.list
May 19 05:36:22 pihole dnsmasq[333]: failed to create listening socket for port 53: Address already in use
May 19 05:36:22 pihole systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

max.bra commented on 2019-05-15 16:03

@graysky - sorry for the delay, I had time to update the system only today...

..and, no, my FTL is up and running for now. rebooted 6 mins ago.

graysky commented on 2019-05-13 19:41

@max.bra - Updating to systemd packages from 242.19-1 -> 242.29-1 on RPi3 kills pihole-FTL for me. Downgrading back fixes it. Can you confirm? Symptoms:

% status pihole-FTL
● pihole-FTL.service - Pi-hole FTLDNS engine
   Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-05-13 15:36:21 EDT; 1min 39s ago
  Process: 105 ExecStart=/usr/bin/pihole-FTL no-daemon (code=exited, status=2)
 Main PID: 105 (code=exited, status=2)

May 13 15:36:21 pihole systemd[1]: pihole-FTL.service: Service RestartSec=100ms expired, scheduling restart.
May 13 15:36:21 pihole systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
May 13 15:36:21 pihole systemd[1]: Stopped Pi-hole FTLDNS engine.
May 13 15:36:21 pihole systemd[1]: pihole-FTL.service: Start request repeated too quickly.
May 13 15:36:21 pihole systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
May 13 15:36:21 pihole systemd[1]: Failed to start Pi-hole FTLDNS engine.

max.bra commented on 2019-03-02 05:20

Hi bolol, I successfully use it in my setup.

Bolol commented on 2019-03-02 00:26

It's seems DHCPv4 does not work ?

max.bra commented on 2019-02-19 20:31

there's always one. updated w/o version bump. thanks for reporting.

jshap70 commented on 2019-02-19 20:11

the link https://raw.github.com/max72bra/pi-hole-ftl-archlinux-customization/master/arch-ftl-4.2.2.patch in the PKGBUILD is returning a 503. It instead should be changed to https://raw.githubusercontent.com/max72bra/pi-hole-ftl-archlinux-customization/master/arch-ftl-4.2.2.patch (the url you get from clicking the "raw" button on github)

ghostv33 commented on 2019-02-08 19:21

@DanSman write "sudo systemctl disable systemd-resolved" restart the pc and now try installing