Package Details: pi-hole-ftl 5.25.2-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: 54
Popularity: 0.33
First Submitted: 2017-05-07 15:23 (UTC)
Last Updated: 2024-05-09 11:54 (UTC)

Dependencies (6)

Required by (65)

Sources (7)

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 .. 4 5 6 7 8 9 10 11 12 13 14 .. 43 Next › Last »

max.bra commented on 2021-06-20 15:46 (UTC)

@Palaress (hi Palaress) and like L0ric0 you need to add a swap partition or file

Palaress commented on 2021-06-20 12:58 (UTC) (edited on 2021-06-20 12:59 (UTC) by Palaress)

Hello guys, I have the same problem as @L0ric0, similar error message (see below)

It's also Arch Linux aarch64

I tried upgrading from pi-hole-ftl version 5.7-1 to 5.8.1-1 by using the AUR helper yay.

Error Message:

[ 99%] Built target dnsmasq
{standard input}: Assembler messages:
{standard input}:1478379: Warning: end of file not at end of a line; newline inserted
cc: fatal error: Killed signal terminated program cc1
compilation terminated.
make[2]: *** [src/database/CMakeFiles/sqlite3.dir/build.make:90: src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o] Error 1
make[2]: *** Deleting file 'src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o'
make[1]: *** [CMakeFiles/Makefile2:348: src/database/CMakeFiles/sqlite3.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Note, that it did not fail at Build target FTL but on dnsmasq. Building FTL did pass earlier in the build process.

max.bra commented on 2021-06-14 10:53 (UTC) (edited on 2021-06-15 09:22 (UTC) by max.bra)

@dama Hi dama, glad you solved and welcome to Linux. Don't be sorry, the only problem was that this is a place for talking about the package itself and its problems and errors.
when you are in need of tips and information try first the Arch Wiki (very active and complete) than the forum. Meanwhile, in another browser tab, search for your need between "discourse", "reddit" and "stackoverflow" hundreds results. see you.

dama commented on 2021-06-14 10:44 (UTC)

@Taijian: Sorry, I'm not an developer, I thought it was a kind of debug-file. I tried systemd-swap with 1024M swap file and this works for me. Thanke for the hint!

Taijian commented on 2021-06-13 22:08 (UTC)

@dama: Have you even tried looking up swap (or swapfile) in the wiki? max.bra is not here to be your personal assistant and do your web searches for you...

max.bra commented on 2021-03-29 08:55 (UTC)

Add swapfile please

L0ric0 commented on 2021-03-29 08:52 (UTC)

I'm unable to build the package on a aarch64 with the following error:

[ 99%] Built target FTL
{standard input}: Assembler messages:
{standard input}:680985: Warning: end of file not at end of a line; newline inserted
{standard input}:681996: Error: unknown pseudo-op: `.lbb113760'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
cc: fatal error: Killed signal terminated program cc1
compilation terminated.
make[2]: *** [src/database/CMakeFiles/sqlite3.dir/build.make:90: src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:348: src/database/CMakeFiles/sqlite3.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

luizribeiro commented on 2021-02-28 22:52 (UTC)

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?