pihole crashed yesterday morning

[kennywest]

Versions
Pi-hole: 6.3
Web: 6.4
FTL: 6.4.1
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
Below FTL and pihole logs:

2026-01-18 00:08:22.175 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 00:08:22.176 CET [2141/T2146] INFO: Time offset: 2.560755e+01 ms (excluded 1 outliers)
2026-01-18 00:08:22.177 CET [2141/T2146] INFO: Round-trip delay: 1.343897e+01 ms (excluded 1 outliers)
2026-01-18 01:08:23.373 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 01:08:23.374 CET [2141/T2146] INFO: Time offset: 2.475777e+01 ms (excluded 0 outliers)
2026-01-18 01:08:23.375 CET [2141/T2146] INFO: Round-trip delay: 3.230566e+01 ms (excluded 0 outliers)
2026-01-18 02:08:24.179 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 02:08:24.181 CET [2141/T2146] INFO: Time offset: 2.483937e+01 ms (excluded 1 outliers)
2026-01-18 02:08:24.182 CET [2141/T2146] INFO: Round-trip delay: 1.638174e+01 ms (excluded 1 outliers)
2026-01-18 03:08:25.374 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 03:08:25.375 CET [2141/T2146] INFO: Time offset: 2.679774e+01 ms (excluded 1 outliers)
2026-01-18 03:08:25.376 CET [2141/T2146] INFO: Round-trip delay: 3.387199e+01 ms (excluded 1 outliers)
2026-01-18 04:08:26.142 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 04:08:26.144 CET [2141/T2146] INFO: Time offset: 2.703646e+01 ms (excluded 1 outliers)
2026-01-18 04:08:26.144 CET [2141/T2146] INFO: Round-trip delay: 1.470375e+01 ms (excluded 1 outliers)
2026-01-18 04:14:13.111 CET [2141/T2147] INFO: Gravity database has been updated, reloading now
2026-01-18 04:14:13.235 CET [2141/T2147] INFO: Compiled 0 allow and 0 deny regex for 2 clients in 1.2 msec
2026-01-18 05:08:27.239 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 05:08:27.240 CET [2141/T2146] INFO: Time offset: 2.436260e+01 ms (excluded 1 outliers)
2026-01-18 05:08:27.241 CET [2141/T2146] INFO: Round-trip delay: 1.364865e+01 ms (excluded 1 outliers)
2026-01-18 06:08:31.745 CET [2141/T2146] ERROR: Failed to receive data from NTP server pool.ntp.org (156.106.214.52): Timeout
2026-01-18 06:08:32.817 CET [2141/T2146] INFO: Received 7/8 valid NTP replies from pool.ntp.org
2026-01-18 06:08:32.818 CET [2141/T2146] INFO: Time offset: 2.655166e+01 ms (excluded 1 outliers)
2026-01-18 06:08:32.819 CET [2141/T2146] INFO: Round-trip delay: 3.380122e+01 ms (excluded 1 outliers)
2026-01-18 07:08:29.188 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 07:08:29.193 CET [2141/T2146] INFO: Time offset: 2.734726e+01 ms (excluded 1 outliers)
2026-01-18 07:08:29.194 CET [2141/T2146] INFO: Round-trip delay: 1.756498e+01 ms (excluded 1 outliers)
2026-01-18 08:08:30.266 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 08:08:30.267 CET [2141/T2146] INFO: Time offset: 2.401672e+01 ms (excluded 1 outliers)
2026-01-18 08:08:30.268 CET [2141/T2146] INFO: Round-trip delay: 1.651437e+01 ms (excluded 1 outliers)
2026-01-18 09:08:31.258 CET [2141/T2146] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-01-18 09:08:31.263 CET [2141/T2146] INFO: Time offset: 2.644110e+01 ms (excluded 1 outliers)
2026-01-18 09:08:31.264 CET [2141/T2146] INFO: Round-trip delay: 1.621355e+01 ms (excluded 1 outliers)
2026-01-18 09:43:59.362 CET [8447/F2141] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2026-01-18 09:43:59.365 CET [8447/F2141] INFO: ---------------------------->  FTL crashed!  <----------------------------
2026-01-18 09:43:59.366 CET [8447/F2141] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2026-01-18 09:43:59.367 CET [8447/F2141] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2026-01-18 09:43:59.368 CET [8447/F2141] INFO: and include in your report already the following details:
2026-01-18 09:43:59.369 CET [8447/F2141] INFO: FTL has been running for 2245564 seconds
2026-01-18 09:43:59.369 CET [8447/F2141] INFO: FTL branch: master
2026-01-18 09:43:59.370 CET [8447/F2141] INFO: FTL version: v6.4.1
2026-01-18 09:43:59.371 CET [8447/F2141] INFO: FTL commit: 8d1add8d
2026-01-18 09:43:59.372 CET [8447/F2141] INFO: FTL date: 2025-11-27 18:02:19 +0000
2026-01-18 09:43:59.373 CET [8447/F2141] INFO: FTL user: started as pihole, ended as pihole
2026-01-18 09:43:59.374 CET [8447/F2141] INFO: Compiled for armv6l (compiled locally) using cc (Debian 12.2.0-14+deb12u1) 12.2.0
2026-01-18 09:43:59.375 CET [8447/F2141] INFO: Process details: MID: 2141
2026-01-18 09:43:59.376 CET [8447/F2141] INFO:                  PID: 8447
2026-01-18 09:43:59.376 CET [8447/F2141] INFO:                  TID: 8447
2026-01-18 09:43:59.377 CET [8447/F2141] INFO:                  Name: pihole-FTL
2026-01-18 09:43:59.378 CET [8447/F2141] INFO: Received signal: Segmentation fault
2026-01-18 09:43:59.379 CET [8447/F2141] INFO:      at address: 0x6
2026-01-18 09:43:59.380 CET [8447/F2141] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2026-01-18 09:43:59.411 CET [8447/F2141] INFO: Backtrace:
2026-01-18 09:43:59.422 CET [8447/F2141] INFO: B[0000]: /usr/bin/pihole-FTL(generate_backtrace+0x40) [0x4ab2b0]
2026-01-18 09:43:59.831 CET [8447/F2141] INFO: L[0000]: /root/FTL/src/signals.c:108
2026-01-18 09:43:59.849 CET [8447/F2141] INFO: B[0001]: /usr/bin/pihole-FTL(+0x668f0) [0x4ab8f0]
2026-01-18 09:44:00.033 CET [8447/F2141] INFO: L[0001]: /root/FTL/src/signals.c:265
2026-01-18 09:44:00.052 CET [8447/F2141] INFO: B[0002]: /lib/arm-linux-gnueabi/libc.so.6(__default_rt_sa_restorer+0) [0xb6c74940]
2026-01-18 09:44:00.053 CET [8447/F2141] INFO: B[0003]: /usr/bin/pihole-FTL(+0x3071a4) [0x74c1a4]
2026-01-18 09:44:05.545 CET [8447/F2141] INFO: L[0003]: /root/FTL/src/database/sqlite3.c:126556
2026-01-18 09:44:05.871 CET [8447/F2141] INFO: B[0004]: /usr/bin/pihole-FTL(+0x2d713c) [0x71c13c]
2026-01-18 09:44:08.923 CET [8447/F2141] INFO: L[0004]: /root/FTL/src/database/sqlite3.c:146924
2026-01-18 09:44:09.096 CET [8447/F2141] INFO: B[0005]: /usr/bin/pihole-FTL(+0x2d9d68) [0x71ed68]
2026-01-18 09:44:10.876 CET [8447/F2141] INFO: L[0005]: /root/FTL/src/database/sqlite3.c:180115
2026-01-18 09:44:10.993 CET [8447/F2141] INFO: B[0006]: /usr/bin/pihole-FTL(+0x2da8f0) [0x71f8f0]
2026-01-18 09:44:12.692 CET [8447/F2141] INFO: L[0006]: /root/FTL/src/database/sqlite3.c:146433
2026-01-18 09:44:12.899 CET [8447/F2141] INFO: B[0007]: /usr/bin/pihole-FTL(+0x2dc15c) [0x72115c]
2026-01-18 09:44:14.593 CET [8447/F2141] INFO: L[0007]: /root/FTL/src/database/sqlite3.c:145789
2026-01-18 09:44:14.701 CET [8447/F2141] INFO: B[0008]: /usr/bin/pihole-FTL(sqlite3_exec+0x7b0) [0x72fc78]
2026-01-18 09:44:16.420 CET [8447/F2141] INFO: L[0008]: /root/FTL/src/database/sqlite3.c:140175
2026-01-18 09:44:16.527 CET [8447/F2141] INFO: B[0009]: /usr/bin/pihole-FTL(+0x2dc4f0) [0x7214f0]
2026-01-18 09:44:18.158 CET [8447/F2141] INFO: L[0009]: /root/FTL/src/database/sqlite3.c:146019 (discriminator 1)
2026-01-18 09:44:18.289 CET [8447/F2141] INFO: B[0010]: /usr/bin/pihole-FTL(+0x2edc4c) [0x732c4c]
2026-01-18 09:44:19.900 CET [8447/F2141] INFO: L[0010]: /root/FTL/src/database/sqlite3.c:146093
2026-01-18 09:44:19.009 CET [8447/F2141] INFO: B[0011]: /usr/bin/pihole-FTL(+0x2edcc0) [0x732cc0]
2026-01-18 09:44:21.648 CET [8447/F2141] INFO: L[0011]: /root/FTL/src/database/sqlite3.c:146119
2026-01-18 09:44:21.753 CET [8447/F2141] INFO: B[0012]: /usr/bin/pihole-FTL(+0x2d6eb4) [0x71beb4]
2026-01-18 09:44:23.360 CET [8447/F2141] INFO: L[0012]: /root/FTL/src/database/sqlite3.c:181447
2026-01-18 09:44:23.469 CET [8447/F2141] INFO: B[0013]: /usr/bin/pihole-FTL(+0x2d9d68) [0x71ed68]
2026-01-18 09:44:25.093 CET [8447/F2141] INFO: L[0013]: /root/FTL/src/database/sqlite3.c:180115
2026-01-18 09:44:25.198 CET [8447/F2141] INFO: B[0014]: /usr/bin/pihole-FTL(+0x2da8f0) [0x71f8f0]
2026-01-18 09:44:26.724 CET [8447/F2141] INFO: L[0014]: /root/FTL/src/database/sqlite3.c:146433
2026-01-18 09:44:26.827 CET [8447/F2141] INFO: B[0015]: /usr/bin/pihole-FTL(+0x2daecc) [0x71fecc]
2026-01-18 09:44:28.556 CET [8447/F2141] INFO: L[0015]: /root/FTL/src/database/sqlite3.c:31937
2026-01-18 09:44:28.698 CET [8447/F2141] INFO: B[0016]: /usr/bin/pihole-FTL(sqlite3_prepare_v2+0x24) [0x7204a8]
2026-01-18 09:44:30.400 CET [8447/F2141] INFO: L[0016]: /root/FTL/src/database/sqlite3.c:146597
2026-01-18 09:44:30.515 CET [8447/F2141] INFO: B[0017]: /usr/bin/pihole-FTL(+0xee35c) [0x53335c]
2026-01-18 09:44:30.745 CET [8447/F2141] INFO: L[0017]: /root/FTL/src/database/gravity-db.c:130
2026-01-18 09:44:30.777 CET [8447/F2141] INFO: B[0018]: /usr/bin/pihole-FTL(+0x11a594) [0x55f594]
2026-01-18 09:44:30.946 CET [8447/F2141] INFO: L[0018]: /root/FTL/src/dnsmasq/dnsmasq.c:2157
2026-01-18 09:44:30.969 CET [8447/F2141] INFO: B[0019]: /usr/bin/pihole-FTL(main_dnsmasq+0x16b0) [0x561a48]
2026-01-18 09:44:31.145 CET [8447/F2141] INFO: L[0019]: /root/FTL/src/dnsmasq/dnsmasq.c:1307
2026-01-18 09:44:31.168 CET [8447/F2141] INFO: B[0020]: /usr/bin/pihole-FTL(main+0x2c4) [0x47bf24]
2026-01-18 09:44:31.303 CET [8447/F2141] INFO: L[0020]: /root/FTL/src/main.c:128
2026-01-18 09:44:31.319 CET [8447/F2141] INFO: B[0021]: /lib/arm-linux-gnueabi/libc.so.6(+0x1e434) [0xb6c5c434]
2026-01-18 09:44:31.320 CET [8447/F2141] INFO: B[0022]: /lib/arm-linux-gnueabi/libc.so.6(__libc_start_main+0x98) [0xb6c5c548]
2026-01-18 09:44:31.326 CET [8447/F2141] INFO: ------ Listing content of directory /dev/shm ------
2026-01-18 09:44:31.326 CET [8447/F2141] INFO: File Mode User:Group      Size  Filename
2026-01-18 09:44:31.341 CET [8447/F2141] INFO: rwxrwxrwx root:root       380   .
2026-01-18 09:44:31.342 CET [8447/F2141] INFO: rwxr-xr-x root:root         3K  ..
2026-01-18 09:44:31.344 CET [8447/F2141] INFO: rw------- pihole:pihole   786K  FTL-2139-recycler
2026-01-18 09:44:31.345 CET [8447/F2141] INFO: rw------- pihole:pihole    29K  FTL-2139-dns-cache-lookup
2026-01-18 09:44:31.347 CET [8447/F2141] INFO: rw------- pihole:pihole    25K  FTL-2139-domains-lookup
2026-01-18 09:44:31.348 CET [8447/F2141] INFO: rw------- pihole:pihole     4K  FTL-2139-clients-lookup
2026-01-18 09:44:31.350 CET [8447/F2141] INFO: rw------- pihole:pihole   560K  FTL-2139-fifo-log
2026-01-18 09:44:31.351 CET [8447/F2141] INFO: rw------- pihole:pihole     4K  FTL-2139-per-client-regex
2026-01-18 09:44:31.353 CET [8447/F2141] INFO: rw------- pihole:pihole     1M  FTL-2139-dns-cache
2026-01-18 09:44:31.354 CET [8447/F2141] INFO: rw------- pihole:pihole    12K  FTL-2139-overTime
2026-01-18 09:44:31.356 CET [8447/F2141] INFO: rw------- pihole:pihole     4M  FTL-2139-queries
2026-01-18 09:44:31.357 CET [8447/F2141] INFO: rw------- pihole:pihole    12K  FTL-2139-upstreams
2026-01-18 09:44:31.359 CET [8447/F2141] INFO: rw------- pihole:pihole   340K  FTL-2139-clients
2026-01-18 09:44:31.360 CET [8447/F2141] INFO: rw------- pihole:pihole   963K  FTL-2139-domains
2026-01-18 09:44:31.362 CET [8447/F2141] INFO: rw------- pihole:pihole   410K  FTL-2139-strings
2026-01-18 09:44:31.363 CET [8447/F2141] INFO: rw------- pihole:pihole   136   FTL-2139-settings
2026-01-18 09:44:31.365 CET [8447/F2141] INFO: rw------- pihole:pihole   344   FTL-2139-counters
2026-01-18 09:44:31.366 CET [8447/F2141] INFO: rw------- pihole:pihole    72   FTL-2139-lock
2026-01-18 09:44:31.367 CET [8447/F2141] INFO: rw-r--r-- root:root         0   .tmpfs
2026-01-18 09:44:31.368 CET [8447/F2141] INFO: ---------------------------------------------------
2026-01-18 09:44:31.369 CET [8447/F2141] INFO: Please also include some lines from above the !!!!!!!!! header.
2026-01-18 09:44:31.370 CET [8447/F2141] INFO: Thank you for helping us to improve our FTL engine!
2026-01-18 09:44:31.371 CET [8447/F2141] INFO: Asking parent pihole-FTL (PID 2141) to shut down
2026-01-18 09:44:31.371 CET [8447/F2141] INFO: FTL fork terminated!
2026-01-18 09:44:31.375 CET [2141M] INFO: Received: Real-time signal 2 (36 -> 2)
2026-01-18 09:44:31.386 CET [2141M] INFO: Asked to terminate by "/usr/bin/pihole-FTL" (PID 2141, user pihole UID 999)
2026-01-18 09:44:31.398 CET [2141/T2147] INFO: Terminating database thread
2026-01-18 09:44:31.474 CET [2141/T2150] INFO: Terminating timer thread
2026-01-18 09:44:32.086 CET [2141/T2149] INFO: Terminating resolver thread
2026-01-18 09:44:32.215 CET [2141/T2148] INFO: Terminating GC thread
2026-01-18 09:44:33.034 CET [2141M] INFO: Finished final database update
2026-01-18 09:44:33.035 CET [2141M] INFO: Waiting for threads to join
2026-01-18 09:44:33.036 CET [2141M] INFO: Thread ntp-client (4) is idle, terminating it.
2026-01-18 09:44:33.052 CET [2141M] INFO: Thread webserver (7) is idle, terminating it.
2026-01-18 09:44:33.054 CET [2141M] INFO: All threads joined
2026-01-18 09:44:33.233 CET [2141M] INFO: PID file emptied
2026-01-18 09:44:33.256 CET [2141M] INFO: Stored 1 API session in the database
2026-01-18 09:44:34.672 CET [2141M] INFO: ########## FTL terminated after 25d 23h 46m 39s  (code 1)! ##########

