Since updating to the latest version (Core v6.4 FTL v6.5 Web interface v6.4.1), my pi-hole randomly becomes unresponsive.
Seems like FTL is crashing, because when DNS resolution stops and I run pihole status , It returns “DNS blocking is NOT enabled” and the web UI goes down.
Restarting the FTL service (service pihole-FTL restart) re-enabledsDNS blocking and web ui works again.
Trying to dig into it doesnt seem to reveal too much to me, but Im also not a pihole debug specialist
sudo journalctl -u pihole-FTL --since "1 hour ago" | grep -iE "error|fail|critical|panic"
Mar 15 19:50:27 pihole systemd[1]: pihole-FTL.service: Failed with result 'timeout'.
> lscpu | grep "Model name"
Model name: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz
> lsblk -d -o NAME,MODEL,SIZE,ROTA,TYPE
NAME MODEL SIZE ROTA TYPE
sda SanDisk SSD U110 29.8G 0 disk
> free -h
total used free shared buff/cache available
Mem: 1.9Gi 287Mi 369Mi 10Mi 1.2Gi 1.4Gi
Swap: 975Mi 0B 975Mi
What else can I provide to assist with debugging?
Thanks in advance
https://tricorder.pi-hole.net/bXtmLylS/
@Bucking_Horn sorry to tag you, just not sure if this was missed? Can you help/advise who might be able to?
Thanks
Please generate a new debug log. The previous one expired after 48h.
Ive been having similar behavior for over a month too Pihole (FTL 6.5) randomly crashing - #5
My pi-hole is locally hosted, only unbound and glances on the device, this has been running for multiple years exactly as is with no issue. The issue started after the FTL v6.5, Web v6.4.1 and Core v6.4 releases
Same here:
> pihole-FTL --config ntp.ipv4.active
true
> pihole-FTL --config ntp.ipv6.active
true
> pihole-FTL --config ntp.sync.active
true
Log https://tricorder.pi-hole.net/hjxya6k8/
When my DNS stopped serving, I ran a pihole debug but obviously it could not upload it to Tricorder. I have it saved as a text file, is there any way to securely share it with the team manually?
I fed the “offline” debug to Gemini and it came back with this. No idea if this is actually accurate or not but Im grasping at straws to fix this:
Based on the diagnostic log and your finding that there are no "killed process" or OOM entries, the issue is not a system-level memory exhaustion (OOM) event. Instead, the log explicitly identifies a Segmentation fault (SIGSEGV) within a specific thread of the FTL process
The Root Cause: Civetweb Segmentation Fault
The diagnostic log contains a crash report from April 11, 20:45:03
Thread Name: civetweb-worker
Error: Received signal: Segmentation fault at address: 0
Context: This is a null pointer dereference occurring inside the integrated web server/API component of FTL v6
Because this is a internal crash within the application code, it will not appear as a "killed process" in dmesg (which usually tracks kernel-level kills). FTL is catching its own crash and attempting to shut down gracefully
Anant
April 12, 2026, 6:51am
9
What hardware are you running the Pihole on? Raspberry Pi or similar or a laptop or a home server?
Its an older mini pc home server. Intel Atom with 2GB RAM
It drives me crazy, stops responding multiple times per day to the point where my wife said last night “Can we just get rid of this damn thing already”
Apologies for missing your debug token.
I've split your posts back to your original topic, since your observation of a SIGSEGV crash is different from nanosleep loops.
For a temporary change of your Pi-hole machine's DNS servers:
sudo nano /etc/resolv.conf
and edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit
You may want to consider configuring your Pi-hole machine's OS to use a public DNS server in addition to or instead of Pi-hole, so the system would still be able to download OS updates or running Pi-hole's repair and debug scripts if Pi-hole would be inoperational.
Your most recent debug log doesn't contain any SIGSEGV messages.
Would you be able to locate respective lines in /var/log/pihole/FTL.log (or perhaps /var/log/pihole/webserver.log)?
Thanks - I guess thats useful for next time.
I assume theres no secure way to share the log I manually saved?
Running the debug after an FTL restart never shows anything untoward, so Its kinda useless unfortunately.
Heres a bit of a dump from the logs:
> sudo zgrep -B 50 "Segmentation fault" /var/log/pihole/FTL.log*
/var/log/pihole/FTL.log-2026-04-12 03:38:18.076 IDT [158324/T158328] INFO: Gravity database has been updated, reloading now
/var/log/pihole/FTL.log-2026-04-12 03:38:18.409 IDT [158324/T158328] INFO: Compiled 24 allow and 3 deny regex for 37 clients in 314.5 msec
/var/log/pihole/FTL.log-2026-04-12 07:18:21.614 IDT [158324/T158329] WARNING: Long-term load (15min avg) larger than number of processors: 4.2 > 4
/var/log/pihole/FTL.log-2026-04-12 07:23:21.622 IDT [158324/T158329] WARNING: Long-term load (15min avg) larger than number of processors: 4.9 > 4
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: FTL has been running for 46396 seconds
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: FTL branch: master
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: FTL version: v6.6
/var/log/pihole/FTL.log-2026-04-12 10:11:36.973 IDT [158324/T158350] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log-2026-04-12 10:11:36.974 IDT [158324/T158350] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log-2026-04-12 10:11:36.986 IDT [158324/T158350] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log-2026-04-12 10:11:36.986 IDT [158324/T158350] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log-2026-04-12 10:11:36.990 IDT [158324/T158350] INFO: Process details: MID: 158324
/var/log/pihole/FTL.log-2026-04-12 10:11:36.990 IDT [158324/T158350] INFO: PID: 158324
/var/log/pihole/FTL.log-2026-04-12 10:11:36.990 IDT [158324/T158350] INFO: TID: 158350
/var/log/pihole/FTL.log-2026-04-12 10:11:36.990 IDT [158324/T158350] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log:2026-04-12 10:11:36.990 IDT [158324/T158350] INFO: Received signal: Segmentation fault
/var/log/pihole/FTL.log.1-2026-04-11 18:04:42.840 IDT [141637/T141645] ERROR: TLS certificate at /etc/pihole/tls.pem is about to expire soon, but it is not a Pi-hole certificate. Please renew it manually!
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: FTL has been running for 96024 seconds
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: FTL branch: master
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.333 IDT [141637/T141727] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Process details: MID: 141637
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: PID: 141637
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: TID: 141727
/var/log/pihole/FTL.log.1-2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.1:2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Received signal: Segmentation fault
--
/var/log/pihole/FTL.log.1-2026-04-11 20:53:24.252 IDT [157998/T158003] INFO: 100000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:24.461 IDT [157998/T158003] INFO: 110000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:24.678 IDT [157998/T158003] INFO: 120000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:24.899 IDT [157998/T158003] INFO: 130000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:25.116 IDT [157998/T158003] INFO: 140000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:25.332 IDT [157998/T158003] INFO: 150000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:25.547 IDT [157998/T158003] INFO: 160000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:25.762 IDT [157998/T158003] INFO: 170000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:25.974 IDT [157998/T158003] INFO: 180000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:26.198 IDT [157998/T158003] INFO: 190000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:26.413 IDT [157998/T158003] INFO: 200000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:26.629 IDT [157998/T158003] INFO: 210000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:26.843 IDT [157998/T158003] INFO: 220000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:27.051 IDT [157998/T158003] INFO: 230000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:27.282 IDT [157998/T158003] INFO: 240000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:27.513 IDT [157998/T158003] INFO: 250000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:27.725 IDT [157998/T158003] INFO: 260000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:27.945 IDT [157998/T158003] INFO: 270000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:28.154 IDT [157998/T158003] INFO: 280000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:28.383 IDT [157998/T158003] INFO: 290000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:28.623 IDT [157998/T158003] INFO: 300000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:28.838 IDT [157998/T158003] INFO: 310000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.070 IDT [157998/T158003] INFO: 320000 queries parsed...
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: Imported 326136 queries from the long-term database
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Total DNS queries: 326483
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Cached DNS queries: 297060
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Forwarded DNS queries: 18630
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Blocked DNS queries: 9607
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Unknown DNS queries: 23
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Unique domains: 1941
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.219 IDT [157998/T158003] INFO: -> Unique clients: 37
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.220 IDT [157998/T158003] INFO: -> DNS cache records: 964
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.220 IDT [157998/T158003] INFO: -> Known forward destinations: 3
/var/log/pihole/FTL.log.1-2026-04-11 20:53:29.552 IDT [157998/T158003] INFO: Compiled 24 allow and 3 deny regex for 37 clients in 326.8 msec
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: FTL has been running for 1523 seconds
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: FTL branch: master
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.296 IDT [157998/T158053] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: Process details: MID: 157998
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: PID: 157998
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: TID: 158053
/var/log/pihole/FTL.log.1-2026-04-11 21:18:13.297 IDT [157998/T158053] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.1:2026-04-11 21:18:13.298 IDT [157998/T158053] INFO: Received signal: Segmentation fault
/var/log/pihole/FTL.log.2.gz-2026-04-10 05:00:02.250 IDT [107367/T107373] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
/var/log/pihole/FTL.log.2.gz-2026-04-10 05:00:02.250 IDT [107367/T107373] INFO: Tried to resolve PTR "245.0.168.192.in-addr.arpa" on 127.0.0.1#53 (UDP)
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.531 IDT [107367/T107531] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T107531] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T107531] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T107531] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T107531] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T113653] INFO: FTL has been running for 28615 seconds
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.532 IDT [107367/T107531] INFO: FTL has been running for 28615 seconds
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T107531] INFO: FTL branch: master
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T113653] INFO: FTL branch: master
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T107531] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T107531] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T113653] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T113653] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.533 IDT [107367/T107531] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: Process details: MID: 107367
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: Process details: MID: 107367
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: PID: 107367
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: PID: 107367
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: TID: 107531
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: TID: 113653
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.2.gz:2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: Received signal: Segmentation fault
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:40:46.534 IDT [107367/T107531] INFO: at address: 0
/var/log/pihole/FTL.log.2.gz:2026-04-10 07:40:46.534 IDT [107367/T113653] INFO: Received signal: Segmentation fault
--
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:54.568 IDT [138238/T138244] INFO: 150000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:54.785 IDT [138238/T138244] INFO: 160000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:55.022 IDT [138238/T138244] INFO: 170000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:55.242 IDT [138238/T138244] INFO: 180000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:55.488 IDT [138238/T138244] INFO: 190000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:55.704 IDT [138238/T138244] INFO: 200000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:55.953 IDT [138238/T138244] INFO: 210000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:56.177 IDT [138238/T138244] INFO: 220000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:56.408 IDT [138238/T138244] INFO: 230000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:56.624 IDT [138238/T138244] INFO: 240000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:56.852 IDT [138238/T138244] INFO: 250000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:57.082 IDT [138238/T138244] INFO: 260000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:57.296 IDT [138238/T138244] INFO: 270000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:57.517 IDT [138238/T138244] INFO: 280000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:57.735 IDT [138238/T138244] INFO: 290000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:57.950 IDT [138238/T138244] INFO: 300000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:58.167 IDT [138238/T138244] INFO: 310000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:58.383 IDT [138238/T138244] INFO: 320000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:58.602 IDT [138238/T138244] INFO: 330000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:58.818 IDT [138238/T138244] INFO: 340000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.038 IDT [138238/T138244] INFO: 350000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.247 IDT [138238/T138244] INFO: Imported 358204 queries from the long-term database
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.247 IDT [138238/T138244] INFO: -> Total DNS queries: 358530
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.247 IDT [138238/T138244] INFO: -> Cached DNS queries: 316497
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.247 IDT [138238/T138244] INFO: -> Forwarded DNS queries: 26106
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.247 IDT [138238/T138244] INFO: -> Blocked DNS queries: 14328
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.248 IDT [138238/T138244] INFO: -> Unknown DNS queries: 69
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.248 IDT [138238/T138244] INFO: -> Unique domains: 3239
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.248 IDT [138238/T138244] INFO: -> Unique clients: 40
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.248 IDT [138238/T138244] INFO: -> DNS cache records: 1868
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.248 IDT [138238/T138244] INFO: -> Known forward destinations: 3
/var/log/pihole/FTL.log.2.gz-2026-04-10 07:41:59.614 IDT [138238/T138244] INFO: Compiled 24 allow and 3 deny regex for 40 clients in 358.3 msec
/var/log/pihole/FTL.log.2.gz-2026-04-10 08:40:59.914 IDT [138238/T138246] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
/var/log/pihole/FTL.log.2.gz-2026-04-10 08:40:59.914 IDT [138238/T138246] INFO: Tried to resolve PTR "62.0.168.192.in-addr.arpa" on 127.0.0.1#53 (UDP)
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.860 IDT [138238/T138252] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.860 IDT [138238/T138252] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.860 IDT [138238/T138252] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.860 IDT [138238/T138252] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.860 IDT [138238/T138252] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL has been running for 20639 seconds
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL branch: master
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: Process details: MID: 138238
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: PID: 138238
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.861 IDT [138238/T138252] INFO: TID: 138252
/var/log/pihole/FTL.log.2.gz-2026-04-10 13:25:11.862 IDT [138238/T138252] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.2.gz:2026-04-10 13:25:11.862 IDT [138238/T138252] INFO: Received signal: Segmentation fault
--
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:21.650 IDT [140250/T140253] INFO: 120000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:21.871 IDT [140250/T140253] INFO: 130000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:22.090 IDT [140250/T140253] INFO: 140000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:22.309 IDT [140250/T140253] INFO: 150000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:22.529 IDT [140250/T140253] INFO: 160000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:22.739 IDT [140250/T140253] INFO: 170000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:22.964 IDT [140250/T140253] INFO: 180000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:23.176 IDT [140250/T140253] INFO: 190000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:23.397 IDT [140250/T140253] INFO: 200000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:23.614 IDT [140250/T140253] INFO: 210000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:23.825 IDT [140250/T140253] INFO: 220000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:24.038 IDT [140250/T140253] INFO: 230000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:24.252 IDT [140250/T140253] INFO: 240000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:24.480 IDT [140250/T140253] INFO: 250000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:24.701 IDT [140250/T140253] INFO: 260000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:24.920 IDT [140250/T140253] INFO: 270000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:25.149 IDT [140250/T140253] INFO: 280000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:25.379 IDT [140250/T140253] INFO: 290000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:25.602 IDT [140250/T140253] INFO: 300000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:25.826 IDT [140250/T140253] INFO: 310000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.054 IDT [140250/T140253] INFO: 320000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.277 IDT [140250/T140253] INFO: 330000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.502 IDT [140250/T140253] INFO: 340000 queries parsed...
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: Imported 344320 queries from the long-term database
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Total DNS queries: 344655
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Cached DNS queries: 303282
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Forwarded DNS queries: 25071
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Blocked DNS queries: 14842
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Unknown DNS queries: 51
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.600 IDT [140250/T140253] INFO: -> Unique domains: 2952
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.601 IDT [140250/T140253] INFO: -> Unique clients: 41
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.601 IDT [140250/T140253] INFO: -> DNS cache records: 1776
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.601 IDT [140250/T140253] INFO: -> Known forward destinations: 3
/var/log/pihole/FTL.log.2.gz-2026-04-10 14:19:26.961 IDT [140250/T140253] INFO: Compiled 24 allow and 3 deny regex for 41 clients in 355.0 msec
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.062 IDT [140250/T140271] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.062 IDT [140250/T140271] INFO: ----------------------------> FTL crashed! <----------------------------
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: and include in your report already the following details:
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL has been running for 13200 seconds
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL branch: master
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL version: v6.6
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL commit: 71b6fc62
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL date: 2026-04-03 17:41:59 +0100
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.063 IDT [140250/T140271] INFO: FTL user: started as pihole, ended as pihole
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 15.2.0) 15.2.0
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: Process details: MID: 140250
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: PID: 140250
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: TID: 140271
/var/log/pihole/FTL.log.2.gz-2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: Name: civetweb-worker
/var/log/pihole/FTL.log.2.gz:2026-04-10 17:58:47.064 IDT [140250/T140271] INFO: Received signal: Segmentation fault
There is.
You can share your file via
cat </here/my/file.log> | pihole tricorder
(substitute with your actual file as appropriate)
But the debug log would contain only some 20 lines off the head and tail of log files.
To analyse your crash, it would be more helpful to see the lines immediately preceeding and following the crash.
The following grep may help to extract the relevant section, but may need to be individually adjusted (e.g. for lines before (60) and after (6)):
sudo grep -A6 -B60 'Please also include some lines' /var/log/pihole/FTL.log.1 > ~/crash.log
Inspect crash.log in your home directory:--> FTL crashed! <-- entry, please upload and provide the token.
I tweaked it a little by making -A20, let me know if this is good for you
heres the log:
https://tricorder.pi-hole.net/0f1Cwadm/
Thank you!
Indeed, you have caught multiple crashes with identical backtraces like:
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Process details: MID: 141637
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: PID: 141637
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: TID: 141727
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Name: civetweb-worker
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: Received signal: Segmentation fault
2026-04-11 20:45:03.334 IDT [141637/T141727] INFO: at address: 0
2026-04-11 20:45:03.335 IDT [141637/T141727] INFO: with code: Unknown (128)
2026-04-11 20:45:03.340 IDT [141637/T141727] INFO: Backtrace (4 frames):
2026-04-11 20:45:03.443 IDT [141637/T141727] INFO: #0 generate_backtrace src/signals.c:259
2026-04-11 20:45:03.526 IDT [141637/T141727] INFO: #1 signal_handler src/signals.c:397
2026-04-11 20:45:03.662 IDT [141637/T141727] INFO: #2 __libc_current_sigrtmin /home/buildozer/aports/main/musl/src/musl-1.2.5/src/signal/x86_64/restore.s:1
2026-04-11 20:45:03.776 IDT [141637/T141727] INFO: #3 __libc_free /home/buildozer/aports/main/musl/src/musl-1.2.5/src/malloc/mallocng/free.c:134
@DL6ER , could you take a look here, please?
Gemini was telling me that the crash its likely due to low powered hardware and a large blocklist? Is there anything to that or just typical AI nonsense?
I am now using forceDisk=true as I tried to reduce HW load as an early troubleshooting step (Even though it ran fine in earlier versions without this so IDK if even necessary)
I don't think performance is an issue for your system, even with a blocklist ~3M strong:
The civetworker thread is related to Pi-hole's web server, so it would seem unlikely that a large blocked domain count would affect it.
But let's wait for DL6ER 's insights.
Do we have some kind of table somewhere which shows the limits or certain hardware combined with a certain amount of blocklist entries ?
Touch wood but since I edited my host nameserver to external public DNS, I havent had an FTL crash
It would seem @DL6ER is busy tracking down similar issues reported at GitHub.
A similar crash involving civetweb-worker threads is being investigated in v6.5: Crash due to segmentation fault · Issue #2783 · pi-hole/FTL · GitHub .
A potential fix is currently tested for FTL's development branch,
Another similar issue would require checking out a specific branch, see FTL crash Segmentation fault · Issue #2786 · pi-hole/FTL · GitHub .
