| 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) |
/run/pihole-ftl/FTL.sock is causing pacman to return an error on every package when creating temporary files:
(3/4) Creating temporary files...
error: command failed to execute correctly
Running systemd-hook tmpfiles returns the following:
$ sudo /usr/share/libalpm/scripts/systemd-hook tmpfiles
/run/pihole-ftl/FTL.sock is not a file.
When the FTL service is stopped (and FTL.sock is gone) pacman no longer returns errors when installing packages. Is there any way to fix this?
Has anyone else noticed that TIMEFRAME=today setting in /etc/pihole/pihole-FTL.conf is being ignored on this update?
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.
2.12-3 please refer to Pi-hole wiki for new configuration options
Stop official service
I can confirm that, 60, 120, and 600 work. But 3600 does not.
...how did you get that debug output?
@graysky i suspected it.
I noticed yesterday that the commit countdown starts from an integer portion of time. I'll explain:
my yesterday test was on a 10-minute commit and the debug output, summarizing, said:
20:43 ftl started
20:50 commit
21:00 commit
so it may be that for portions of time greater than one hour it can not trigger.
need to inspect the source
Is anyone else experiencing no writes to /etc/pihole/pihole-FTL.db with large values such as 3600 (package default)?
waiting for a parameterized version, you can customize the FTL database commit interval by modifying the following PKGBUILD line:
sed -i "s|#define DBinterval 60|#define DBinterval 3600|w $_ssc" "$srcdir"/$_pkgname-$pkgver/FTL.h
where 3600 is for this package new timing of an hour. you can write 600 for 10 minutes or 7200 for 2 hours and so on.
@graysky - the define is perfectly honored. applying...
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.