Package Details: pi-hole-server 4.2.1-3

Git Clone URL: https://aur.archlinux.org/pi-hole-server.git (read-only)
Package Base: pi-hole-server
Description: The Pi-hole is an advertising-aware DNS/Web server. Arch adaptation for lan wide DNS server.
Upstream URL: https://github.com/pi-hole/pi-hole
Keywords: ad block pi-hole
Licenses: EUPL-1.1
Conflicts: pi-hole-standalone
Submitter: max.bra
Maintainer: max.bra (graysky)
Last Packager: max.bra
Votes: 50
Popularity: 2.936943
First Submitted: 2016-01-13 12:50
Last Updated: 2019-02-11 11:54

Pinned Comments

max.bra commented on 2018-02-09 16:45

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 2 3 4 5 6 7 8 ... Next › Last »

mystique commented on 2019-02-05 14:36

so far a fix for me has been this:

https://github.com/pi-hole/FTL/issues/494#issuecomment-460482768

Add these lines to a new config file in /etc/dnsmasq.d/:

user=root
group=root

And restart FTL: sudo service pihole-FTL restart

And no crash that I can see.

[2019-02-05 09:02:33.862] Resizing "/FTL-strings" from 8192 to 12288 [2019-02-05 09:10:55.157] Resizing "/FTL-strings" from 12288 to 16384 [2019-02-05 09:22:47.979] Resizing "/FTL-strings" from 16384 to 20480

max.bra commented on 2019-02-05 10:03

Hi mystique, for an FTL problem you should post to FTL package. Anyway, it's a problem, i have same hardware and not a crash for now...

RyanFlaherty commented on 2019-02-04 23:54

@graysky Forgive me if I don't provide you what you need right away. I'm not a frequent poster on AUR and not really a wiz enough to maintain my own packages.

Update: looks like this is a known issue upstream https://github.com/pi-hole/FTL/pull/493

I see this behavior on my pi3b+ running arch linux on arm. my logs have it regularly failing on realloc_shm() after varying delays on startup. I notice pihole starts as root, but then when checking the webinterface its running as nobody. Could it be that when the user gets changed to 'nobody' it no longer can open and resize the shared memory object it needs?

edit: adding log excerpt below

