Package Details: pi-hole-ftl 2.11.1-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
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 7
Popularity: 1.160470
First Submitted: 2017-05-07 15:23
Last Updated: 2017-10-08 19:56

Latest Comments

max.bra commented on 2017-09-30 21:34

dude, dude, duuuuuude (cit. https://www.youtube.com/watch?v=z9GA5yILnOI)

graysky commented on 2017-09-30 21:25

I found the problem. It was with writing to the log ftl uses for the statistics. Long story short, https://github.com/graysky2/lxc-snapshots/commit/295fa23be84600860c4ef6877084ba73f2e1935d

max.bra commented on 2017-09-30 20:46

no problem at all, keep me update

graysky commented on 2017-09-30 20:32

OK... I have confirmed the problem is not with the package but with something in the container. Sorry for all the noise.

max.bra commented on 2017-09-30 19:55

> I am running pihole in an linux container... that might be the issue.
maybe. not much experience on that.
at least, we found out that does not seem to be a compilation problem...

graysky commented on 2017-09-30 19:42

I am running pihole in an linux container... that might be the issue. I need to dig deeper. Version 2.10-1 is fine though.

graysky commented on 2017-09-30 19:41

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

max.bra commented on 2017-09-30 19:39

is it still core dump?

graysky commented on 2017-09-30 19:36

@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

max.bra commented on 2017-09-30 17:51

would you like to test mine?
https://www.dropbox.com/s/ie8z2vafp1s8i3p/pi-hole-ftl-2.11-1-armv7h.pkg.tar.xz?dl=0
just to know if it's on me or you

edit: arch arm of course

All comments