FTL Crash - Githubissues

IngmarStein commented 1 month ago

Versions

Core Version is 0cf0b2a (Latest: null) Branch is development Hash is 0cf0b2ab (Latest: e3dc0670) Web Version is 05c286d (Latest: null) Branch is development Hash is 05c286df (Latest: 32f89861) FTL Version is vDev-975e7cf (Latest: null) Branch is development Hash is 975e7cf6 (Latest: 23e614cc)

Platform

OS and version: Docker
Platform: Synology

Expected behavior

FTL shouldn't crash.

Actual behavior / bug

2024-09-22 19:00:00.514 CEST [48/T21515] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: ----------------------------> FTL crashed! <---------------------------- 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: and include in your report already the following details: 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL has been running for 439505 seconds 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL branch: development 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL version: vDev-975e7cf 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL commit: 975e7cf6 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL date: 2024-09-13 21:59:06 +0200 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: FTL user: started as root, ended as root 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 13.2.1_git20240309) 13.2.1 20240309 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: Process details: MID: 48 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: PID: 48 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: TID: 21515 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: Name: dns-client 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: Received signal: Segmentation fault 2024-09-22 19:00:00.514 CEST [48/T21515] INFO: at address: 0x7f2ac43ba401 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: with code: SEGV_MAPERR (Address not mapped to object) 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!! 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: ------ Listing content of directory /dev/shm ------ 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: File Mode User:Group Size Filename 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rwxrwxrwx root:root 280 . 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rwxr-xr-x root:root 340 .. 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 569K FTL-fifo-log 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 4K FTL-per-client-regex 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 4M FTL-dns-cache 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 8K FTL-overTime 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 14M FTL-queries 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 29K FTL-upstreams 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 172K FTL-clients 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 1M FTL-domains 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 328K FTL-strings 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 140 FTL-settings 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 292 FTL-counters 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: rw------- root:root 88 FTL-lock 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: --------------------------------------------------- 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: Please also include some lines from above the !!!!!!!!! header. 2024-09-22 19:00:00.515 CEST [48/T21515] INFO: Thank you for helping us to improve our FTL engine!

There are no lines above the "!!!!!" header (the preceding message was from several hours earlier).

Steps to reproduce

I have no steps to reproduce. FTL crashed after 5 days of uptime and there was no unusual traffic when the crash happened.

Debug Token

URL: https://tricorder.pi-hole.net/JjEeSKjK

Screenshots

n/a

Additional context

Unfortunately not.

DL6ER commented 1 month ago

Sorry for it having taken so long to come back to you. The crash log above doesn't reveal anything interesting so - unless you can reproduce it - I don't think there is much we can do right now to fix this. I see you have been using a version of FTL which is about three weeks old. We merged quite a few improvements meanwhile, hopefully the bug you've been seeing is already fixed therein!