Arch Linux User Repository

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.

Looking at this package again and checking against the 'official' changelog for 4.2, I noticed that the fix for the wpad vulnerability included in v4.2+ is not included in this package because you opted to not ship the 01-pihole.conf file included with the upstream package but instead replace it with your homebrew version 'dnsmasq.include', which hasn't been updated with this fix. Is there a reason for this that I'm just not seeing, or is this an oversight?

Crashing for me here: The -2 patch seemed to mitigate the symptoms a bit, but I get pihole rebooted every 5 minutes or so :(

It seems to be working for me as well. I've seen a few resizes occur without a crash after running for a few hours. Thank you!

this is a different machine, same env..

(formatted) https://slexy.org/view/s21gHV2g1M (/formatted)

[2019-02-05 11:43:40.691] Resizing "/FTL-queries" from 79036416 to 79331328 [2019-02-05 11:43:40.737] Resizing "/FTL-strings" from 4382720 to 4386816 [2019-02-05 11:43:40.883] Resizing "/FTL-strings" from 4386816 to 4390912 [2019-02-05 11:43:40.918] Resizing "/FTL-queries" from 79331328 to 79626240 [2019-02-05 11:43:41.037] Resizing "/FTL-strings" from 4390912 to 4395008 [2019-02-05 11:43:41.061] Imported 1104617 queries from the long-term database [2019-02-05 11:43:41.061] -> Total DNS queries: 1104617 [2019-02-05 11:43:41.061] -> Cached DNS queries: 347654 [2019-02-05 11:43:41.061] -> Forwarded DNS queries: 333982 [2019-02-05 11:43:41.061] -> Exactly blocked DNS queries: 422981 [2019-02-05 11:43:41.061] -> Unknown DNS queries: 0 [2019-02-05 11:43:41.061] -> Unique domains: 72655 [2019-02-05 11:43:41.062] -> Unique clients: 3 [2019-02-05 11:43:41.062] -> Known forward destinations: 1 [2019-02-05 11:43:41.062] Successfully accessed setupVars.conf [2019-02-05 11:43:41.092] PID of FTL process: 374 [2019-02-05 11:43:41.092] Listening on port 4711 for incoming IPv4 telnet connections [2019-02-05 11:43:41.092] Listening on Unix socket [2019-02-05 11:43:41.101] Compiled 0 Regex filters and 14 whitelisted domains in 0.1 msec (0 errors) [2019-02-05 11:43:41.105] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms) [2019-02-05 11:43:41.488] /etc/pihole/gravity.list: parsed 126293 domains (took 377.2 ms) [2019-02-05 11:43:49.749] Resizing "/FTL-queries" from 79626240 to 79921152 [2019-02-05 11:43:57.435] Resizing "/FTL-strings" from 4395008 to 4399104 [2019-02-05 11:44:58.785] Resizing "/FTL-strings" from 4399104 to 4403200 [2019-02-05 11:45:10.911] Resizing "/FTL-queries" from 79921152 to 80216064 [2019-02-05 11:46:07.925] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-05 11:46:07.925] ----------------------------> FTL crashed! <---------------------------- [2019-02-05 11:46:07.925] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-05 11:46:07.925] Please report a bug at https://github.com/pi-hole/FTL/issues [2019-02-05 11:46:07.925] and include in your report already the following details: [2019-02-05 11:46:07.925] FTL has been running for 183 seconds [2019-02-05 11:46:07.925] FTL branch: master [2019-02-05 11:46:07.925] FTL version: v4.2 [2019-02-05 11:46:07.925] FTL commit: aca02c4 [2019-02-05 11:46:07.925] FTL date: 2019-02-03 [2019-02-05 11:46:07.925] FTL user: root [2019-02-05 11:46:07.925] Received signal: Segmentation fault [2019-02-05 11:46:07.925] at address: 140136641380264 [2019-02-05 11:46:07.925] with code: SEGV_MAPERR (Address not mapped to object) [2019-02-05 11:46:07.926] Backtrace: [2019-02-05 11:46:07.926] B[0000]: /usr/bin/pihole-FTL(+0x17d37) [0x556704054d37] [2019-02-05 11:46:07.926] B[0001]: /usr/lib/libpthread.so.0(+0x123c0) [0x7f74200403c0] [2019-02-05 11:46:07.926] B[0002]: /usr/bin/pihole-FTL(FTL_new_query+0x34b) [0x55670405e1fb] [2019-02-05 11:46:07.926] B[0003]: /usr/bin/pihole-FTL(tcp_request+0x65a) [0x55670406f61a] [2019-02-05 11:46:07.926] B[0004]: /usr/bin/pihole-FTL(+0x45816) [0x556704082816] [2019-02-05 11:46:07.926] B[0005]: /usr/bin/pihole-FTL(main_dnsmasq+0x1188) [0x556704084418] [2019-02-05 11:46:07.926] B[0006]: /usr/bin/pihole-FTL(main+0xce) [0x55670405326e] [2019-02-05 11:46:07.926] B[0007]: /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f741fe8e223] [2019-02-05 11:46:07.926] B[0008]: /usr/bin/pihole-FTL(_start+0x2e) [0x5567040533ae] [2019-02-05 11:46:07.926] Thank you for helping us to improve our FTL engine! [2019-02-05 11:46:07.926] FTL terminated! [2019-02-05 11:46:26.876] Resizing "/FTL-strings" from 4403200 to 4407296 [2019-02-05 11:46:49.395] Resizing "/FTL-queries" from 80216064 to 80510976