[2019-02-04 18:04:57.170] Using log file /run/log/pihole-ftl/pihole-FTL.log
[2019-02-04 18:04:57.170] ########## FTL started! ##########
[2019-02-04 18:04:57.170] FTL branch: master
[2019-02-04 18:04:57.170] FTL version: v4.2
[2019-02-04 18:04:57.171] FTL commit: a636945
[2019-02-04 18:04:57.171] FTL date: 2019-02-03
[2019-02-04 18:04:57.171] FTL user: root
[2019-02-04 18:04:57.171] WARNING: Starting pihole-FTL as user root is not recommended
[2019-02-04 18:04:57.171] Starting config file parsing (/etc/pihole/pihole-FTL.conf)
[2019-02-04 18:04:57.171] SOCKET_LISTENING: only local
[2019-02-04 18:04:57.171] AAAA_QUERY_ANALYSIS: Show AAAA queries
[2019-02-04 18:04:57.171] MAXDBDAYS: max age for stored queries is 365 days
[2019-02-04 18:04:57.171] RESOLVE_IPV6: Resolve IPv6 addresses
[2019-02-04 18:04:57.171] RESOLVE_IPV4: Resolve IPv4 addresses
[2019-02-04 18:04:57.171] DBINTERVAL: saving to DB file every minute
[2019-02-04 18:04:57.171] DBFILE: Using /etc/pihole/pihole-FTL.db
[2019-02-04 18:04:57.172] MAXLOGAGE: Importing up to 24.0 hours of log data
[2019-02-04 18:04:57.172] PRIVACYLEVEL: Set to 0
[2019-02-04 18:04:57.172] IGNORE_LOCALHOST: Show queries from localhost
[2019-02-04 18:04:57.172] BLOCKINGMODE: Null IPs for blocked domains
[2019-02-04 18:04:57.172] REGEX_DEBUGMODE: Inactive
[2019-02-04 18:04:57.172] ANALYZE_ONLY_A_AND_AAAA: Disabled. Analyzing all queries
[2019-02-04 18:04:57.172] DBIMPORT: Importing history from database
[2019-02-04 18:04:57.172] PIDFILE: Using /run/pihole-ftl/pihole-FTL.pid
[2019-02-04 18:04:57.172] PORTFILE: Using /run/pihole-ftl/pihole-FTL.port
[2019-02-04 18:04:57.172] SOCKETFILE: Using /run/pihole-ftl/FTL.sock
[2019-02-04 18:04:57.172] WHITELISTFILE: Using /etc/pihole/whitelist.txt
[2019-02-04 18:04:57.172] BLACKLISTFILE: Using /etc/pihole/black.list
[2019-02-04 18:04:57.172] GRAVITYFILE: Using /etc/pihole/gravity.list
[2019-02-04 18:04:57.173] REGEXLISTFILE: Using /etc/pihole/regex.list
[2019-02-04 18:04:57.173] SETUPVARSFILE: Using /etc/pihole/setupVars.conf
[2019-02-04 18:04:57.173] AUDITLISTFILE: Using /etc/pihole/auditlog.list
[2019-02-04 18:04:57.173] Finished config file parsing
[2019-02-04 18:04:57.173] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
[2019-02-04 18:04:57.174] Database successfully initialized
[2019-02-04 18:04:57.175] New forward server: 8.8.4.4 (0/4096)
[2019-02-04 18:04:57.176] New forward server: 127.0.0.1 (1/4096)
[2019-02-04 18:04:57.181] Imported 1024 queries from the long-term database
[2019-02-04 18:04:57.181] -> Total DNS queries: 1024
[2019-02-04 18:04:57.181] -> Cached DNS queries: 205
[2019-02-04 18:04:57.181] -> Forwarded DNS queries: 487
[2019-02-04 18:04:57.182] -> Exactly blocked DNS queries: 180
[2019-02-04 18:04:57.182] -> Unknown DNS queries: 152
[2019-02-04 18:04:57.182] -> Unique domains: 161
[2019-02-04 18:04:57.182] -> Unique clients: 3
[2019-02-04 18:04:57.182] -> Known forward destinations: 2
[2019-02-04 18:04:57.182] Successfully accessed setupVars.conf
[2019-02-04 18:04:57.188] PID of FTL process: 13980
[2019-02-04 18:04:57.188] Listening on port 4711 for incoming IPv4 telnet connections
[2019-02-04 18:04:57.188] Listening on port 4711 for incoming IPv6 telnet connections
[2019-02-04 18:04:57.189] Listening on Unix socket
[2019-02-04 18:04:57.190] Compiled 0 Regex filters and 0 whitelisted domains in 0.1 msec (0 errors)
[2019-02-04 18:04:57.190] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms)
[2019-02-04 18:04:58.414] /etc/pihole/gravity.list: parsed 112784 domains (took 1223.4 ms)
[2019-02-04 18:04:58.414] Resizing "/FTL-strings" from 4096 to 8192
[2019-02-04 18:04:58.414] realloc_shm(): Failed to open shared memory object "/FTL-strings": Permission denied
[2019-02-04 18:04:58.415] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2019-02-04 18:04:58.415] ----------------------------> FTL crashed! <----------------------------
[2019-02-04 18:04:58.415] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2019-02-04 18:04:58.415] Please report a bug at https://github.com/pi-hole/FTL/issues
[2019-02-04 18:04:58.415] and include in your report already the following details:

