FTL v4.1.1 Crash

I updated and also get an issue with FTL core dumping.
It's an original type B RPi that hosts only pi-hole and an ADS-B flight aware server.
The single core normally runs at about 50%
The DNS in my router resolves to one supplied by SMART DNS Proxy

What other info can I give you?

[2018-12-22 10:56:09.459] Compiled 0 Regex filters and 22 whitelisted domains in 19.8 msec (0 errors)
[2018-12-22 10:56:09.519] Database successfully initialized
[2018-12-22 10:56:09.568] Notice: Increasing queries struct size from 0 to 10000
[2018-12-22 10:56:09.569] Notice: Increasing domains struct size from 0 to 1000
[2018-12-22 10:56:09.569] Notice: Increasing clients struct size from 0 to 10
[2018-12-22 10:56:09.570] New forward server: 54.93.173.153 (0/0)
[2018-12-22 10:56:09.570] Notice: Increasing forwarded struct size from 0 to 4
[2018-12-22 10:56:09.570] Notice: Increasing overTime struct size from 0 to 100
[2018-12-22 10:56:09.609] New forward server: 46.116.189.68 (1/4)
[2018-12-22 10:56:11.037] Imported 3479 queries from the long-term database
[2018-12-22 10:56:11.037]  -> Total DNS queries: 3479
[2018-12-22 10:56:11.038]  -> Cached DNS queries: 137
[2018-12-22 10:56:11.109]  -> Forwarded DNS queries: 2814
[2018-12-22 10:56:11.109]  -> Exactly blocked DNS queries: 528
[2018-12-22 10:56:11.128]  -> Unknown DNS queries: 0
[2018-12-22 10:56:11.129]  -> Unique domains: 691
[2018-12-22 10:56:11.129]  -> Unique clients: 2
[2018-12-22 10:56:11.129]  -> Known forward destinations: 2
[2018-12-22 10:56:11.130] Successfully accessed setupVars.conf
[2018-12-22 10:56:11.780] PID of FTL process: 653
[2018-12-22 10:56:11.781] Listening on port 4711 for incoming IPv4 telnet connections
[2018-12-22 10:56:11.782] Listening on port 4711 for incoming IPv6 telnet connections
[2018-12-22 10:56:11.783] Listening on Unix socket
[2018-12-22 10:56:11.882] Compiled 0 Regex filters and 22 whitelisted domains in 94.8 msec (0 errors)
[2018-12-22 10:56:11.899] /etc/pihole/black.list: parsed 0 domains (took 0.1 ms)
[2018-12-22 10:56:28.337] /etc/pihole/gravity.list: parsed 136336 domains (took 16408.6 ms)
[2018-12-22 10:56:28.379] Notice: Increasing overTime struct size from 100 to 200
[2018-12-22 10:56:28.510] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-12-22 10:56:28.510] ---------------------------->  FTL crashed!  <----------------------------
[2018-12-22 10:56:28.511] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2018-12-22 10:56:28.511] Please report a bug at https://github.com/pi-hole/FTL/issues
[2018-12-22 10:56:28.512] and include in your report already the following details:

[2018-12-22 10:56:28.512] FTL has been running for 19 seconds
[2018-12-22 10:56:28.512] FTL branch: master
[2018-12-22 10:56:28.513] FTL version: v4.1.1
[2018-12-22 10:56:28.513] FTL commit: f5f331b
[2018-12-22 10:56:28.513] FTL date: 2018-12-21 10:32:10 -0600
[2018-12-22 10:56:28.514] FTL user: pihole
[2018-12-22 10:56:28.514] Received signal: Segmentation fault
[2018-12-22 10:56:28.515]      at address: 0
[2018-12-22 10:56:28.515]      with code: SEGV_MAPERR (Address not mapped to object)
[2018-12-22 10:56:28.516] Backtrace:
[2018-12-22 10:56:28.517] B[0000]: /usr/bin/pihole-FTL(+0x200e0) [0x4e70e0]
[2018-12-22 10:56:28.517] B[0001]: /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer_v2+0) [0xb6d8e1a0]
[2018-12-22 10:56:28.517] Thank you for helping us to improve our FTL engine!
[2018-12-22 10:56:28.518] FTL terminated!

Update pihole-FTL to version v4.1.2.

This issue (reported here: [4.1.1] FTL crashed · Issue #444 · pi-hole/FTL · GitHub) has been resolved through issue of V4.1.2.

Run pihole -up to update. If the update fails, then edit /etc/resolv.conf and change nameserver 127.0.0.1 to nameserver 1.1.1.1 (or third party DNS server of your choice), save and exit, then run pihole -up.

3 Likes

Fixed, thanks :smile:

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.