esxi 6.x vm, dual core, 2GB ram.

[2019-02-05 11:43:40.691] Resizing "/FTL-queries" from 79036416 to 79331328 [2019-02-05 11:43:40.737] Resizing "/FTL-strings" from 4382720 to 4386816 [2019-02-05 11:43:40.883] Resizing "/FTL-strings" from 4386816 to 4390912 [2019-02-05 11:43:40.918] Resizing "/FTL-queries" from 79331328 to 79626240 [2019-02-05 11:43:41.037] Resizing "/FTL-strings" from 4390912 to 4395008 [2019-02-05 11:43:41.061] Imported 1104617 queries from the long-term database [2019-02-05 11:43:41.061] -> Total DNS queries: 1104617 [2019-02-05 11:43:41.061] -> Cached DNS queries: 347654 [2019-02-05 11:43:41.061] -> Forwarded DNS queries: 333982 [2019-02-05 11:43:41.061] -> Exactly blocked DNS queries: 422981 [2019-02-05 11:43:41.061] -> Unknown DNS queries: 0 [2019-02-05 11:43:41.061] -> Unique domains: 72655 [2019-02-05 11:43:41.062] -> Unique clients: 3 [2019-02-05 11:43:41.062] -> Known forward destinations: 1 [2019-02-05 11:43:41.062] Successfully accessed setupVars.conf [2019-02-05 11:43:41.092] PID of FTL process: 374 [2019-02-05 11:43:41.092] Listening on port 4711 for incoming IPv4 telnet connections [2019-02-05 11:43:41.092] Listening on Unix socket [2019-02-05 11:43:41.101] Compiled 0 Regex filters and 14 whitelisted domains in 0.1 msec (0 errors) [2019-02-05 11:43:41.105] /etc/pihole/black.list: parsed 0 domains (took 0.0 ms) [2019-02-05 11:43:41.488] /etc/pihole/gravity.list: parsed 126293 domains (took 377.2 ms) [2019-02-05 11:43:49.749] Resizing "/FTL-queries" from 79626240 to 79921152 [2019-02-05 11:43:57.435] Resizing "/FTL-strings" from 4395008 to 4399104 [2019-02-05 11:44:58.785] Resizing "/FTL-strings" from 4399104 to 4403200 [2019-02-05 11:45:10.911] Resizing "/FTL-queries" from 79921152 to 80216064 [2019-02-05 11:46:07.925] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-05 11:46:07.925] ----------------------------> FTL crashed! <---------------------------- [2019-02-05 11:46:07.925] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [2019-02-05 11:46:07.925] Please report a bug at https://github.com/pi-hole/FTL/issues [2019-02-05 11:46:07.925] and include in your report already the following details: [2019-02-05 11:46:07.925] FTL has been running for 183 seconds [2019-02-05 11:46:07.925] FTL branch: master [2019-02-05 11:46:07.925] FTL version: v4.2 [2019-02-05 11:46:07.925] FTL commit: aca02c4 [2019-02-05 11:46:07.925] FTL date: 2019-02-03 [2019-02-05 11:46:07.925] FTL user: root [2019-02-05 11:46:07.925] Received signal: Segmentation fault [2019-02-05 11:46:07.925] at address: 140136641380264 [2019-02-05 11:46:07.925] with code: SEGV_MAPERR (Address not mapped to object) [2019-02-05 11:46:07.926] Backtrace: [2019-02-05 11:46:07.926] B[0000]: /usr/bin/pihole-FTL(+0x17d37) [0x556704054d37] [2019-02-05 11:46:07.926] B[0001]: /usr/lib/libpthread.so.0(+0x123c0) [0x7f74200403c0] [2019-02-05 11:46:07.926] B[0002]: /usr/bin/pihole-FTL(FTL_new_query+0x34b) [0x55670405e1fb] [2019-02-05 11:46:07.926] B[0003]: /usr/bin/pihole-FTL(tcp_request+0x65a) [0x55670406f61a] [2019-02-05 11:46:07.926] B[0004]: /usr/bin/pihole-FTL(+0x45816) [0x556704082816] [2019-02-05 11:46:07.926] B[0005]: /usr/bin/pihole-FTL(main_dnsmasq+0x1188) [0x556704084418] [2019-02-05 11:46:07.926] B[0006]: /usr/bin/pihole-FTL(main+0xce) [0x55670405326e] [2019-02-05 11:46:07.926] B[0007]: /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f741fe8e223] [2019-02-05 11:46:07.926] B[0008]: /usr/bin/pihole-FTL(_start+0x2e) [0x5567040533ae] [2019-02-05 11:46:07.926] Thank you for helping us to improve our FTL engine! [2019-02-05 11:46:07.926] FTL terminated! [2019-02-05 11:46:26.876] Resizing "/FTL-strings" from 4403200 to 4407296 [2019-02-05 11:46:49.395] Resizing "/FTL-queries" from 80216064 to 80510976

