It looks like this and pi-hole-server
sets different permissions to /etc/pihole
.
pi-hole-ftl: install -dm755 "$pkgdir"/etc/pihole
pi-hole-server: install -dm775 "$pkgdir"/etc/pihole
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: | 59 |
Popularity: | 1.26 |
First Submitted: | 2017-05-07 15:23 (UTC) |
Last Updated: | 2025-03-30 17:00 (UTC) |
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 46 Next › Last »
It looks like this and pi-hole-server
sets different permissions to /etc/pihole
.
pi-hole-ftl: install -dm755 "$pkgdir"/etc/pihole
pi-hole-server: install -dm775 "$pkgdir"/etc/pihole
@max.bra - No cache sync tools.
@mmtung yeah, I think @max.bra is right.
Check https://aur.archlinux.org/packages/pi-hole-ftl/#comment-758404
I bet you don't have any swap configured and/or too much memory assigned to your GPU.
@mmtung 1) absolutely not 2) i think you are out of ram
This package has various issues:
(1) Validating of source files with md5sums fails with ERROR: One or more files did not pass the validity check!
(2) Disabling validity check, compilation fails at 71% building target dnsmasq with error:
{standard input}: Assembler messages:
{standard input}:677197: Warning: end of file not at end of a line; newline inserted
{standard input}:678426: Error: symbol `.LVU22387' is already defined
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
cc: fatal error: Killed signal terminated program cc1
compilation terminated.
make[2]: *** [src/database/CMakeFiles/sqlite3.dir/build.make:82: src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:264: src/database/CMakeFiles/sqlite3.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
error making: %!s(func() string=0x7c8ff4)
my hardware is Raspberry Pi 3 Model B Rev 1.2
Thank you.
HEADS UP You need at least 800Mb of RAM to successfully compile this package.
I have a Raspberry 1 Model B+ with NO swap configured and the compilation process was always failing at 61%:
Scanning dependencies of target sqlite3 [ 61%] Building C object src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o {entrada estándar}: Mensajes del ensamblador: {entrada estándar}: Error: abre CFI al final del fichero; directiva .cfi_endproc ausente cc: error fatal: la señal Terminado (killed) terminó el programa cc1 compilación terminada. make[2]: [src/database/CMakeFiles/sqlite3.dir/build.make:82: src/database/CMakeFiles/sqlite3.dir/sqlite3.c.o] Error 1 make[1]: [CMakeFiles/Makefile2:264: src/database/CMakeFiles/sqlite3.dir/all] Error 2 make: *** [Makefile:149: all] Error 2
I added some swap on a USB drive and it compiled just fine :)
@graysky no problem for post upgrade message. it's not the first time you have cache problem with your chrom* browser. first with status icons, now with summary data... do you use some cache /tmp synchronizer? maybe some data share with one of your containers?
@euvitudo - Thank you for the suggestion. Like magic, the issue is gone!
https://wiki.archlinux.org/index.php?title=Pi-hole&type=revision&diff=626889&oldid=621677
@max.bra - post_upgrade 1-line message?
@graysky, @max.bra saw similar when I upgraded; just needed to clear out my browser cache for the pi-hole site (stale css or js?).
@graysky when FTL is stopped, my GUI is how it should be: https://postimg.cc/Whdj7SkH
i really can't get it...
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.