hi prakkie, do you have any relevant errors in your syslog?
Search Criteria
Package Details: pi-hole-ftl 5.25.2-2
Package Actions
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.029901 |
First Submitted: | 2017-05-07 15:23 (UTC) |
Last Updated: | 2024-08-10 09:53 (UTC) |
Dependencies (6)
- gmp (gmp-hgAUR)
- libidn (libidn-gitAUR)
- nettle (nettle-gitAUR)
- cmake (cmake-gitAUR) (make)
- sqlite (sqlite-fossilAUR) (make)
- xxd (vim-minimal-gitAUR, gvim-gitAUR, vim-cli-gitAUR, gvim-wayland-lilydjwg-gitAUR, gvim-gtk2AUR, gvim, tinyxxd, vim) (make)
Required by (65)
- adhocspot-script-git (requires dnsmasq)
- airgeddon (requires dnsmasq) (optional)
- anti-ad-dnsmasq-git (requires dnsmasq)
- appgate-sdp (requires dnsmasq) (optional)
- appgate-sdp-headless (requires dnsmasq) (optional)
- archpxe (requires dnsmasq)
- berate_ap-git (requires dnsmasq)
- blueman-git (requires dnsmasq) (optional)
- corplink-bin (requires dnsmasq)
- create_ap (requires dnsmasq)
- create_ap-git (requires dnsmasq)
- cuttlefish-base-git (requires dnsmasq)
- dns-zone-blacklist-git (requires dnsmasq) (optional)
- dnsmasq-china-list-git (requires dnsmasq)
- dnsmasq-openrc (requires dnsmasq)
- docker-dnsmasq (requires dnsmasq)
- docker-machine-driver-kvm2 (requires dnsmasq)
- easywifi-git (requires dnsmasq) (optional)
- ethoscope-device (requires dnsmasq)
- ethoscope-node (requires dnsmasq)
- Show 45 more...
Sources (6)
Latest Comments
« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 44 Next › Last »
max.bra commented on 2020-10-28 18:02 (UTC)
Prakkie commented on 2020-10-28 14:56 (UTC)
Versions Pi-hole: v5.1.2 FTL: v5.2 Platform OS and version: Arch Linux 5.9.1 Platform: Desktop Expected behavior Settings through UI should get saved.
Actual behavior / bug _No setting through UI is getting saved. I am using nginx. It was all working till upgrade to this version. Tried after complete browser cache clear too. Still issue persists. Also, checked http user expiry. All good with the user. _
Steps to reproduce Steps to reproduce the behavior:
Click on any option and change the setting. Click on any other option. Whatever changes made wont get saved and resets to whatever there before. Tried with disabling pihole for all time options, DNS settings, UI theme to dark.
Exarch commented on 2020-10-21 15:11 (UTC) (edited on 2020-10-21 16:16 (UTC) by Exarch)
@max.bra I have uncommented the two extensions mentioned on the wiki and installed php-sqlite
However...I just rebooted, I had updated previously the kernel among other things, and now I see different errors:
Oct 21 11:13:26 terminal-rp4 sudo[2016]: pam_unix(sudo:auth): conversation failed
Oct 21 11:13:26 terminal-rp4 sudo[2016]: pam_unix(sudo:auth): auth could not identify password for [http]
max.bra commented on 2020-10-21 14:55 (UTC)
@Exarch follow the php wiki, luke... follow the php wiki...
Exarch commented on 2020-10-21 14:48 (UTC) (edited on 2020-10-21 14:54 (UTC) by Exarch)
I'm having issues with nginx and sqlite. Looking though the nginx logs I see this error:
2020/10/21 09:45:19 [error] 18615#18615: *1 FastCGI sent in stderr: "PHP message: PHP Warning: Use of undefined constant SQLITE3_OPEN_READONLY - assumed 'SQLITE3_OPEN_READONLY' (this will throw an Error in a future version of PHP) in /srv/http/pihole/admin/scripts/pi-hole/php/database.php on line 61PHP message: PHP Fatal error: Uncaught Error: Class 'SQLite3' not found in /srv/http/pihole/admin/scripts/pi-hole/php/database.php:42
archery commented on 2020-10-08 13:30 (UTC)
Getting the following errror with version 5.2:
Process 324 (pihole-FTL) of user 994 dumped core.
Stack trace of thread 324:
#0 0x00000000004a4188 _FTL_new_query (pihole-FTL + 0x14188)
madhatt commented on 2020-09-30 00:07 (UTC)
I am seeing the same issue as @akya re: file in /dev/shm.
akya commented on 2020-09-16 05:33 (UTC) (edited on 2020-09-16 05:34 (UTC) by akya)
I am getting this -
pihole-FTL.service - Pi-hole FTLDNS engine
Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-09-16 09:57:56 IST; 49min ago
Process: 20560 ExecStartPre=/bin/chown -R pihole:pihole /etc/pihole (code=exited, status=0/SUCCESS)
Process: 20561 ExecStartPre=/bin/chown root:root /etc/pihole/logrotate (code=exited, status=0/SUCCESS)
Process: 20562 ExecStart=/usr/bin/pihole-FTL no-daemon (code=exited, status=1/FAILURE)
Main PID: 20562 (code=exited, status=1/FAILURE)
Sep 16 09:57:56 quady pihole-FTL[20562]: [2020-09-16 09:57:56.155 20562M] Finished config file parsing
Sep 16 09:57:56 quady pihole-FTL[20562]: [2020-09-16 09:57:56.155 20562M] create_shm(): shm_unlink("/FTL-lock") failed: Permission denied (13)
Sep 16 09:57:56 quady pihole-FTL[20562]: [2020-09-16 09:57:56.155 20562M] FATAL: create_shm(): Failed to create_shm shared memory object "/FTL-lock": File exists
Sep 16 09:57:56 quady systemd[1]: pihole-FTL.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 09:57:56 quady systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Sep 16 09:57:56 quady systemd[1]: pihole-FTL.service: Scheduled restart job, restart counter is at 6.
Sep 16 09:57:56 quady systemd[1]: Stopped Pi-hole FTLDNS engine.
Sep 16 09:57:56 quady systemd[1]: pihole-FTL.service: Start request repeated too quickly.
Sep 16 09:57:56 quady systemd[1]: pihole-FTL.service: Failed with result 'exit-code'.
Sep 16 09:57:56 quady systemd[1]: Failed to start Pi-hole FTLDNS engine.
once I clear the FTL-* files in /dev/shm
the FTL service will start. I am guessing this is a permission issue introduced in the last update?
andreapier commented on 2020-08-21 09:20 (UTC)
It worked, thanks.
max.bra commented on 2020-08-21 08:56 (UTC)
@andreapier assuming you have not any hardware or filesystem problem, please try to build wiping your build cache or better from the snapshot.
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.