It did crash, but it spawned another and kept going..

dnsadmn@arch98c1e8 /etc> cat -n dnsmasq.d/* | egrep -v "#" 22
23 addn-hosts=/etc/pihole/gravity.list 24 addn-hosts=/etc/pihole/local.list 25 addn-hosts=/etc/pihole/black.list 26 localise-queries 27 no-resolv 28 cache-size=10000 29 log-queries=extra 30 log-facility=/run/log/pihole/pihole.log 31 local-ttl=2 32 log-async 33 server=127.0.0.1#5353 34 server=127.0.0.1#5454 35 interface=ens192 36
37 all-servers 38 edns-packet-max=4096

23-35 is pihole config and 37-38 is a local.conf that I added to get my 33-34 recursors going. The edns is for the squid proxies directly querying this machine.

[2019-02-05 10:01:14.786] ########## FTL started! ##########
[2019-02-05 10:01:14.786] FTL branch: master
[2019-02-05 10:01:14.786] FTL version: v4.2
[2019-02-05 10:01:14.787] FTL commit: aca02c4
[2019-02-05 10:01:14.787] FTL date: 2019-02-03
[2019-02-05 10:01:14.787] FTL user: root

Will report back if there are issues.

Thanks

@RyanFlaherty @mystique - Please try pi-hole-ftl 4.2-2

@max.bra - Seems to be fixed for me. I will push to the AUR. BTW, you can trigger the bug by browsing to sites with a lot of ads at least on ARM hardware.

For example: https://www.reddit.com/r/pihole/comments/8jsgt3/what_is_your_go_to_site_for_testing_that/

Here is my log tailed with the patches:

% tail -f /run/log/pihole-ftl/pihole-FTL.log 
% tail -f /run/log/pihole-ftl/pihole-FTL.log 
[2019-02-05 09:53:47.023]  -> Unique clients: 8
[2019-02-05 09:53:47.023]  -> Known forward destinations: 1
[2019-02-05 09:53:47.023] Successfully accessed setupVars.conf
[2019-02-05 09:53:47.027] PID of FTL process: 141
[2019-02-05 09:53:47.027] Listening on port 4711 for incoming IPv4 telnet connections
[2019-02-05 09:53:47.027] Listening on port 4711 for incoming IPv6 telnet connections
[2019-02-05 09:53:47.027] Listening on Unix socket
[2019-02-05 09:53:47.029] Compiled 0 Regex filters and 29 whitelisted domains in 0.1 msec (0 errors)
[2019-02-05 09:53:47.029] /etc/pihole/black.list: parsed 4 domains (took 0.1 ms)
[2019-02-05 09:53:49.223] /etc/pihole/gravity.list: parsed 264453 domains (took 2193.6 ms)
[2019-02-05 09:55:44.196] Resizing "/FTL-strings" from 24576 to 28672
[2019-02-05 09:55:51.190] Resizing "/FTL-strings" from 28672 to 32768

egrep -v "^#" /etc/security/limits.conf

proxy soft nofile 65536
proxy hard nofile 65536

* soft nofile 65536
* hard nofile 65536

(don't hate please.. runit-systemd) I needed it to keep running regardless of the crash until I could work something out..

cat /var/service/pihole-ftl/run

#!/bin/sh -e

exec chpst -o 65536 chpst -e env \
/usr/bin/pihole-FTL -f

and in env I just set TZ=/etc/localtime

OT: https://blog.packagecloud.io/eng/2017/02/21/set-environment-variable-save-thousands-of-system-calls/

@max.bra - I am testing the two commits @mystique referenced now on my ARM device. No crash yet. If it's good, I will push to pi-hole-ftl-4.2-2 which will incorporate them. It seems as though upstream has a 4.2.1 milestone queued up with these fixes: https://github.com/pi-hole/FTL/milestone/13

for me default limits.conf, systemd/system.conf and systemd/user.conf...