FTL crashes on startup #2711
Description
Versions
- Pi-hole: v6.2.2
- Web: v6.3
- FTL: v6.3.3
Platform
- OS and version: Debian 12 (bookworm)
- Platform: Docker
Expected behavior
pihole works and nothing crashes
Actual behavior / bug
FTL crashes and the container restarts (restart-policy: unless-stopped)
Steps to reproduce
Steps to reproduce the behavior:
docker compose up -d
Log
pihole | 2025-11-14 15:45:19.158 CET [64M] INFO: Reading certificate from /etc/pihole/tls.pem ...
pihole | 2025-11-14 15:45:19.158 CET [64M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: Web server ports:
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
pihole | 2025-11-14 15:45:19.159 CET [64M] INFO: Restored 0 API sessions from the database
pihole | 2025-11-14 15:45:19.161 CET [64M] INFO: Blocking status is enabled
pihole | 2025-11-14 15:45:19.262 CET [64/T355] INFO: Compiled 0 allow and 0 deny regex for 52281 clients in 3.0 msec
pihole | 2025-11-14 15:45:21.160 CET [64M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: ----------------------------> FTL crashed! <----------------------------
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: and include in your report already the following details:
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL has been running for 693 seconds
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL branch: master
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL version: v6.3.3
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL commit: a0186fd4
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL date: 2025-11-04 20:18:48 +0100
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: FTL user: started as pihole, ended as pihole
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: Process details: MID: 64
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: PID: 64
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: TID: 64
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: Name: pihole-FTL
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: Received signal: Segmentation fault
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: at address: 0x10
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: with code: SEGV_MAPERR (Address not mapped to object)
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: ------ Listing content of directory /dev/shm ------
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: File Mode User:Group Size Filename
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rwxrwxrwx root:root 360 .
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rwxr-xr-x root:root 340 ..
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 786K FTL-64-recycler
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 4K FTL-64-dns-cache-lookup
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 4K FTL-64-domains-lookup
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 422K FTL-64-clients-lookup
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 569K FTL-64-fifo-log
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 4K FTL-64-per-client-regex
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 12K FTL-64-dns-cache
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 8K FTL-64-overTime
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 27M FTL-64-queries
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 29K FTL-64-upstreams
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 36M FTL-64-clients
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 4K FTL-64-domains
pihole | 2025-11-14 15:45:21.161 CET [64M] INFO: rw------- pihole:pihole 819K FTL-64-strings
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: rw------- pihole:pihole 144 FTL-64-settings
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: rw------- pihole:pihole 344 FTL-64-counters
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: rw------- pihole:pihole 88 FTL-64-lock
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: ---------------------------------------------------
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: Please also include some lines from above the !!!!!!!!! header.
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: Thank you for helping us to improve our FTL engine!
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: Waiting for threads to join
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: Thread database (0) is idle, terminating it.
pihole | 2025-11-14 15:45:21.162 CET [64M] INFO: Thread housekeeper (1) is idle, terminating it.
pihole | 2025-11-14 15:45:21.164 CET [64/T358] INFO: Terminating timer thread
pihole | 2025-11-14 15:45:23.162 CET [64M] INFO: Thread dns-client (2) is still busy, cancelling it.
pihole | 2025-11-14 15:45:23.162 CET [64/T357] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
pihole | 2025-11-14 15:45:23.162 CET [64/T357] INFO: Tried to resolve PTR "117.200.175.87.in-addr.arpa" on 127.0.0.1#53 (UDP)
pihole | /bin/bash: line 1: 64 Segmentation fault /usr/bin/pihole-FTL no-daemon > /dev/null
pihole | 2025-11-14 15:45:23.977 CET [64/T354] INFO: Received 8/8 valid NTP replies from pool.ntp.org
pihole | 2025-11-14 15:45:23.978 CET [64/T354] INFO: Time offset: 1.212358e-01 ms (excluded 0 outliers)
pihole | 2025-11-14 15:45:23.978 CET [64/T354] INFO: Round-trip delay: 1.020859e+02 ms (excluded 0 outliers)
pihole | 2025-11-14 15:45:23.978 CET [64/T354] INFO: Terminating NTP thread
pihole | 2025-11-14 15:45:23.978 CET [64M] INFO: Thread webserver (7) is idle, terminating it.
pihole | 2025-11-14 15:45:23.978 CET [64/T362] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
pihole | 2025-11-14 15:45:23.978 CET [64M] INFO: All threads joined
pihole | 2025-11-14 15:45:23.978 CET [64M] ERROR: Error when obtaining outer SHM lock: Resource deadlock would occur
pihole | 2025-11-14 15:45:23.978 CET [64M] ERROR: Error when obtaining inner SHM lock: Resource deadlock would occur
pihole |
pihole | [i] pihole-FTL exited with status 139
pihole |
pihole | [i] Container will now stop or restart depending on your restart policy
Additional context
Docker compose file:
pihole:
container_name: pihole
image: pihole/pihole:latest
ports:
# DNS Ports
- "53:53/tcp"
- "53:53/udp"
# Default HTTP Port
- "127.0.0.1:87:80/tcp"
# Default HTTPs Port. FTL will generate a self-signed certificate
# - "127.0.0.1:443/tcp"
# Uncomment the below if using Pi-hole as your DHCP Server
#- "67:67/udp"
# Uncomment the line below if you are using Pi-hole as your NTP server
#- "123:123/udp"
environment:
# Set the appropriate timezone for your location from
# https://en.wikipedia.org/wiki/List_of_tz_database_time_zones, e.g:
TZ: 'Europe/Berlin'
# Set a password to access the web interface. Not setting one will result in a random password being assigned
FTLCONF_webserver_api_password: 'thisisnottherealpassword'
# If using Docker's default `bridge` network setting the dns listening mode should be set to 'all'
FTLCONF_dns_listeningMode: 'all'
# Volumes store your data between container upgrades
volumes:
# For persisting Pi-hole's databases and common configuration file
- './etc-pihole:/etc/pihole'
# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you shoul>
#- './etc-dnsmasq.d:/etc/dnsmasq.d'
cap_add:
# See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
# Required if you are using Pi-hole as your DHCP server, else not needed
- NET_ADMIN
# Required if you are using Pi-hole as your NTP client to be able to set the host's system time
- SYS_TIME
# Optional, if Pi-hole should get some more processing time
- SYS_NICE
restart: unless-stopped
networks:
- services
networks:
services:
name: services
external: true