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.012724
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 .. 8 9 10 11 12 13 14 15 16 17 18 .. 44 Next › Last »

deemon commented on 2020-12-10 01:49 (UTC)

Figured it out. It's libvirtd.service that hates pihole-FTL.service trying to be dnsmasq once again and overwrites/changes the ownership of the files in /dev/shm/FTL* to root:root. It does look like a bug with pihole. Because the default dnsmasq surely does not use user "pihole" and I assume it more likely uses "root" (not 100% sure, but ... more likely than pihole). So when pihole tries to be drop-in replacement for dnsmasq and creates some extra user to run as and then fails when some other process that heavily depends on dnsmasq and runs dnsmasq(pihole in disguise) as root and overwrites something and pihole itself then crashes because it can't anymore access his own files... kinda screams for pihole inadequacy.

deemon commented on 2020-12-05 23:42 (UTC) (edited on 2020-12-10 01:45 (UTC) by deemon)

After running a while, all the FTL-* files in /dev/shm/ directory turned to root:root again and pihole-FTL.service failed again.

xyzabc123 commented on 2020-12-05 21:35 (UTC) (edited on 2020-12-05 21:36 (UTC) by xyzabc123)

@deemon: Pi-hole version is -15.2.1 (Latest: v5.2.1) is related to /opt/pihole/version.h

...
# Variables
DEFAULT="-1"
COREGITDIR="/etc/.pihole/"
WEBGITDIR="/srv/http/pihole/admin/"
...
 # Local FTL btranch is stored in /etc/pihole/ftlbranch
if [[ "$1" == "FTL" ]]; then
    branch="$(pihole-FTL branch)"
    else
        cd "${directory}" 2> /dev/null || { echo "${DEFAULT}"; return 1; }
        branch=$(git rev-parse --abbrev-ref HEAD || echo "$DEFAULT")
fi
...

Replacing DEFAULT="-1" with DEFAULT="" fixes this.

deemon commented on 2020-12-05 21:14 (UTC)

libvirtd.service complains about unparsable dnsmasq version number.

dets  05 23:11:39 Zen libvirtd[174554]: internal error: cannot parse /usr/bin/dnsmasq version number in 'Dnsmasq version pi-hole-2.81  Copyright (c) 2000-2020 Simon Kelley'

deemon commented on 2020-12-05 21:13 (UTC)

$ pihole -v
  Pi-hole version is -15.2.1 (Latest: v5.2.1)
  FTL version is 5.3.2 (Latest: v5.3.2)

not quite sure the version should be -15.2.1

deemon commented on 2020-12-05 21:07 (UTC) (edited on 2020-12-05 23:39 (UTC) by deemon)

After updating it stop starting. Apparently pihole-FTL.service started failing to start.

dets  05 23:02:15 Zen pihole-FTL[173868]: [2020-12-05 23:02:15.768 173868M] create_shm(): shm_unlink("FTL-counters") failed: Permission denied (13)
dets  05 23:02:15 Zen pihole-FTL[173868]: [2020-12-05 23:02:15.768 173868M] FATAL: create_shm(): Failed to create shared memory object "FTL-counters": File exists
dets  05 23:02:15 Zen pihole-FTL[173868]: [2020-12-05 23:02:15.768 173868M] Initialization of shared memory failed.
dets  05 23:02:15 Zen systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
dets  05 23:02:15 Zen systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
dets  05 23:02:16 Zen systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 5.
dets  05 23:02:16 Zen systemd[1]: Stopped Pi-hole FTLDNS engine.
dets  05 23:02:16 Zen systemd[1]: pihole-FTL.service: Start request repeated too quickly.
dets  05 23:02:16 Zen systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
dets  05 23:02:16 Zen systemd[1]: Failed to start Pi-hole FTLDNS engine.

so... I went to /dev/shm and moved all the FTL-* files to backup folder and it started afterwards fine. Observed that all the previous files now in backup folder are root:root, whereas the new created files are all pihole:pihole.

max.bra commented on 2020-12-03 09:52 (UTC) (edited on 2020-12-03 15:01 (UTC) by max.bra)

@setboolean yes it's true! missed that querytypes is now extern...
and no more warnings!!! nice for a patch release...
thanks for reporting.

xyzabc123 commented on 2020-12-03 09:35 (UTC)

@max.bra It seems patching HARDENING_FLAGS and EXTRAWARN is no longer necessary.

max.bra commented on 2020-12-02 08:43 (UTC)

@meijin lsof is in server now, thanks for reporting!

meijin commented on 2020-12-02 07:51 (UTC)

I think lsof is missing as a dependency:

> pihole -g
....
  [✓] Cleaning up stray matter

/usr/bin/pihole: line 268: lsof: command not found