Package Details: pi-hole-ftl 5.7-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.1
Conflicts: dnsmasq
Provides: dnsmasq
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 39
Popularity: 1.00
First Submitted: 2017-05-07 15:23
Last Updated: 2021-02-16 22:22

Required by (71)

Sources (7)

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 »

luizribeiro commented on 2021-02-28 22:52

On a fresh new install the package is giving me errors unless I remove all the /dev/shm/FTL-* files and restart the service:

-- Journal begins at Sat 2021-02-27 08:25:46 UTC, ends at Sun 2021-02-28 21:25:47 UTC. --
Feb 28 21:25:19 instance systemd[1]: Starting Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: Started Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance systemd[1]: Stopping Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Succeeded.
Feb 28 21:25:19 instance systemd[1]: Stopped Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance systemd[1]: Starting Pi-hole FTLDNS engine...
Feb 28 21:25:19 instance systemd[1]: Started Pi-hole FTLDNS engine.
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Using log file /run/log/pihole-ftl/pihole-FTL.log
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] ########## FTL started! ##########
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL branch: master
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL version: v5.7
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL commit: builtfromreleasetarball
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL date: 2021-02-16
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FTL user: pihole
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Compiled for x86_64 (compiled locally) using cc (GCC) 10.2.0
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] FATAL: create_shm(): Failed to create shared memory object "FTL-lock": File exists
Feb 28 21:25:19 instance pihole-FTL[28554]: [2021-02-28 21:25:19.091 28554M] Initialization of shared memory failed.
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Feb 28 21:25:19 instance systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 1.

Could this be because the package is setup to automatically enable the service upon install? Something else?

Also, is there any reason why (a very old) pi-hole-ftl.db is included with this package? Wouldn't pihole set that up automatically on its first run?

max.bra commented on 2021-02-25 09:58

DNS settings page error: -> https://aur.archlinux.org/packages/pi-hole-server/

nasdack commented on 2021-01-30 20:42

@graysky @max.bra Yes, no ipv6 configurations. Settings are identical across both Pi-holes, with DNS set to upstream unbound resolver and conditional forwarding enabled.

Deleted all files under /srv/pihole/ and /etc/pihole/ and reinstalled Pi-hole. Same thing occurs. I think there is something wrong with how it is reading ipv6 configuration on device.

graysky commented on 2021-01-30 13:45

@max.bra - Correct, I am pure ipv4 here.

max.bra commented on 2021-01-30 12:39

@graysky @nasdack can you confirm that you have no ipv6 connectivity configured?

max.bra commented on 2021-01-30 12:37

@nasdack have you any differences between DNS configs of your pi's?

setboolean commented on 2021-01-30 12:22

https://discourse.pi-hole.net/t/php-error-2-undefined-array-key-v6-2/43081/2

nasdack commented on 2021-01-30 12:06

@graysky

I am encountering the same error whenever I modify Settings>DNS, not just the FQDN toggle.

I have two Pi-holes that run identical versions, the error only occurs with one of them. Have tried to delete the FTL database to no avail.

graysky commented on 2021-01-29 15:58

@max.bra - How odd. Thanks for letting me know.

max.bra commented on 2021-01-29 13:28

@graysky successfully saved here, no notable syslog errors.