pihole.log

Jan 18 09:43:56 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:43:58 dnsmasq[2141]: query[A] phonedeviceverification-pa.googleapis.com from 192.168.0.172
Jan 18 09:43:58 dnsmasq[2141]: forwarded phonedeviceverification-pa.googleapis.com to 127.0.0.1#5053
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 64.233.167.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 142.251.173.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 74.125.206.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 74.125.71.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 74.125.133.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 64.233.184.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 64.233.166.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 173.194.76.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 108.177.15.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 66.102.1.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 142.250.110.95
Jan 18 09:43:58 dnsmasq[2141]: reply phonedeviceverification-pa.googleapis.com is 142.251.168.95
Jan 18 09:43:58 dnsmasq[2141]: reply is truncated
Jan 18 09:43:58 dnsmasq[8446]: query[A] phonedeviceverification-pa.googleapis.com from 192.168.0.172
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 64.233.167.95
Jan 18 09:43:58 dnsmasq[2141]: query[A] android.googleapis.com from 192.168.0.172
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 142.251.173.95
Jan 18 09:43:58 dnsmasq[2141]: cached-stale android.googleapis.com is 216.239.36.223
Jan 18 09:43:58 dnsmasq[2141]: cached-stale android.googleapis.com is 216.239.34.223
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 74.125.206.95
Jan 18 09:43:58 dnsmasq[2141]: cached-stale android.googleapis.com is 216.239.32.223
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 74.125.71.95
Jan 18 09:43:58 dnsmasq[2141]: cached-stale android.googleapis.com is 216.239.38.223
Jan 18 09:43:58 dnsmasq[2141]: forwarded android.googleapis.com to 127.0.0.1#5053
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 74.125.133.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 64.233.184.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 64.233.166.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 173.194.76.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 108.177.15.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 66.102.1.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 142.250.110.95
Jan 18 09:43:58 dnsmasq[8446]: cached phonedeviceverification-pa.googleapis.com is 142.251.168.95
Jan 18 09:43:58 dnsmasq[2141]: reply android.googleapis.com is 216.239.36.223
Jan 18 09:43:58 dnsmasq[2141]: reply android.googleapis.com is 216.239.32.223
Jan 18 09:43:58 dnsmasq[2141]: reply android.googleapis.com is 216.239.34.223
Jan 18 09:43:58 dnsmasq[2141]: reply android.googleapis.com is 216.239.38.223
Jan 18 09:43:59 dnsmasq[2141]: query[A] cryptauthenrollment.googleapis.com from 192.168.0.172
Jan 18 09:43:59 dnsmasq[2141]: forwarded cryptauthenrollment.googleapis.com to 127.0.0.1#5053
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 142.251.5.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 64.233.166.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 173.194.76.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 74.125.206.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 108.177.15.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 64.233.184.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 74.125.133.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 142.251.168.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 64.233.167.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 66.102.1.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 142.250.110.95
Jan 18 09:43:59 dnsmasq[2141]: reply cryptauthenrollment.googleapis.com is 74.125.71.95
Jan 18 09:43:59 dnsmasq[2141]: reply is truncated
Jan 18 09:43:59 dnsmasq[2141]: query[A] android.googleapis.com from 192.168.0.172
Jan 18 09:43:59 dnsmasq[2141]: cached android.googleapis.com is 216.239.36.223
Jan 18 09:43:59 dnsmasq[2141]: cached android.googleapis.com is 216.239.32.223
Jan 18 09:43:59 dnsmasq[2141]: cached android.googleapis.com is 216.239.34.223
Jan 18 09:43:59 dnsmasq[2141]: cached android.googleapis.com is 216.239.38.223
Jan 18 09:43:59 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:43:59 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:03 dnsmasq[2141]: query[A] push.prod.netflix.com from 192.168.0.172
Jan 18 09:44:03 dnsmasq[2141]: cached-stale push.prod.netflix.com is <CNAME>
Jan 18 09:44:03 dnsmasq[2141]: cached-stale push.prod.dradis.netflix.com is <CNAME>
Jan 18 09:44:03 dnsmasq[2141]: cached-stale push.prod.eu-west-1.internal.dradis.netflix.com is <CNAME>
Jan 18 09:44:03 dnsmasq[2141]: cached-stale pushy-prod-nlb3-shard2-6cb1673808d103cf.elb.eu-west-1.amazonaws.com is 3.248.133.231
Jan 18 09:44:03 dnsmasq[2141]: cached-stale pushy-prod-nlb3-shard2-6cb1673808d103cf.elb.eu-west-1.amazonaws.com is 34.253.108.152
Jan 18 09:44:03 dnsmasq[2141]: cached-stale pushy-prod-nlb3-shard2-6cb1673808d103cf.elb.eu-west-1.amazonaws.com is 18.203.189.247
Jan 18 09:44:03 dnsmasq[2141]: forwarded push.prod.netflix.com to 127.0.0.1#5053
Jan 18 09:44:03 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:03 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:03 dnsmasq[2141]: query[A] ntp.airable.io from 192.168.0.172
Jan 18 09:44:03 dnsmasq[2141]: cached-stale ntp.airable.io is 45.32.196.44
Jan 18 09:44:03 dnsmasq[2141]: forwarded ntp.airable.io to 127.0.0.1#5053
Jan 18 09:44:06 dnsmasq[2141]: reply ntp.airable.io is 45.32.196.44
Jan 18 09:44:06 dnsmasq[2141]: reply push.prod.netflix.com is <CNAME>
Jan 18 09:44:06 dnsmasq[2141]: reply push.prod.dradis.netflix.com is <CNAME>
Jan 18 09:44:06 dnsmasq[2141]: reply push.prod.eu-west-1.internal.dradis.netflix.com is <CNAME>
Jan 18 09:44:06 dnsmasq[2141]: reply pushy-prod-nlb1-shard2-1973926ccdf27c1a.elb.eu-west-1.amazonaws.com is 34.252.38.116
Jan 18 09:44:06 dnsmasq[2141]: reply pushy-prod-nlb1-shard2-1973926ccdf27c1a.elb.eu-west-1.amazonaws.com is 52.212.10.98
Jan 18 09:44:06 dnsmasq[2141]: reply pushy-prod-nlb1-shard2-1973926ccdf27c1a.elb.eu-west-1.amazonaws.com is 54.216.148.165
Jan 18 09:44:06 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:06 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:09 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:09 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:12 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:12 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:15 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:15 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:18 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:18 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:21 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:21 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:23 dnsmasq[2141]: query[A] mobile.pipe.aria.microsoft.com from 192.168.0.172
Jan 18 09:44:23 dnsmasq[2141]: gravity blocked mobile.pipe.aria.microsoft.com is 0.0.0.0
Jan 18 09:44:24 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:24 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:27 dnsmasq[2141]: query[A] mobile.pipe.aria.microsoft.com from 192.168.0.172
Jan 18 09:44:27 dnsmasq[2141]: gravity blocked mobile.pipe.aria.microsoft.com is 0.0.0.0
Jan 18 09:44:27 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:27 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:27 dnsmasq[2141]: query[A] digitalassetlinks.googleapis.com from 192.168.0.172
Jan 18 09:44:27 dnsmasq[2141]: forwarded digitalassetlinks.googleapis.com to 127.0.0.1#5053
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 66.102.1.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 64.233.184.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 142.250.110.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 74.125.71.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 64.233.166.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 142.251.5.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 142.251.168.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 64.233.167.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 74.125.133.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 173.194.76.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 142.251.173.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 74.125.206.95
Jan 18 09:44:28 dnsmasq[2141]: reply digitalassetlinks.googleapis.com is 108.177.15.95
Jan 18 09:44:28 dnsmasq[2141]: reply is truncated
Jan 18 09:44:28 dnsmasq[8478]: query[A] digitalassetlinks.googleapis.com from 192.168.0.172
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 66.102.1.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 64.233.184.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 142.250.110.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 74.125.71.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 64.233.166.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 142.251.5.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 142.251.168.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 64.233.167.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 74.125.133.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 173.194.76.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 142.251.173.95
Jan 18 09:44:28 dnsmasq[8478]: cached digitalassetlinks.googleapis.com is 74.125.206.95
Jan 18 09:44:30 dnsmasq[2141]: query[A] logs.netflix.com from 192.168.0.172
Jan 18 09:44:30 dnsmasq[2141]: gravity blocked logs.netflix.com is 0.0.0.0
Jan 18 09:44:31 dnsmasq[2141]: exiting on receipt of SIGTERM

