Package Details: pi-hole-ftl 5.25.2-2

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)

Required by (65)

Sources (6)

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 .. 36 37 38 39 40 41 42 43 44 Next › Last »

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'.

graysky commented on 2017-09-30 19:36 (UTC)

@max.bra - Using your package: % pihole -c /opt/pihole/chronometer.sh: connect: Connection refused /opt/pihole/chronometer.sh: line 16: /dev/tcp/localhost/4711: Connection refused /opt/pihole/chronometer.sh: connect: Connection refused /opt/pihole/chronometer.sh: line 16: /dev/tcp/localhost/4711: Connection refused /opt/pihole/chronometer.sh: connect: Connection refused /opt/pihole/chronometer.sh: line 16: /dev/tcp/localhost/4711: Connection refused /opt/pihole/chronometer.sh: connect: Connection refused /opt/pihole/chronometer.sh: line 16: /dev/tcp/localhost/4711: Connection refused /opt/pihole/chronometer.sh: connect: Connection refused /opt/pihole/chronometer.sh: line 16: /dev/tcp/localhost/4711: Connection refused

graysky commented on 2017-09-30 16:31 (UTC)

@max - Are you certain 2.11 is working for you? I have confirmed on the web GUI that I cannot connect the API backend on: armv7h, x86_64 and aarch64.

graysky commented on 2017-09-29 19:20 (UTC)

@max.bra - Yes, it too does not work but doesn't fail in a core dump. Just with 'exit-code'... not very helpful to debug. Journalctl suggests the problem is that it cannot read the log. Sep 29 15:18:06 pihole pihole-FTL[3670]: Opening of FTL's log file failed! Sep 29 15:18:06 pihole pihole-FTL[3670]: FATAL: Opening of FTL log (/var/log/pihole-FTL.log) failed! Sep 29 15:18:06 pihole pihole-FTL[3670]: Make sure it exists and is writeable by user pihole Sep 29 15:18:06 pihole systemd[1]: pi-hole-ftl.service: Main process exited, code=exited, status=1/FAILURE

graysky commented on 2017-09-29 19:08 (UTC)

@max.bra - I haven't tried a precompiled one. I will try building for x86_64 and see if it coredumps too. What is your architecture that works without issue?