pihole-ftl crashes after a number of days.
Expected Behaviour:
raspberry pi 4B 4GB running raspbian buster, fully updated.
Actual Behaviour:
(Moderator edit: explicit debug log removed)
The dashboard looked normal until FTL crashed. To get normal operation i had to start pihole-ftl, stop it and then start again.
When i click on any point on the total queries graph before the crash i can see it blocking or forwarding as normal but all the forwarding entries show Reply as N/A. After the restart, replies are as expected
I have removed your debug log output for privacy reasons. In addition, it was malformatted beyond repair, making it hard to read.
When producing a debug log, you'll have the choice to upload it into a protected area on Pi-hole's servers, where only a limited number of trusted moderators and developers have access, and it's also kept for 48 hours only before being auto-deleted.
It is sufficient to just post the debug token shown at the end of the process to allow access by moderators and developers.
The debug log is also a good source for analysing problems yourself, as it may contain hints at possible solutions if obvious errors are detected during its creation.
Please probide a new debug token generated by
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Without FTL running i cannot upload the debug log. Perhaps if you included in the FAQ section how to get dns working without FTL running?
https://tricorder.pi-hole.net/cot491nvdf
restarting pihole-FTLmay remove pertinent crash information from the debug log.
Another crash.
Again pihole-ftl had to be started, stopped and then started again before normal operation
Can you post lines from /var/log/pihole-FTL.log where ist state "FTL crashed"?
[2020-05-29 06:32:08.560 8493] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-05-29 06:32:08.560 8493] ----------------------------> FTL crashed! <----------------------------
[2020-05-29 06:32:08.560 8493] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-05-29 06:32:08.560 8493] Please report a bug at GitHub · Where software is built
[2020-05-29 06:32:08.560 8493] and include in your report already the following details:
[2020-05-29 06:32:08.560 8493] FTL has been running for 83320 seconds
[2020-05-29 06:32:08.560 8493] FTL branch: master
[2020-05-29 06:32:08.560 8493] FTL version: v5.0
[2020-05-29 06:32:08.560 8493] FTL commit: 3d7c095
[2020-05-29 06:32:08.560 8493] FTL date: 2020-05-10 18:58:38 +0100
[2020-05-29 06:32:08.561 8493] FTL user: started as pihole, ended as pihole
[2020-05-29 06:32:08.561 8493] Compiled for armhf (compiled on CI) using arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516
[2020-05-29 06:32:08.561 8493] Received signal: Segmentation fault
[2020-05-29 06:32:08.561 8493] at address: 0xa1e340f8
[2020-05-29 06:32:08.561 8493] with code: SEGV_MAPERR (Address not mapped to object)
[2020-05-29 06:32:08.561 8493] Backtrace:
[2020-05-29 06:32:08.562 8493] B[0000]: 0x47a8e4, /usr/bin/pihole-FTL(+0x238e4) [0x47a8e4]
[2020-05-29 06:32:08.562 8493] B[0001]: 0xb6e09130, /lib/arm-linux-gnueabihf/libc.so.6(__default_rt_sa_restorer+0) [0xb6e09130]
[2020-05-29 06:32:08.562 8493] B[0002]: 0x49b9c6, /usr/bin/pihole-FTL(cache_recv_insert+0x115) [0x49b9c6]
[2020-05-29 06:32:08.562 8493] B[0003]: 0x49e9b6, /usr/bin/pihole-FTL(+0x479b6) [0x49e9b6]
[2020-05-29 06:32:08.562 8493] B[0004]: 0x49ffcc, /usr/bin/pihole-FTL(main_dnsmasq+0xc07) [0x49ffcc]
[2020-05-29 06:32:08.562 8493] B[0005]: 0x470da8, /usr/bin/pihole-FTL(main+0xa7) [0x470da8]
[2020-05-29 06:32:08.562 8493] B[0006]: 0xb6df3718, /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x10c) [0xb6df3718]
[2020-05-29 06:32:08.562 8493] ------ Listing content of directory /dev/shm ------
[2020-05-29 06:32:08.562 8493] File Mode User:Group Filesize Filename
[2020-05-29 06:32:08.563 8493] rwxrwxrwx root:root 260 .
[2020-05-29 06:32:08.563 8493] rwxr-xr-x root:root 4K ..
[2020-05-29 06:32:08.563 8493] rw------- pihole:pihole 4K FTL-per-client-regex
[2020-05-29 06:32:08.563 8493] rw------- pihole:pihole 29K FTL-dns-cache
[2020-05-29 06:32:08.563 8493] rw------- pihole:pihole 29K FTL-overTime
[2020-05-29 06:32:08.564 8493] rw------- pihole:pihole 1M FTL-queries
[2020-05-29 06:32:08.564 8493] rw------- pihole:pihole 20K FTL-upstreams
[2020-05-29 06:32:08.564 8493] rw------- pihole:pihole 643K FTL-clients
[2020-05-29 06:32:08.564 8493] rw------- pihole:pihole 66K FTL-domains
[2020-05-29 06:32:08.565 8493] rw------- pihole:pihole 45K FTL-strings
[2020-05-29 06:32:08.565 8493] rw------- pihole:pihole 12 FTL-settings
[2020-05-29 06:32:08.565 8493] rw------- pihole:pihole 124 FTL-counters
[2020-05-29 06:32:08.565 8493] rw------- pihole:pihole 28 FTL-lock
[2020-05-29 06:32:08.565 8493] ---------------------------------------------------
[2020-05-29 06:32:08.565 8493] Thank you for helping us to improve our FTL engine!
[2020-05-29 06:32:08.566 8493] FTL terminated!
Perfect, maybe a few lines above
----------------------------> FTL crashed! <---------------------------
as well.
There a few bugs about FTL issues since v5.0 on github. It would be really helpful if you could attach a debugger to FTL as described here: Redirecting...
A dev will likely reach out to you to ask for more information.
Pinging @DL6ER
With severely limited linux skills I think it's running. I can see threads starting and exiting.
If a dev does contact me it will have to be words of single syllables.
1 Like
preceding lines:
[2020-05-29 00:59:00.245 8493] Notice: Database size is 95.15 MB, deleted 1340 rows
[2020-05-29 02:00:00.136 8493] Notice: Database size is 95.15 MB, deleted 973 rows
[2020-05-29 02:59:00.199 8493] Notice: Database size is 95.15 MB, deleted 469 rows
[2020-05-29 03:20:34.732 8493] Resizing "/FTL-dns-cache" from 24576 to 28672
[2020-05-29 03:24:54.955 8493] Resizing "/FTL-strings" from 40960 to 45056
[2020-05-29 03:59:00.217 8493] Notice: Database size is 95.15 MB, deleted 1456 rows
[2020-05-29 04:59:00.241 8493] Notice: Database size is 95.15 MB, deleted 1149 rows
[2020-05-29 06:00:00.253 8493] Notice: Database size is 95.15 MB, deleted 736 rows
[2020-05-29 06:32:08.560 8493] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[2020-05-29 06:32:08.560 8493] ----------------------------> FTL crashed! <----------------------------
[2020-05-29 06:32:08.560 8493] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Let's wait for it to crash again to squash the bug.
Well it's been a week and no crash yet. I will leave the debugger running but I have to confess I changed the POE injector and the POE switch port before starting the debugger.
Good for you - but we would like to see the bug again 
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.