FTL segmentation fault

[KatsuroKurosaki]

Versions

• Core version is v6.0.5 (Latest: v6.0.5)
• Web version is v6.0.2 (Latest: v6.0.2)
• FTL version is v6.0.4 (Latest: v6.0.4)

Platform

• OS and version: Debian 12 - Docker engine community 28.0.1
• Platform: Physical Intel NUC

Actual behavior

FTL just triggered a segmentation fault and the container just restarted, this is what the docker logs pihole returns:

2025-03-11 06:33:58.134 AST [48M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-11 06:33:58.134 AST [48M] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-03-11 06:33:58.134 AST [48M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-11 06:33:58.134 AST [48M] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-03-11 06:33:58.134 AST [48M] INFO: and include in your report already the following details:
2025-03-11 06:33:58.134 AST [48M] INFO: FTL has been running for 25248 seconds
2025-03-11 06:33:58.134 AST [48M] INFO: FTL branch: master
2025-03-11 06:33:58.134 AST [48M] INFO: FTL version: v6.0.4
2025-03-11 06:33:58.134 AST [48M] INFO: FTL commit: b7eb53bf
2025-03-11 06:33:58.135 AST [48M] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-11 06:33:58.135 AST [48M] INFO: FTL user: started as pihole, ended as pihole
2025-03-11 06:33:58.135 AST [48M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-11 06:33:58.135 AST [48M] INFO: Process details: MID: 48
2025-03-11 06:33:58.135 AST [48M] INFO:                  PID: 48
2025-03-11 06:33:58.135 AST [48M] INFO:                  TID: 48
2025-03-11 06:33:58.135 AST [48M] INFO:                  Name: pihole-FTL
2025-03-11 06:33:58.135 AST [48M] INFO: Received signal: Segmentation fault
2025-03-11 06:33:58.135 AST [48M] INFO:      at address: 0x6f4285449be4
2025-03-11 06:33:58.135 AST [48M] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-03-11 06:33:58.135 AST [48M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-03-11 06:33:58.135 AST [48M] INFO: ------ Listing content of directory /dev/shm ------
2025-03-11 06:33:58.135 AST [48M] INFO: File Mode User:Group      Size  Filename
2025-03-11 06:33:58.135 AST [48M] INFO: rwxrwxrwx root:root       360   .
2025-03-11 06:33:58.135 AST [48M] INFO: rwxr-xr-x root:root       340   ..
2025-03-11 06:33:58.135 AST [48M] INFO: rw------- pihole:pihole   786K  FTL-48-recycler
2025-03-11 06:33:58.135 AST [48M] INFO: rw------- pihole:pihole   602K  FTL-48-dns-cache-lookup
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole   373K  FTL-48-domains-lookup
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole     4K  FTL-48-clients-lookup
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole   569K  FTL-48-fifo-log
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole     4K  FTL-48-per-client-regex
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole     3M  FTL-48-dns-cache
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole     8K  FTL-48-overTime
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole   383M  FTL-48-queries
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole    29K  FTL-48-upstreams
2025-03-11 06:33:58.136 AST [48M] INFO: rw------- pihole:pihole   348K  FTL-48-clients
2025-03-11 06:33:58.137 AST [48M] INFO: rw------- pihole:pihole     1M  FTL-48-domains
2025-03-11 06:33:58.137 AST [48M] INFO: rw------- pihole:pihole     2M  FTL-48-strings
2025-03-11 06:33:58.137 AST [48M] INFO: rw------- pihole:pihole   144   FTL-48-settings
2025-03-11 06:33:58.137 AST [48M] INFO: rw------- pihole:pihole   328   FTL-48-counters
2025-03-11 06:33:58.138 AST [48M] INFO: rw------- pihole:pihole    88   FTL-48-lock
2025-03-11 06:33:58.138 AST [48M] INFO: ---------------------------------------------------
2025-03-11 06:33:58.138 AST [48M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-03-11 06:33:58.138 AST [48M] INFO: Thank you for helping us to improve our FTL engine!
2025-03-11 06:33:58.138 AST [48M] INFO: Waiting for threads to join
2025-03-11 06:33:58.138 AST [48M] INFO: Thread database (0) is idle, terminating it.
2025-03-11 06:33:58.138 AST [48M] INFO: Thread housekeeper (1) is idle, terminating it.
2025-03-11 06:33:58.139 AST [48M] INFO: Thread dns-client (2) is idle, terminating it.
2025-03-11 06:33:58.139 AST [48M] INFO: Thread timer (3) is idle, terminating it.
2025-03-11 06:33:58.139 AST [48M] INFO: All threads joined
2025-03-11 06:33:58.154 AST [48M] INFO: PID file emptied
2025-03-11 06:33:58.156 AST [48M] INFO: Stored 0 API sessions in the database
2025-03-11 06:33:59.770 AST [48M] INFO: ########## FTL terminated after 7h 49s  (code 1)! ##########

  [i] pihole-FTL exited with status 1

I wonder if my issue could be related to 2307 and 2316 as well

[DL6ER]

Do you have a way to reproduce this? If so, we could try attaching a debugger to see where the crash is coming from. So far, we unfortunately don't have the necessary information to trace this down to the cause of the bug.

[KatsuroKurosaki]

Sadly I am not aware what caused it, I noticed it crashed because uptime-kuma is monitoring it. I wonder if it has to do with the fact that's a pretty busy server (I think? the notch on the chart is when it went kaput): https://nc.katsunet.com/index.php/s/xY2LFF5fqSM9Qf4

Let me know anything else you need from my end to help diagnosing it