pihole FTL crashed last night

[kennywest]

Versions

• Pi-hole: 6.1.4
• Web: 6.2.1
• FTL: 6.2.3

Platform

• OS and version: Debian 12 Bookworm (all up to date)

• Platform: Pogoplug Pro (Linux pogo02 5.15.158-oxnas-tld-2 #2 SMP PREEMPT Sun May 12 18:45:05 PDT 2024 armv6l GNU/Linux)

This is unsupported hardware, but I've managed to compile FTL myself. Have been doing this since one of the first v6 beta releases.

Expected behavior

pihole-FTL crashed and it shouldn't (unless this is because my exotic setup)

Actual behavior / bug

Found this in the logs. Please note, this is all I have in FTL.log.1 :(

root@pogo02:/var/log/pihole# cat FTL.log.1

2025-10-07 00:08:21.008 CEST [20811/F884] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-10-07 00:08:22.030 CEST [20811/F884] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-10-07 00:08:22.031 CEST [20811/F884] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-10-07 00:08:22.032 CEST [20811/F884] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-10-07 00:08:22.034 CEST [20811/F884] INFO: and include in your report already the following details:
2025-10-07 00:08:22.035 CEST [20811/F884] INFO: FTL has been running for 1746550 seconds
2025-10-07 00:08:22.037 CEST [20811/F884] INFO: FTL branch: master
2025-10-07 00:08:22.038 CEST [20811/F884] INFO: FTL version: v6.2.3
2025-10-07 00:08:22.039 CEST [20811/F884] INFO: FTL commit: 88737f62
2025-10-07 00:08:22.040 CEST [20811/F884] INFO: FTL date: 2025-06-10 20:44:58 +0200
2025-10-07 00:08:22.074 CEST [20811/F884] INFO: FTL user: started as pihole, ended as pihole
2025-10-07 00:08:22.074 CEST [20811/F884] INFO: Compiled for armv6l (compiled locally) using cc (Debian 12.2.0-14+deb12u1) 12.2.0
2025-10-07 00:08:22.075 CEST [20811/F884] INFO: Process details: MID: 884
2025-10-07 00:08:22.076 CEST [20811/F884] INFO:                  PID: 20811
2025-10-07 00:08:22.077 CEST [20811/F884] INFO:                  TID: 20811
2025-10-07 00:08:22.077 CEST [20811/F884] INFO:                  Name: pihole-FTL
2025-10-07 00:08:22.092 CEST [20811/F884] INFO: Received signal: Segmentation fault
2025-10-07 00:08:22.093 CEST [20811/F884] INFO:      at address: 0x6
2025-10-07 00:08:22.094 CEST [20811/F884] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-10-07 00:08:22.144 CEST [20811/F884] INFO: Backtrace:
2025-10-07 00:08:22.171 CEST [20811/F884] INFO: B[0000]: /usr/bin/pihole-FTL(generate_backtrace+0x40) [0x50b23c]
2025-10-07 00:08:22.911 CEST [20811/F884] INFO: L[0000]: /root/FTL/src/signals.c:107
2025-10-07 00:08:22.963 CEST [20811/F884] INFO: B[0001]: /usr/bin/pihole-FTL(+0x6287c) [0x50b87c]
2025-10-07 00:08:23.872 CEST [20811/F884] INFO: L[0001]: /root/FTL/src/signals.c:264
2025-10-07 00:08:23.936 CEST [20811/F884] INFO: B[0002]: /lib/arm-linux-gnueabi/libc.so.6(__default_rt_sa_restorer+0) [0xb6bd4940]
2025-10-07 00:08:23.942 CEST [20811/F884] INFO: B[0003]: /usr/bin/pihole-FTL(+0x2a8a0c) [0x751a0c]
2025-10-07 00:08:28.095 CEST [20811/F884] INFO: L[0003]: /root/FTL/src/database/sqlite3.c:124336
2025-10-07 00:08:28.352 CEST [20811/F884] INFO: B[0004]: /usr/bin/pihole-FTL(+0x27e49c) [0x72749c]
2025-10-07 00:08:30.356 CEST [20811/F884] INFO: L[0004]: /root/FTL/src/database/sqlite3.c:144037
2025-10-07 00:08:30.695 CEST [20811/F884] INFO: B[0005]: /usr/bin/pihole-FTL(+0x280ecc) [0x729ecc]
2025-10-07 00:08:32.408 CEST [20811/F884] INFO: L[0005]: /root/FTL/src/database/sqlite3.c:176851
2025-10-07 00:08:32.511 CEST [20811/F884] INFO: B[0006]: /usr/bin/pihole-FTL(+0x281a4c) [0x72aa4c]
2025-10-07 00:08:34.088 CEST [20811/F884] INFO: L[0006]: /root/FTL/src/database/sqlite3.c:143548
2025-10-07 00:08:34.218 CEST [20811/F884] INFO: B[0007]: /usr/bin/pihole-FTL(+0x282e9c) [0x72be9c]
2025-10-07 00:08:35.942 CEST [20811/F884] INFO: L[0007]: /root/FTL/src/database/sqlite3.c:142904
2025-10-07 00:08:36.045 CEST [20811/F884] INFO: B[0008]: /usr/bin/pihole-FTL(sqlite3_exec+0x7b0) [0x738d44]
2025-10-07 00:08:37.639 CEST [20811/F884] INFO: L[0008]: /root/FTL/src/database/sqlite3.c:137327
2025-10-07 00:08:37.749 CEST [20811/F884] INFO: B[0009]: /usr/bin/pihole-FTL(+0x28320c) [0x72c20c]
2025-10-07 00:08:39.490 CEST [20811/F884] INFO: L[0009]: /root/FTL/src/database/sqlite3.c:143134 (discriminator 1)
2025-10-07 00:08:39.643 CEST [20811/F884] INFO: B[0010]: /usr/bin/pihole-FTL(+0x292af8) [0x73baf8]
2025-10-07 00:08:41.308 CEST [20811/F884] INFO: L[0010]: /root/FTL/src/database/sqlite3.c:143208
2025-10-07 00:08:41.425 CEST [20811/F884] INFO: B[0011]: /usr/bin/pihole-FTL(+0x292b34) [0x73bb34]
2025-10-07 00:08:42.972 CEST [20811/F884] INFO: L[0011]: /root/FTL/src/database/sqlite3.c:143234
2025-10-07 00:08:43.073 CEST [20811/F884] INFO: B[0012]: /usr/bin/pihole-FTL(+0x27e210) [0x727210]
2025-10-07 00:08:44.666 CEST [20811/F884] INFO: L[0012]: /root/FTL/src/database/sqlite3.c:178181
2025-10-07 00:08:44.769 CEST [20811/F884] INFO: B[0013]: /usr/bin/pihole-FTL(+0x280ecc) [0x729ecc]
2025-10-07 00:08:46.279 CEST [20811/F884] INFO: L[0013]: /root/FTL/src/database/sqlite3.c:176851
2025-10-07 00:08:46.376 CEST [20811/F884] INFO: B[0014]: /usr/bin/pihole-FTL(+0x281a4c) [0x72aa4c]
2025-10-07 00:08:47.913 CEST [20811/F884] INFO: L[0014]: /root/FTL/src/database/sqlite3.c:143548
2025-10-07 00:08:48.019 CEST [20811/F884] INFO: B[0015]: /usr/bin/pihole-FTL(+0x282008) [0x72b008]
2025-10-07 00:08:49.705 CEST [20811/F884] INFO: L[0015]: /root/FTL/src/database/sqlite3.c:143621
2025-10-07 00:08:49.805 CEST [20811/F884] INFO: B[0016]: /usr/bin/pihole-FTL(sqlite3_prepare_v2+0x24) [0x72b5bc]
2025-10-07 00:08:51.239 CEST [20811/F884] INFO: L[0016]: /root/FTL/src/database/sqlite3.c:143710
2025-10-07 00:08:51.336 CEST [20811/F884] INFO: B[0017]: /usr/bin/pihole-FTL(+0xda504) [0x583504]
2025-10-07 00:08:51.492 CEST [20811/F884] INFO: L[0017]: /root/FTL/src/database/gravity-db.c:128
2025-10-07 00:08:51.512 CEST [20811/F884] INFO: B[0018]: /usr/bin/pihole-FTL(+0x1060a8) [0x5af0a8]
2025-10-07 00:08:51.676 CEST [20811/F884] INFO: L[0018]: /root/FTL/src/dnsmasq/dnsmasq.c:2157
2025-10-07 00:08:51.698 CEST [20811/F884] INFO: B[0019]: /usr/bin/pihole-FTL(main_dnsmasq+0x16ac) [0x5b156c]
2025-10-07 00:08:51.862 CEST [20811/F884] INFO: L[0019]: /root/FTL/src/dnsmasq/dnsmasq.c:1307
2025-10-07 00:08:51.884 CEST [20811/F884] INFO: B[0020]: /usr/bin/pihole-FTL(main+0x2b4) [0x4dfa44]
2025-10-07 00:08:52.014 CEST [20811/F884] INFO: L[0020]: /root/FTL/src/main.c:128
2025-10-07 00:08:52.030 CEST [20811/F884] INFO: B[0021]: /lib/arm-linux-gnueabi/libc.so.6(+0x1e434) [0xb6bbc434]
2025-10-07 00:08:52.031 CEST [20811/F884] INFO: B[0022]: /lib/arm-linux-gnueabi/libc.so.6(__libc_start_main+0x98) [0xb6bbc548]
2025-10-07 00:08:52.040 CEST [20811/F884] INFO: ------ Listing content of directory /dev/shm ------
2025-10-07 00:08:52.041 CEST [20811/F884] INFO: File Mode User:Group      Size  Filename
2025-10-07 00:08:52.070 CEST [20811/F884] INFO: rwxrwxrwx root:root       380   .
2025-10-07 00:08:52.072 CEST [20811/F884] INFO: rwxr-xr-x root:root         3K  ..
2025-10-07 00:08:52.073 CEST [20811/F884] INFO: rw------- pihole:pihole   786K  FTL-863-recycler
2025-10-07 00:08:52.075 CEST [20811/F884] INFO: rw------- pihole:pihole    25K  FTL-863-dns-cache-lookup
2025-10-07 00:08:52.076 CEST [20811/F884] INFO: rw------- pihole:pihole    25K  FTL-863-domains-lookup
2025-10-07 00:08:52.078 CEST [20811/F884] INFO: rw------- pihole:pihole     4K  FTL-863-clients-lookup
2025-10-07 00:08:52.081 CEST [20811/F884] INFO: rw------- pihole:pihole   560K  FTL-863-fifo-log
2025-10-07 00:08:52.082 CEST [20811/F884] INFO: rw------- pihole:pihole     4K  FTL-863-per-client-regex
2025-10-07 00:08:52.084 CEST [20811/F884] INFO: rw------- pihole:pihole   885K  FTL-863-dns-cache
2025-10-07 00:08:52.085 CEST [20811/F884] INFO: rw------- pihole:pihole    12K  FTL-863-overTime
2025-10-07 00:08:52.087 CEST [20811/F884] INFO: rw------- pihole:pihole     7M  FTL-863-queries
2025-10-07 00:08:52.088 CEST [20811/F884] INFO: rw------- pihole:pihole    12K  FTL-863-upstreams
2025-10-07 00:08:52.090 CEST [20811/F884] INFO: rw------- pihole:pihole   340K  FTL-863-clients
2025-10-07 00:08:52.091 CEST [20811/F884] INFO: rw------- pihole:pihole   680K  FTL-863-domains
2025-10-07 00:08:52.093 CEST [20811/F884] INFO: rw------- pihole:pihole   328K  FTL-863-strings
2025-10-07 00:08:52.094 CEST [20811/F884] INFO: rw------- pihole:pihole   136   FTL-863-settings
2025-10-07 00:08:52.096 CEST [20811/F884] INFO: rw------- pihole:pihole   328   FTL-863-counters
2025-10-07 00:08:52.097 CEST [20811/F884] INFO: rw------- pihole:pihole    56   FTL-863-lock
2025-10-07 00:08:52.098 CEST [20811/F884] INFO: rw-r--r-- root:root         0   .tmpfs
2025-10-07 00:08:52.099 CEST [20811/F884] INFO: ---------------------------------------------------
2025-10-07 00:08:52.101 CEST [20811/F884] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-10-07 00:08:52.102 CEST [20811/F884] INFO: Thank you for helping us to improve our FTL engine!
2025-10-07 00:08:52.103 CEST [20811/F884] INFO: Asking parent pihole-FTL (PID 884) to shut down
2025-10-07 00:08:52.104 CEST [20811/F884] INFO: FTL fork terminated!
2025-10-07 00:08:52.109 CEST [884M] INFO: Received: Real-time signal 2 (36 -> 2)
2025-10-07 00:08:52.132 CEST [884M] INFO: Asked to terminate by "/usr/bin/pihole-FTL" (PID 884, user pihole UID 999)
2025-10-07 00:08:52.224 CEST [884/T903] INFO: Terminating database thread
2025-10-07 00:08:52.255 CEST [884/T906] INFO: Terminating timer thread
2025-10-07 00:08:52.382 CEST [884/T904] INFO: Terminating GC thread
2025-10-07 00:08:53.151 CEST [884/T905] INFO: Terminating resolver thread
2025-10-07 00:08:55.781 CEST [884M] INFO: Finished final database update
2025-10-07 00:08:55.782 CEST [884M] INFO: Waiting for threads to join
2025-10-07 00:08:55.784 CEST [884M] INFO: Thread ntp-client (4) is idle, terminating it.
2025-10-07 00:08:55.805 CEST [884M] INFO: All threads joined
2025-10-07 00:08:55.980 CEST [884M] INFO: PID file emptied
2025-10-07 00:08:55.007 CEST [884M] INFO: Stored 1 API session in the database
2025-10-07 00:08:56.895 CEST [884M] INFO: ########## FTL terminated after 20d 5h 9m 47s  (code 1)! ##########

Steps to reproduce

Just left it running, nothing special.

[pralor-bot]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/crash-of-pihole-last-night/82679/3

[ETA-2026]

This issue has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/crash-of-pihole-last-night/82679/3

@pralor-bot perhaps if you'd read the linked thread, you would have realised @kennywest was told to post here!

[rdwebdesign]

@ETA-2026

@pralor-bot perhaps if you'd read the linked thread, you would have realised @kennywest was told to post here!

You are talking to a Bot, created exactly to post Discourse links here on Github.

[DL6ER]

FTL/src/database/gravity-db.c

Lines 124 to 128 in bc18568

	int rc = sqlite3_prepare_v2(gravity_db,
	"SELECT value FROM info WHERE property = 'abp_domains';",
	-1, &stmt, NULL);
	if( rc != SQLITE_OK )

It crashed here which is kind of a strange place for this to happen. Did anything noteworthy happen on that time? /var/log/pihole/FTL.log and pihole.log (in the same dir) might have some more information for us

[kennywest]

No, nothing more. Logs got rotated in the meantime :(

[DL6ER]

There should be other files in the same directory (like FTL.log.1) which contain the rotated logs.

[kennywest]

Indeed. But we are now a few days later and FTL.log.1 contains the logs of 9/10 (yesterday the logs of 8/10).

[rdwebdesign]

The log rotation moves FTL.log to FTL.log.1. It also moves .1 to .2 and so on, but some files are archived as .gz:

pihole:/var/log/pihole# ls -la FTL*
-rw-r----- 1 pihole pihole  1175 Oct 10 03:00 FTL.log
-rw-r----- 1 pihole pihole 12395 Oct 10 00:00 FTL.log.1
-rw-r----- 1 pihole pihole   799 Oct  9 00:00 FTL.log.2.gz
-rw-r----- 1 pihole pihole  1120 Oct  8 00:00 FTL.log.3.gz

You can try to find the crashed log in FTL.log.2.gz or FTL.log.3.gz using tools like zcat or zless. Or simply use less like this:

LESSOPEN='|gzip -cdfq -- %s' less FTL.log.2.gz

If you can't find the log, probably there is nothing we can do without more information and you will need to wait for the next crash.

[kennywest]

sorry, I only have this:

-rw-r----- 1 pihole pihole     1176 Oct  5 04:14 pihole_updateGravity.log
-rw-r----- 1 pihole pihole        2 Oct 10 00:00 webserver.log.1
-rw-r----- 1 pihole pihole    10807 Oct 10 23:55 FTL.log.1
-rw-r----- 1 pihole pihole 27974306 Oct 11 00:00 pihole.log.1
-rw-r----- 1 pihole pihole        2 Oct 11 00:00 webserver.log
-rw-r----- 1 pihole pihole     2756 Oct 11 08:55 FTL.log
-rw-r----- 1 pihole pihole  7506291 Oct 11 09:21 pihole.log

So I only have today and the day before. Probably a setting somewhere, can't remember.
I guess indeed there's not much we can do if we indeed require the other log files as well.

[DL6ER]

We fixed quite a few side-effects concerning the database with FTL v6.3.3 - do you still encounter such crashes?

[kennywest]

I'm still on 6.3.2. I will upgrade today or tomorrow. But if this is the case (so fixes in sqlite), I guess we can close this issue?

[DL6ER]

Let's see once you upgraded, I'd say. I do not want to close ticket too early "just to have them closed", but it could be re-opened anyway at any time.