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 .. 29 30 31 32 33 34 35 36 37 38 39 .. 44 Next › Last »

pepper_chico commented on 2019-01-25 06:12 (UTC) (edited on 2019-01-25 06:16 (UTC) by pepper_chico)

On stop, I also always get

pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE

pihole-FTL.service: Failed with result 'exit-code'.

Not sure why, dunno whether it has any effect.

pepper_chico commented on 2019-01-25 06:05 (UTC) (edited on 2019-01-25 06:15 (UTC) by pepper_chico)

Hi @max.bra and all. I have Pi-hole running almost right in my system but I noticed that when I reboot my device all entries in the web interface are cleared and it starts collecting from scratch. It doesn't happen when I stop and start the pihole-FTL service, as of now I could only reduce the issue to a reboot.... It's even weirder because pihole-FTL.db is increasing, but when I restart the device, the web is empty of events, while pihole-FTL.db seems preserved and still increasing.

I'm searching the issue tracker about anything related but nothing relevant in particular yet. I've noticed though that it's recommended to not start the service as root (https://github.com/pi-hole/pi-hole/issues/2386), and systemctl status pihole-FTL also warns on that.

Any help appreciated.

ChuckHL commented on 2019-01-17 16:12 (UTC)

Hi max.bra,

Thank you for the assistance. Just fixed what DanSman said and I was able to finish updating and working fine.

Thank you both.

max.bra commented on 2019-01-16 21:06 (UTC) (edited on 2019-01-16 21:08 (UTC) by max.bra)

Hi ChuckHL, i don't think your problem it's related with packages you point at. I've same version of your problematic packets and my FTL starts. Take a look at pinned DanSman comment.

ChuckHL commented on 2019-01-16 17:06 (UTC)

I just upgraded my system and pihole-ftl is no longer starting.

I noticed that my system upgraded package bind-tools (bind-tools-9.13.0-2) and from that version, python3 is no longer optional, but required. It installed python-3.7.2-3 and my pihole-ftl is no longer starting.

I downgraded bind-tools to bind-tools-9.12.0-1 and removed python 3.7.2 and after rebooting, pihole was working fine.

Is there anything I need to fix so that I can reupdate bind-tools?

Regards

DanSman commented on 2019-01-10 04:32 (UTC) (edited on 2019-01-10 04:34 (UTC) by DanSman)

Hi

If someone has the same problem after the systemd update to 240.0-3.

dnsmasq/pi-hole-ftl couldn't start because systemd-resolved is using port 53.

I had to change:

/etc/systemd/resolved.conf

  • '#DNSStubListener=yes'
  • to
  • DNSStubListener=no

Thanks, Dan

max.bra commented on 2019-01-01 10:30 (UTC)

@hakayova there was some type of problem with ftl systemd tmp file creation solved, exactly, by reinstallation of the package. the reason for all this will perhaps remain a mystery. good continuation.

hakayova commented on 2019-01-01 08:31 (UTC)

Thanks for your prompt reply max.bra! I did some troubleshooting via "sudo journalctl --system -u pihole-FTL.service" which complained about not being able to write PID to the file, socket to the file and connecting to the socket, etc. despite the fact that it was a system service run by root. Having seen so many problems, I reinstalled pi-hole-server and pi-hole-ftl via yaourt and was quite happy to see that it solved the problem. Not sure what caused the corruption, but it seems to be fixed now, fingers crossed. Perhaps this may inspire somebody in the future.

Thanks for providing and maintaining such a useful package for the community!

« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 44 Next › Last »