Pi-Hole crashes

[mayk]

Please follow the below template, it will help us to help you!

Expected Behaviour:

continuous operations.

Actual Behaviour:

crashing pihole since last update.

[2018-10-23 13:35:08.115] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-10-23 13:35:08.116] ---------------------------->  FTL crashed!  <----------------------------
[2018-10-23 13:35:08.116] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-10-23 13:35:08.116] Please report a bug at https://github.com/pi-hole/FTL/issues
[2018-10-23 13:35:08.116] and include in your report already the following details:
[2018-10-23 13:35:08.116] FTL has been running for 136729 seconds
[2018-10-23 13:35:08.116] FTL branch: 
[2018-10-23 13:35:08.117] FTL version: v4.0
[2018-10-23 13:35:08.117] FTL commit: 8493df4
[2018-10-23 13:35:08.117] FTL date: 2018-08-05 13:40:30 -0700
[2018-10-23 13:35:08.117] FTL user: pihole
[2018-10-23 13:35:08.117] Received signal: Segmentation fault
[2018-10-23 13:35:08.117]      at address: 1869348903
[2018-10-23 13:35:08.118]      with code: SEGV_MAPERR (Address not mapped to object)
[2018-10-23 13:35:08.119] Backtrace:
[2018-10-23 13:35:08.119] B[0000]: /usr/bin/pihole-FTL(+0x1870a) [0x4e870a]
[2018-10-23 13:35:08.120] B[0001]: /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0x76da86c0]
[2018-10-23 13:35:08.120] B[0002]: /usr/bin/pihole-FTL(cache_find_by_addr+0x131) [0x507b8a]
[2018-10-23 13:35:08.120] B[0003]: /usr/bin/pihole-FTL(answer_request+0x142f) [0x5056a0]
[2018-10-23 13:35:08.120] B[0004]: /usr/bin/pihole-FTL(receive_query+0x349) [0x4fcfd6]
[2018-10-23 13:35:08.120] B[0005]: /usr/bin/pihole-FTL(+0x3a172) [0x50a172]
[2018-10-23 13:35:08.120] B[0006]: /usr/bin/pihole-FTL(main_dnsmasq+0xa33) [0x50b264]
[2018-10-23 13:35:08.121] B[0007]: /usr/bin/pihole-FTL(main+0x7b) [0x4e7028]
[2018-10-23 13:35:08.121] B[0008]: /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x114) [0x76d92678]
[2018-10-23 13:35:08.121] Thank you for helping us to improve our FTL engine!
[2018-10-23 13:35:08.121] FTL terminated!

[jfb]

Please upload a debug log and post the token.

pihole -d

or do it through the Web interface:

How do I debug my Pi-hole installation?

Method 1: Generate a debug token via the Web interface Log in to your Pi-hole's Web interface Navigate to Tools > Generate debug log Click the Generate debug log button Send us the debug token [debug] Method 2: Use the command line to generate a debug token Login into your Pi-hole's command line Enter pihole -d Provide us with the debug token that is generated after the debug script completes Alternative: Securely sending us additional information Preferred Method If there is additi…

[mayk]

Hi ,

the debug token is : mi35vptt9b
Like the log suggested i also created a bug report on github.

thanx !

[mayk]

DL6ER gave feedback on github. Checking this out at the moment.

This is a crash inside dnsmasq caused by domains with incompatible characters. Looking at your debug log, I see entries like the following at the top of your /etc/pihole/gravity.list :

   ${tomcat.server}
   "c.smartclick.net
   --little--princess--.tumblr.com

They result from using adlists in an incompatible format that cannot be parsed by Pi-hole. Please remove the corresponding lists and FTL will again be stable for you.

P.S.: We intentionally forgo sanity checks of the domains in gravity.list inside of FTL to allow for a quick parsing of this file. If we'd check each domain for validity, the overall startup of FTL would need up to 30 seconds on a Raspberry Pi 1B+ which is, obviously, unacceptable.