[2019-02-04 18:04:58.415] FTL has been running for 1 seconds
[2019-02-04 18:04:58.415] FTL branch: master
[2019-02-04 18:04:58.415] FTL version: v4.2
[2019-02-04 18:04:58.415] FTL commit: a636945
[2019-02-04 18:04:58.415] FTL date: 2019-02-03
[2019-02-04 18:04:58.415] FTL user: root
[2019-02-04 18:04:58.415] Received signal: Segmentation fault
[2019-02-04 18:04:58.415] at address: 1995751425
[2019-02-04 18:04:58.415] with code: SEGV_MAPERR (Address not mapped to object)
[2019-02-04 18:04:58.415] Backtrace:
[2019-02-04 18:04:58.415] B[0000]: /usr/bin/pihole-FTL(+0xf6dc) [0x48f6dc]
[2019-02-04 18:04:58.415] B[0001]: /usr/lib/libc.so.6(__default_rt_sa_restorer+0) [0x76c9fe10]
[2019-02-04 18:04:58.415] Thank you for helping us to improve our FTL engine!
[2019-02-04 18:04:58.415] FTL terminated!

graysky commented on 2019-02-04 23:29

@mystique - You provided no useful info beyond some log output. What webserver? How did you trigger the error?

mystique commented on 2019-02-04 23:06

dnsadmn@vmArch59 ~> pacman -Q | grep pi-hole pi-hole-ftl 4.2-1 pi-hole-server 4.2.1-1

dnsadmn@vmArch59 ~> pihole version Pi-hole version is 4.1 (Latest: v4.2.1) FTL version is v4.2 (Latest: v4.2)

sh -x /usr/bin/pihole + /opt/pihole/version.sh Pi-hole version is 4.1 (Latest: v4.2.1) FTL version is v4.2 (Latest: v4.2)

[2019-02-04 18:04:10.653] create_shm(): shm_unlink("/FTL-client-0") failed: Permission denied (13) [2019-02-04 18:04:10.653] create_shm(): Failed to create_shm shared memory object "/FTL-client-0": File exists [2019-02-04 18:04:10.653] Failed to initialize new overTime client 0 [2019-02-04 18:04:10.653] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-04 18:04:10.653] ----------------------------> FTL crashed! <---------------------------- [2019-02-04 18:04:10.653] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-04 18:04:10.653] Please report a bug at https://github.com/pi-hole/FTL/issues [2019-02-04 18:04:10.653] and include in your report already the following details:

[2019-02-04 18:04:10.653] FTL has been running for 10 seconds [2019-02-04 18:04:10.653] FTL branch: master [2019-02-04 18:04:10.653] FTL version: v4.2 [2019-02-04 18:04:10.653] FTL commit: a636945 [2019-02-04 18:04:10.653] FTL date: 2019-02-03 [2019-02-04 18:04:10.653] FTL user: root [2019-02-04 18:04:10.653] Received signal: Segmentation fault [2019-02-04 18:04:10.653] at address: 0 [2019-02-04 18:04:10.653] with code: SEGV_MAPERR (Address not mapped to object) [2019-02-04 18:04:10.654] Backtrace: [2019-02-04 18:04:10.654] B[0000]: /usr/bin/pihole-FTL(+0x17d37) [0x5583d8771d37]

Completely stock build out of the box.. they changed things in their 4.2 release..

I'm still looking for the fix.. but wanted to share this this seems to not work..

max.bra commented on 2019-02-02 17:08

@ghost33 no new version or at least not yet officially released

max.bra commented on 2019-01-21 08:54

@pepper_chico that is not for pihole-server, it's for FTL

pepper_chico commented on 2019-01-21 08:51

On ArchLinuxARM, I had to apply the following manually for pihole to start:

DNSStubListener=no on resolved.conf

ghostv33 commented on 2018-12-30 22:32

Got it to work Forgot to copy the config file of lighttpd as stated in the wiki page And thanks for bringing pihole to arch :D Debian is slow so gave up then found this page ❤

max.bra commented on 2018-12-30 22:25

127.0.0.1/html has nothing to do with us. i don't know where that url come from but is not from this package config files for sure.

http://pi.hole/admin/ or http://<pihole_machine_ip>/admin/ or http://<localhost_127.0.0.1>/admin/ should work out of the box.

i think you'd better follow pi-hole ARCH wiki: https://wiki.archlinux.org/index.php/Pi-hole