[DL6ER]

I don't think this is because of your exotic setup but looks like an issue with the SQLite3 library itself. Have you seen this more than once? You may also want to try building from branch development which ships an upgraded version of SQLite3. The development branch is - right now - fully backwards compatible to master so you could go back at any time without any trouble.

[kennywest]

No, this happened only once ... I think. Currently it has been running fine ever since this report. Will try a development build.

[kennywest]

seems development does not want to compile on my machine

[ 22%] Built target api_docs
[ 23%] Building C object src/webserver/CMakeFiles/webserver.dir/http-common.c.o
[ 24%] Building C object src/api/CMakeFiles/api.dir/stats.c.o
[ 24%] Building C object src/webserver/CMakeFiles/webserver.dir/lua_web.c.o
[ 25%] Building C object src/webserver/CMakeFiles/webserver.dir/webserver.c.o
[ 25%] Building C object src/api/CMakeFiles/api.dir/teleporter.c.o
[ 25%] Building C object src/webserver/CMakeFiles/webserver.dir/x509.c.o
/root/FTL/src/webserver/x509.c: In function 'generate_certificate':
/root/FTL/src/webserver/x509.c:232:19: error: too few arguments to function 'mbedtls_x509write_crt_pem'
  232 |         if((ret = mbedtls_x509write_crt_pem(&ca_cert, ca_buffer, sizeof(ca_buffer))) != 0)
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /root/FTL/src/webserver/x509.c:23:
/usr/local/include/mbedtls/x509_crt.h:1196:5: note: declared here
 1196 | int mbedtls_x509write_crt_pem(mbedtls_x509write_cert *ctx, unsigned char *buf, size_t size,
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
/root/FTL/src/webserver/x509.c:294:19: error: too few arguments to function 'mbedtls_x509write_crt_pem'
  294 |         if((ret = mbedtls_x509write_crt_pem(&server_cert, cert_buffer, sizeof(cert_buffer))) != 0)
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/mbedtls/x509_crt.h:1196:5: note: declared here
 1196 | int mbedtls_x509write_crt_pem(mbedtls_x509write_cert *ctx, unsigned char *buf, size_t size,
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~
/root/FTL/src/webserver/x509.c: In function 'read_certificate':
/root/FTL/src/webserver/x509.c:445:18: error: too few arguments to function 'mbedtls_pk_parse_keyfile'
  445 |         int rc = mbedtls_pk_parse_keyfile(&key, certfile, NULL);
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/mbedtls/x509.h:17,
                 from /usr/local/include/mbedtls/x509_crt.h:16:
/usr/local/include/mbedtls/pk.h:1174:5: note: declared here
 1174 | int mbedtls_pk_parse_keyfile(mbedtls_pk_context *ctx,
      |     ^~~~~~~~~~~~~~~~~~~~~~~~
gmake[2]: *** [src/webserver/CMakeFiles/webserver.dir/build.make:118: src/webserver/CMakeFiles/webserver.dir/x509.c.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:555: src/webserver/CMakeFiles/webserver.dir/all] Error 2
gmake[1]: *** Waiting for unfinished jobs....
[ 26%] Building C object src/api/CMakeFiles/api.dir/theme.c.o
[ 26%] Built target api
gmake: *** [Makefile:136: all] Error 2

[kennywest]

hah, but wait ... do I need a newer version for libmbedtls 🤔 ?

[DL6ER]

Yes, sorry. I thought this went it before. Updated instructions can be found here: pi-hole/docs#1329

[kennywest]

Ok, managed to compile and install everything 🤞

[Kretikus]

I use the latest pihole docker image and got a similiar error:
(Docker Tag [2025.11.1] Core [v6.3] FTL [v6.4.1] Web interface [v6.4])

2026-02-14 09:22:00.260 CET [68/T113] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2026-02-14 09:22:00.260 CET [68/T113] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2026-02-14 09:22:00.261 CET [68/T113] INFO: and include in your report already the following details:
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL has been running for 346965 seconds
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL branch: master
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL version: v6.4.1
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL commit: 8d1add8d
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL date: 2025-11-27 18:02:19 +0000
2026-02-14 09:22:00.261 CET [68/T113] INFO: FTL user: started as pihole, ended as pihole
2026-02-14 09:22:00.261 CET [68/T113] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2026-02-14 09:22:00.262 CET [68/T113] INFO: Process details: MID: 68
2026-02-14 09:22:00.262 CET [68/T113] INFO:                  PID: 68
2026-02-14 09:22:00.262 CET [68/T113] INFO:                  TID: 113
2026-02-14 09:22:00.262 CET [68/T113] INFO:                  Name: database
2026-02-14 09:22:00.262 CET [68/T113] INFO: Received signal: Segmentation fault
2026-02-14 09:22:00.262 CET [68/T113] INFO:      at address: 0x207f87ed3fd8
2026-02-14 09:22:00.262 CET [68/T113] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2026-02-14 09:22:00.262 CET [68/T113] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2026-02-14 09:22:00.263 CET [68/T113] INFO: ------ Listing content of directory /dev/shm ------
2026-02-14 09:22:00.263 CET [68/T113] INFO: File Mode User:Group      Size  Filename
2026-02-14 09:22:00.263 CET [68/T113] INFO: rwxrwxrwx root:root       360   .
2026-02-14 09:22:00.263 CET [68/T113] INFO: rwxr-xr-x root:root       320   ..
2026-02-14 09:22:00.263 CET [68/T113] INFO: rw------- pihole:pihole   786K  FTL-68-recycler
2026-02-14 09:22:00.263 CET [68/T113] INFO: rw------- pihole:pihole    66K  FTL-68-dns-cache-lookup
2026-02-14 09:22:00.263 CET [68/T113] INFO: rw------- pihole:pihole    41K  FTL-68-domains-lookup
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole     4K  FTL-68-clients-lookup
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole   569K  FTL-68-fifo-log
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole     4K  FTL-68-per-client-regex
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole   983K  FTL-68-dns-cache
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole     8K  FTL-68-overTime
2026-02-14 09:22:00.264 CET [68/T113] INFO: rw------- pihole:pihole     7M  FTL-68-queries
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole    29K  FTL-68-upstreams
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   348K  FTL-68-clients
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   381K  FTL-68-domains
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   328K  FTL-68-strings
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   144   FTL-68-settings
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   344   FTL-68-counters
2026-02-14 09:22:00.265 CET [68/T113] INFO: rw------- pihole:pihole   120   FTL-68-lock
2026-02-14 09:22:00.266 CET [68/T113] INFO: ---------------------------------------------------
2026-02-14 09:22:00.266 CET [68/T113] INFO: Please also include some lines from above the !!!!!!!!! header.
2026-02-14 09:22:00.266 CET [68/T113] INFO: Thank you for helping us to improve our FTL engine!
2026-02-14 09:22:00.266 CET [68/T113] INFO: Shutting down thread...
2026-02-14 09:22:00.266 CET [68/T113] INFO: Asked to terminate by "/usr/bin/pihole-FTL no-daemon" (PID 68, user pihole UID 1000)
2026-02-14 09:22:00.338 CET [68/T116] INFO: Terminating timer thread
2026-02-14 09:22:01.125 CET [68/T115] INFO: Terminating resolver thread
2026-02-14 09:22:01.259 CET [68/T114] INFO: Terminating GC thread

Now twice within the same week.

[DL6ER]

@Kretikus Could you try the latest nightly container tag?

[Kretikus]

@DL6ER
Installed. Lets see what happens.

Docker Tag [nightly]
Core vDev (development, e929d799)
FTL vDev (development, 04e3332)
Web interface vDev (development, c39117e9

[kennywest]

@DL6ER happened again this morning:

2026-02-16 00:51:40.288 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 00:51:40.297 CET [14799/T14804] INFO: NTP time offset: 2.550956e+01 ms (excluded 1 outliers)
2026-02-16 00:51:40.298 CET [14799/T14804] INFO: NTP round-trip delay: 1.860346e+01 ms (excluded 1 outliers)
2026-02-16 01:51:41.246 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 01:51:41.256 CET [14799/T14804] INFO: NTP time offset: 2.615305e+01 ms (excluded 1 outliers)
2026-02-16 01:51:41.258 CET [14799/T14804] INFO: NTP round-trip delay: 1.883895e+01 ms (excluded 1 outliers)
2026-02-16 02:51:42.235 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 02:51:42.244 CET [14799/T14804] INFO: NTP time offset: 2.652356e+01 ms (excluded 0 outliers)
2026-02-16 02:51:42.245 CET [14799/T14804] INFO: NTP round-trip delay: 1.470023e+01 ms (excluded 0 outliers)
2026-02-16 03:51:43.195 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 03:51:43.206 CET [14799/T14804] INFO: NTP time offset: 2.628756e+01 ms (excluded 1 outliers)
2026-02-16 03:51:43.206 CET [14799/T14804] INFO: NTP round-trip delay: 1.362760e+01 ms (excluded 1 outliers)
2026-02-16 04:51:44.350 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 04:51:44.358 CET [14799/T14804] INFO: NTP time offset: 2.616457e+01 ms (excluded 1 outliers)
2026-02-16 04:51:44.359 CET [14799/T14804] INFO: NTP round-trip delay: 1.951483e+01 ms (excluded 1 outliers)
2026-02-16 05:51:46.165 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:51:51.765 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:51:57.285 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:52:02.325 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:52:07.365 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:52:12.405 CET [14799/T14804] ERROR: Failed to receive data from NTP server pool.ntp.org (45.9.2.181): Timeout
2026-02-16 05:52:12.406 CET [14799/T14804] INFO: Received 2/8 valid NTP replies from pool.ntp.org
2026-02-16 05:52:12.408 CET [14799/T14804] INFO: NTP time offset: 2.336574e+01 ms (excluded 6 outliers)
2026-02-16 05:52:12.409 CET [14799/T14804] INFO: NTP round-trip delay: 1.979923e+01 ms (excluded 6 outliers)
2026-02-16 06:51:46.263 CET [14799/T14804] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2026-02-16 06:51:46.272 CET [14799/T14804] INFO: NTP time offset: 2.844954e+01 ms (excluded 1 outliers)
2026-02-16 06:51:46.273 CET [14799/T14804] INFO: NTP round-trip delay: 1.648508e+01 ms (excluded 1 outliers)
2026-02-16 06:52:37.051 CET [14799/T14805] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2026-02-16 06:52:37.059 CET [14799/T14805] INFO: ---------------------------->  FTL crashed!  <----------------------------
2026-02-16 06:52:37.060 CET [14799/T14805] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2026-02-16 06:52:37.060 CET [14799/T14805] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2026-02-16 06:52:37.061 CET [14799/T14805] INFO: and include in your report already the following details:
2026-02-16 06:52:37.062 CET [14799/T14805] INFO: FTL has been running for 677060 seconds
2026-02-16 06:52:37.063 CET [14799/T14805] INFO: FTL branch: development
2026-02-16 06:52:37.063 CET [14799/T14805] INFO: FTL version: v6.4.1-83-gb0407dd6
2026-02-16 06:52:37.064 CET [14799/T14805] INFO: FTL commit: b0407dd6
2026-02-16 06:52:37.065 CET [14799/T14805] INFO: FTL date: 2026-01-31 11:58:47 +0100
2026-02-16 06:52:37.067 CET [14799/T14805] INFO: FTL user: started as pihole, ended as pihole
2026-02-16 06:52:37.068 CET [14799/T14805] INFO: Compiled for armv6l (compiled locally) using cc (Debian 12.2.0-14+deb12u1) 12.2.0
2026-02-16 06:52:37.069 CET [14799/T14805] INFO: Process details: MID: 14799
2026-02-16 06:52:37.069 CET [14799/T14805] INFO:                  PID: 14799
2026-02-16 06:52:37.070 CET [14799/T14805] INFO:                  TID: 14805
2026-02-16 06:52:37.071 CET [14799/T14805] INFO:                  Name: database
2026-02-16 06:52:37.072 CET [14799/T14805] INFO: Received signal: Segmentation fault
2026-02-16 06:52:37.073 CET [14799/T14805] INFO:      at address: 0x1043
2026-02-16 06:52:37.073 CET [14799/T14805] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2026-02-16 06:52:37.100 CET [14799/T14805] INFO: Backtrace:
2026-02-16 06:52:37.106 CET [14799/T14805] INFO: B[0000]: /usr/bin/pihole-FTL(generate_backtrace+0x40) [0x4a1320]
2026-02-16 06:52:37.545 CET [14799/T14805] INFO: L[0000]: /root/FTL/src/signals.c:108
2026-02-16 06:52:37.570 CET [14799/T14805] INFO: B[0001]: /usr/bin/pihole-FTL(+0x65960) [0x4a1960]
2026-02-16 06:52:37.724 CET [14799/T14805] INFO: L[0001]: /root/FTL/src/signals.c:265
2026-02-16 06:52:37.742 CET [14799/T14805] INFO: B[0002]: /lib/arm-linux-gnueabi/libc.so.6(__default_rt_sa_restorer+0) [0xb6bc4940]
2026-02-16 06:52:37.743 CET [14799/T14805] INFO: B[0003]: /usr/bin/pihole-FTL(+0x20c478) [0x648478]
2026-02-16 06:52:40.969 CET [14799/T14805] INFO: L[0003]: /root/FTL/src/database/sqlite3.c:77860
2026-02-16 06:52:41.110 CET [14799/T14805] INFO: B[0004]: /usr/bin/pihole-FTL(+0x2e2888) [0x71e888]
2026-02-16 06:52:42.862 CET [14799/T14805] INFO: L[0004]: /root/FTL/src/database/sqlite3.c:82914
2026-02-16 06:52:43.127 CET [14799/T14805] INFO: B[0005]: /usr/bin/pihole-FTL(sqlite3_step+0x35c) [0x723c70]
2026-02-16 06:52:44.853 CET [14799/T14805] INFO: L[0005]: /root/FTL/src/database/sqlite3.c:93246
2026-02-16 06:52:44.976 CET [14799/T14805] INFO: B[0006]: /usr/bin/pihole-FTL(get_number_of_queries_in_DB+0x16c) [0x53b32c]
2026-02-16 06:52:45.287 CET [14799/T14805] INFO: L[0006]: /root/FTL/src/database/query-table.c:546
2026-02-16 06:52:45.309 CET [14799/T14805] INFO: B[0007]: /usr/bin/pihole-FTL(queries_to_database+0x978) [0x53e948]
2026-02-16 06:52:45.469 CET [14799/T14805] INFO: L[0007]: /root/FTL/src/database/query-table.c:1759
2026-02-16 06:52:45.490 CET [14799/T14805] INFO: B[0008]: /usr/bin/pihole-FTL(DB_thread+0x494) [0x528058]
2026-02-16 06:52:45.637 CET [14799/T14805] INFO: L[0008]: /root/FTL/src/database/database-thread.c:115
2026-02-16 06:52:45.666 CET [14799/T14805] INFO: ------ Listing content of directory /dev/shm ------
2026-02-16 06:52:45.667 CET [14799/T14805] INFO: File Mode User:Group      Size  Filename
2026-02-16 06:52:45.685 CET [14799/T14805] INFO: rwxrwxrwx root:root       380   .
2026-02-16 06:52:45.688 CET [14799/T14805] INFO: rwxr-xr-x root:root         3K  ..
2026-02-16 06:52:45.690 CET [14799/T14805] INFO: rw------- pihole:pihole   786K  FTL-14797-recycler
2026-02-16 06:52:45.691 CET [14799/T14805] INFO: rw------- pihole:pihole    29K  FTL-14797-dns-cache-lookup
2026-02-16 06:52:45.693 CET [14799/T14805] INFO: rw------- pihole:pihole    29K  FTL-14797-domains-lookup
2026-02-16 06:52:45.694 CET [14799/T14805] INFO: rw------- pihole:pihole     4K  FTL-14797-clients-lookup
2026-02-16 06:52:45.696 CET [14799/T14805] INFO: rw------- pihole:pihole   560K  FTL-14797-fifo-log
2026-02-16 06:52:45.697 CET [14799/T14805] INFO: rw------- pihole:pihole     4K  FTL-14797-per-client-regex
2026-02-16 06:52:45.699 CET [14799/T14805] INFO: rw------- pihole:pihole   479K  FTL-14797-dns-cache
2026-02-16 06:52:45.700 CET [14799/T14805] INFO: rw------- pihole:pihole    12K  FTL-14797-overTime
2026-02-16 06:52:45.702 CET [14799/T14805] INFO: rw------- pihole:pihole     6M  FTL-14797-queries
2026-02-16 06:52:45.703 CET [14799/T14805] INFO: rw------- pihole:pihole    12K  FTL-14797-upstreams
2026-02-16 06:52:45.705 CET [14799/T14805] INFO: rw------- pihole:pihole   340K  FTL-14797-clients
2026-02-16 06:52:45.706 CET [14799/T14805] INFO: rw------- pihole:pihole   377K  FTL-14797-domains
2026-02-16 06:52:45.708 CET [14799/T14805] INFO: rw------- pihole:pihole   328K  FTL-14797-strings
2026-02-16 06:52:45.710 CET [14799/T14805] INFO: rw------- pihole:pihole   136   FTL-14797-settings
2026-02-16 06:52:45.711 CET [14799/T14805] INFO: rw------- pihole:pihole   344   FTL-14797-counters
2026-02-16 06:52:45.713 CET [14799/T14805] INFO: rw------- pihole:pihole    72   FTL-14797-lock
2026-02-16 06:52:45.714 CET [14799/T14805] INFO: rw-r--r-- root:root         0   .tmpfs
2026-02-16 06:52:45.715 CET [14799/T14805] INFO: ---------------------------------------------------
2026-02-16 06:52:45.715 CET [14799/T14805] INFO: Please also include some lines from above the !!!!!!!!! header.
2026-02-16 06:52:45.716 CET [14799/T14805] INFO: Thank you for helping us to improve our FTL engine!
2026-02-16 06:52:45.717 CET [14799/T14805] INFO: Shutting down thread...
2026-02-16 06:52:45.719 CET [14799/T14805] INFO: Asked to terminate by "/usr/bin/pihole-FTL" (PID 14799, user pihole UID 999)
2026-02-16 06:52:45.817 CET [14799/T14806] ERROR: Error when obtaining outer SHM lock: Owner died
2026-02-16 06:52:45.820 CET [14799/T14806] ERROR: Error when obtaining inner SHM lock: Owner died
2026-02-16 06:52:45.886 CET [14799/T14808] INFO: Terminating timer thread
2026-02-16 06:52:45.969 CET [14799/T14807] INFO: Terminating resolver thread
2026-02-16 06:52:46.865 CET [14799/T14806] INFO: Terminating GC thread
2026-02-16 07:51:43.103 CET [14799/T14804] INFO: Terminating NTP thread

[DL6ER]

The best I can say about this right now is that the code where the crash happened has meanwhile been removed from development (on Feb 8).

@PromoFaux how comes that they installed the nightly tag reporting

Docker Tag [nightly]
Core vDev (development, e929d799)
FTL vDev (development, https://github.com/pi-hole/FTL/commit/04e333242a9b45322915338a9dd1b0753933cc39)
Web interface vDev (development, c39117e9)

but the FTL binary running in there is two weeks old and not reflecting the tag the output claimed before?

2026-02-16 06:52:37.064 CET [14799/T14805] INFO: FTL commit: b0407dd6
2026-02-16 06:52:37.065 CET [14799/T14805] INFO: FTL date: 2026-01-31 11:58:47 +0100

[kennywest]

Ok ... pulled latest code ... rebuilding FTL

EDIT: build complete + up and running

2026-02-16 09:18:48.780 CET [27703M] INFO: ########## FTL terminated after 1h 6m 33s  (code 0)! ##########
2026-02-16 13:46:03.150 CET [30136M] INFO: ########## FTL started on pogo02! ##########
2026-02-16 13:46:03.151 CET [30136M] INFO: FTL branch: development
2026-02-16 13:46:03.151 CET [30136M] INFO: FTL version: v6.4.1-122-g04e33324
2026-02-16 13:46:03.151 CET [30136M] INFO: FTL commit: 04e33324
2026-02-16 13:46:03.152 CET [30136M] INFO: FTL date: 2026-02-14 12:49:36 +0100
2026-02-16 13:46:03.152 CET [30136M] INFO: FTL user: pihole
2026-02-16 13:46:03.152 CET [30136M] INFO: Compiled for armv6l (compiled locally) using cc (Debian 12.2.0-14+deb12u1) 12.2.0
2026-02-16 13:46:03.177 CET [30136M] INFO: Wrote config file:
2026-02-16 13:46:03.177 CET [30136M] INFO:  - 166 total entries
2026-02-16 13:46:03.177 CET [30136M] INFO:  - 151 entries are default
2026-02-16 13:46:03.178 CET [30136M] INFO:  - 15 entries are modified
2026-02-16 13:46:03.178 CET [30136M] INFO:  - 0 entries are forced through environment

[yubiuser]

how comes that they installed the nightly tag reporting

I did a fresh pull and it reports

  [i] Starting pihole-FTL (no-daemon) as pihole

  [i] Version info:
      Core
          Version is e929d79 (Latest: null)
          Branch is development
          Hash is e929d799 (Latest: e929d799)
      Web
          Version is 192d96f (Latest: null)
          Branch is development
          Hash is 192d96ff (Latest: 192d96ff)
      FTL
          Version is vDev-04e3332 (Latest: null)
          Branch is development
          Hash is 04e33324 (Latest: 04e33324)