Pihole FTL fails because of a segmentation fault

Help
1

Expected Behaviour:

Running the command pihole enable should enable my pi-hole.

Actual Behaviour:

Running the command pihole enable has this as the output

/opt/pihole/api.sh: line 25: utilsfile: readonly variable
Communication error. Is FTL running?

Environment

  • Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 16GBRAM

  • Ubuntu 24.04.2 LTS

  • Not using Docker

  • Running pihole up gives the following output:

      [✓] Update local cache of available packages
  [✓] Building dependency package pihole-meta.deb
  [✓] Installing Pi-hole dependency package

  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] Web Interface:    up to date
  [i] FTL:              up to date

  [✓] Everything is up to date!

  • The following output has also been seen:

    root@hostname:/etc/pihole# pihole-FTL verify
[✓] Binary integrity check: OK
root@hostname:/etc/pihole# pihole-FTL
Segmentation fault (core dumped)

  • TCP ports 80 and 443 are being used by apache, but Pi-hole binds to different ports anyway, so I don't think this is an issue.

  • This PC also has Plex and MariaDB installed, but I don't think that makes this a non-standard setup.

  • I see that pihole-FTL.service failed to start with the result 'core-dump' which sounded frightening.

  • I also see that the log file tells you more about my hardware than I told you! Anyway, I looked through it and nothing stood out to me as the cause of the problem.

Debug Token:

/var/log/pihole/ihole_debug.log

2

Is there any crash logged to /var/log/pihole/FTL.log?

3

I got the same issue but FTL service continuously crash

2025-05-31 12:40:31.323 -03 [1850M] INFO: Compiled for linux/arm/v6 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 12:40:31.323 -03 [1850M] INFO: Process details: MID: 1850
2025-05-31 12:40:31.323 -03 [1850M] INFO:                  PID: 1850
2025-05-31 12:40:31.323 -03 [1850M] INFO:                  TID: 1850
2025-05-31 12:40:31.324 -03 [1850M] INFO:                  Name: pihole-FTL
2025-05-31 12:40:31.324 -03 [1850M] INFO: Received signal: Segmentation fault
2025-05-31 12:40:31.324 -03 [1850M] INFO:      at address: 0xb6f2969b
2025-05-31 12:40:31.325 -03 [1850M] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-05-31 12:40:31.325 -03 [1850M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
4

Same issue:

2025-05-31 15:59:06.903 UTC [419M] INFO: FTL version: v6.2
2025-05-31 15:59:06.903 UTC [419M] INFO: FTL commit: d7ec012f
2025-05-31 15:59:06.903 UTC [419M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-05-31 15:59:06.904 UTC [419M] INFO: FTL user: started as pihole, ended as pihole
2025-05-31 15:59:06.904 UTC [419M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 15:59:06.904 UTC [419M] INFO: Process details: MID: 419
2025-05-31 15:59:06.904 UTC [419M] INFO:                  PID: 419
2025-05-31 15:59:06.904 UTC [419M] INFO:                  TID: 419
2025-05-31 15:59:06.904 UTC [419M] INFO:                  Name: pihole-FTL
2025-05-31 15:59:06.904 UTC [419M] INFO: Received signal: Segmentation fault
2025-05-31 15:59:06.904 UTC [419M] INFO:      at address: 0x7ea649f5f22b
2025-05-31 15:59:06.904 UTC [419M] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
5

Those are just partial logs.
A crash log would start with an explicit FTL crashed!, and we'd need a few lines before that for analysing your crash.

Could you please extract the full crash log lines and share them?

To help with that, the start of a crash can be found by running

sudo grep -n 'FTL crashed!' /var/log/pihole/FTL.log*

That should find any crash occurrences and list them with their file and line number.

1 Like
6 
/var/log/pihole/FTL.log:114668:2025-05-31 10:25:59.954 -03 [15501M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:114747:2025-05-31 10:26:16.765 -03 [15520M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:114826:2025-05-31 10:26:33.730 -03 [15539M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:114905:2025-05-31 10:26:50.344 -03 [15558M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:114984:2025-05-31 10:27:07.142 -03 [15577M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115063:2025-05-31 10:27:24.004 -03 [15596M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115142:2025-05-31 10:27:40.713 -03 [15615M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115221:2025-05-31 10:27:57.458 -03 [15634M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115300:2025-05-31 10:28:13.973 -03 [15654M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115379:2025-05-31 10:28:30.533 -03 [15673M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115458:2025-05-31 10:28:47.395 -03 [15692M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115537:2025-05-31 10:29:04.057 -03 [15711M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115616:2025-05-31 10:29:20.831 -03 [15730M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115695:2025-05-31 10:29:37.577 -03 [15749M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115774:2025-05-31 10:29:54.411 -03 [15768M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115853:2025-05-31 10:30:11.177 -03 [15787M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:115932:2025-05-31 10:30:27.790 -03 [15809M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116011:2025-05-31 10:30:44.631 -03 [15828M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116090:2025-05-31 10:31:01.528 -03 [15847M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116169:2025-05-31 10:31:18.592 -03 [15867M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116248:2025-05-31 10:31:35.211 -03 [15886M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116327:2025-05-31 10:31:51.862 -03 [15905M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116406:2025-05-31 10:32:08.675 -03 [15924M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116485:2025-05-31 10:32:25.447 -03 [15943M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116564:2025-05-31 10:32:42.320 -03 [15962M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116643:2025-05-31 10:32:59.399 -03 [15981M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116722:2025-05-31 10:33:16.222 -03 [16001M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116801:2025-05-31 10:33:32.688 -03 [16020M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116880:2025-05-31 10:33:49.535 -03 [16039M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:116959:2025-05-31 10:34:06.284 -03 [16065M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117038:2025-05-31 10:34:23.098 -03 [16084M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117117:2025-05-31 10:34:39.829 -03 [16103M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117196:2025-05-31 10:34:56.915 -03 [16122M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117275:2025-05-31 10:35:13.429 -03 [16144M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117354:2025-05-31 10:35:29.952 -03 [16163M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117433:2025-05-31 10:35:46.435 -03 [16182M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117512:2025-05-31 10:36:03.040 -03 [16201M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117591:2025-05-31 10:36:19.898 -03 [16220M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117670:2025-05-31 10:36:36.533 -03 [16240M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117749:2025-05-31 10:36:53.601 -03 [16259M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117828:2025-05-31 10:37:10.153 -03 [16278M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117907:2025-05-31 10:37:26.881 -03 [16297M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:117986:2025-05-31 10:37:43.637 -03 [16316M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118065:2025-05-31 10:38:00.422 -03 [16335M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118144:2025-05-31 10:38:17.100 -03 [16355M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118223:2025-05-31 10:38:33.717 -03 [16374M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118302:2025-05-31 10:38:50.162 -03 [16393M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118381:2025-05-31 10:39:06.933 -03 [16412M] INFO: ---------------------------->  FTL crashed!  <----------------------------
/var/log/pihole/FTL.log:118460:2025-05-31 10:39:23.972 -03 [16475M] INFO: ---------------------------->  FTL crashed!  <----------------------------
7

This lines repeat forever

2025-05-31 13:46:14.589 -03 [7085M] INFO: ########## FTL started on rpi! ##########
2025-05-31 13:46:14.593 -03 [7085M] INFO: FTL branch: master
2025-05-31 13:46:14.593 -03 [7085M] INFO: FTL version: v6.2
2025-05-31 13:46:14.594 -03 [7085M] INFO: FTL commit: d7ec012f
2025-05-31 13:46:14.595 -03 [7085M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-05-31 13:46:14.595 -03 [7085M] INFO: FTL user: pihole
2025-05-31 13:46:14.596 -03 [7085M] INFO: Compiled for linux/arm/v6 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 13:46:14.648 -03 [7085M] INFO: Wrote config file:
2025-05-31 13:46:14.651 -03 [7085M] INFO:  - 155 total entries
2025-05-31 13:46:14.653 -03 [7085M] INFO:  - 143 entries are default
2025-05-31 13:46:14.655 -03 [7085M] INFO:  - 12 entries are modified
2025-05-31 13:46:14.656 -03 [7085M] INFO:  - 0 entries are forced through environment
2025-05-31 13:46:14.673 -03 [7085M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-05-31 13:46:14.676 -03 [7085M] INFO: PID file does not exist or not readable
2025-05-31 13:46:14.677 -03 [7085M] INFO: No other running FTL process found.
2025-05-31 13:46:14.711 -03 [7085M] INFO: PID of FTL process: 7085
2025-05-31 13:46:14.720 -03 [7085M] INFO: listening on 0.0.0.0 port 53
2025-05-31 13:46:14.723 -03 [7085M] INFO: listening on :: port 53
2025-05-31 13:46:14.731 -03 [7085M] INFO: PID of FTL process: 7085
2025-05-31 13:46:14.747 -03 [7085M] INFO: Database version is 21
2025-05-31 13:46:14.754 -03 [7085M] INFO: Database successfully initialized
2025-05-31 13:46:20.045 -03 [7085M] INFO: Imported 14286 queries from the on-disk database (it has 2410419 rows)
2025-05-31 13:46:20.046 -03 [7085M] INFO: Parsing queries in database
2025-05-31 13:46:21.269 -03 [7085M] INFO:   10000 queries parsed...
2025-05-31 13:46:21.767 -03 [7085M] INFO: Imported 14286 queries from the long-term database
2025-05-31 13:46:21.770 -03 [7085M] INFO:  -> Total DNS queries: 14286
2025-05-31 13:46:21.772 -03 [7085M] INFO:  -> Cached DNS queries: 9367
2025-05-31 13:46:21.773 -03 [7085M] INFO:  -> Forwarded DNS queries: 4266
2025-05-31 13:46:21.773 -03 [7085M] INFO:  -> Blocked DNS queries: 515
2025-05-31 13:46:21.773 -03 [7085M] INFO:  -> Unknown DNS queries: 0
2025-05-31 13:46:21.773 -03 [7085M] INFO:  -> Unique domains: 502
2025-05-31 13:46:21.774 -03 [7085M] INFO:  -> Unique clients: 6
2025-05-31 13:46:21.774 -03 [7085M] INFO:  -> DNS cache records: 54
2025-05-31 13:46:21.774 -03 [7085M] INFO:  -> Known forward destinations: 6
2025-05-31 13:46:23.405 -03 [7085M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-05-31 13:46:23.408 -03 [7085M] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-05-31 13:46:23.408 -03 [7085M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-05-31 13:46:23.408 -03 [7085M] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-05-31 13:46:23.408 -03 [7085M] INFO: and include in your report already the following details:
2025-05-31 13:46:23.410 -03 [7085M] INFO: FTL has been running for 9 seconds
2025-05-31 13:46:23.410 -03 [7085M] INFO: FTL branch: master
2025-05-31 13:46:23.411 -03 [7085M] INFO: FTL version: v6.2
2025-05-31 13:46:23.411 -03 [7085M] INFO: FTL commit: d7ec012f
2025-05-31 13:46:23.411 -03 [7085M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-05-31 13:46:23.411 -03 [7085M] INFO: FTL user: started as pihole, ended as pihole
2025-05-31 13:46:23.412 -03 [7085M] INFO: Compiled for linux/arm/v6 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 13:46:23.412 -03 [7085M] INFO: Process details: MID: 7085
2025-05-31 13:46:23.412 -03 [7085M] INFO:                  PID: 7085
2025-05-31 13:46:23.412 -03 [7085M] INFO:                  TID: 7085
2025-05-31 13:46:23.412 -03 [7085M] INFO:                  Name: pihole-FTL
2025-05-31 13:46:23.413 -03 [7085M] INFO: Received signal: Segmentation fault
2025-05-31 13:46:23.413 -03 [7085M] INFO:      at address: 0xb6e8e5cb
2025-05-31 13:46:23.413 -03 [7085M] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-05-31 13:46:23.413 -03 [7085M] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-05-31 13:46:23.414 -03 [7085M] INFO: ------ Listing content of directory /dev/shm ------
2025-05-31 13:46:23.414 -03 [7085M] INFO: File Mode User:Group      Size  Filename
2025-05-31 13:46:23.414 -03 [7085M] INFO: rwxrwxrwx root:root       360   .
2025-05-31 13:46:23.415 -03 [7085M] INFO: rwxr-xr-x root:root         3K  ..
2025-05-31 13:46:23.416 -03 [7085M] INFO: rw------- pihole:pihole    56   FTL-7085-lock
2025-05-31 13:46:23.416 -03 [7085M] INFO: rw------- pihole:pihole   328   FTL-7085-counters
2025-05-31 13:46:23.417 -03 [7085M] INFO: rw------- pihole:pihole   136   FTL-7085-settings
2025-05-31 13:46:23.418 -03 [7085M] INFO: rw------- pihole:pihole    82K  FTL-7085-strings
2025-05-31 13:46:23.423 -03 [7085M] INFO: rw------- pihole:pihole    16K  FTL-7085-domains
2025-05-31 13:46:23.426 -03 [7085M] INFO: rw------- pihole:pihole   340K  FTL-7085-clients
2025-05-31 13:46:23.429 -03 [7085M] INFO: rw------- pihole:pihole    12K  FTL-7085-upstreams
2025-05-31 13:46:23.432 -03 [7085M] INFO: rw------- pihole:pihole     1M  FTL-7085-queries
2025-05-31 13:46:23.435 -03 [7085M] INFO: rw------- pihole:pihole     8K  FTL-7085-overTime
2025-05-31 13:46:23.436 -03 [7085M] INFO: rw------- pihole:pihole    20K  FTL-7085-dns-cache
2025-05-31 13:46:23.437 -03 [7085M] INFO: rw------- pihole:pihole     4K  FTL-7085-per-client-regex
2025-05-31 13:46:23.438 -03 [7085M] INFO: rw------- pihole:pihole   560K  FTL-7085-fifo-log
2025-05-31 13:46:23.442 -03 [7085M] INFO: rw------- pihole:pihole     4K  FTL-7085-clients-lookup
2025-05-31 13:46:23.443 -03 [7085M] INFO: rw------- pihole:pihole     4K  FTL-7085-domains-lookup
2025-05-31 13:46:23.444 -03 [7085M] INFO: rw------- pihole:pihole     4K  FTL-7085-dns-cache-lookup
2025-05-31 13:46:23.445 -03 [7085M] INFO: rw------- pihole:pihole   786K  FTL-7085-recycler
2025-05-31 13:46:23.445 -03 [7085M] INFO: ---------------------------------------------------
2025-05-31 13:46:23.446 -03 [7085M] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-05-31 13:46:23.446 -03 [7085M] INFO: Thank you for helping us to improve our FTL engine!
2025-05-31 13:46:23.446 -03 [7085M] INFO: PID file emptied
2025-05-31 13:46:23.543 -03 [7085M] INFO: ########## FTL terminated after 8s 954ms  (code 1)! ##########
8

I'm having the same issue. It happened when updating Pi-hole to 6.2 yesterday, at the time it said only FTL had an update, the update failed and now it's completely locked up.

My debug token: https://tricorder.pi-hole.net/lh6N1Exv/

9

Sure. I am providing three sets of FTL logs from yesterday. One thing I'd like to note is that Pi-hole was running at 90-120% CPU usage according to btop (it's a more visually appealing version of top) so I tried restarting it, and that's when I ran into all of my issues.

You may notice that there are gaps in between these logs. In the spaces between, it was pretty much the same. But I believe these three may help give you an idea of what was going on.

2025-05-31 00:44:27.049 UTC [2049M] INFO: ########## FTL terminated after 4m 10s (internal restart)! ##########
2025-05-31 00:44:27.055 UTC [2049M] INFO: ########## FTL started on yttrium! ##########
2025-05-31 00:44:27.055 UTC [2049M] INFO: FTL branch: master
2025-05-31 00:44:27.056 UTC [2049M] INFO: FTL version: v6.0.3
2025-05-31 00:44:27.056 UTC [2049M] INFO: FTL commit: 37f9a96e
2025-05-31 00:44:27.056 UTC [2049M] INFO: FTL date: 2025-02-28 09:26:27 +0000
2025-05-31 00:44:27.056 UTC [2049M] INFO: FTL user: pihole
2025-05-31 00:44:27.056 UTC [2049M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 00:44:27.061 UTC [2049M] INFO: Wrote config file:
2025-05-31 00:44:27.061 UTC [2049M] INFO: - 153 total entries
2025-05-31 00:44:27.061 UTC [2049M] INFO: - 133 entries are default
2025-05-31 00:44:27.061 UTC [2049M] INFO: - 20 entries are modified
2025-05-31 00:44:27.061 UTC [2049M] INFO: - 0 entries are forced through environment
2025-05-31 00:44:27.063 UTC [2049M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-05-31 00:44:27.063 UTC [2049M] INFO: PID file does not exist or not readable
2025-05-31 00:44:27.063 UTC [2049M] INFO: No other running FTL process found.
2025-05-31 00:44:27.066 UTC [2049M] INFO: PID of FTL process: 2049
2025-05-31 00:44:27.067 UTC [2049M] INFO: listening on 0.0.0.0 port 53
2025-05-31 00:44:27.067 UTC [2049M] INFO: listening on :: port 53
2025-05-31 00:44:27.068 UTC [2049M] INFO: PID of FTL process: 2049
2025-05-31 00:44:27.069 UTC [2049M] INFO: Database version is 21
2025-05-31 00:44:27.069 UTC [2049M] INFO: Database successfully initialized
2025-05-31 00:44:28.330 UTC [2049M] INFO: Imported 108515 queries from the on-disk database (it has 8767501 rows)
2025-05-31 00:44:28.330 UTC [2049M] INFO: Parsing queries in database
2025-05-31 00:44:28.365 UTC [2049M] INFO: 10000 queries parsed...
2025-05-31 00:44:28.405 UTC [2049M] INFO: 20000 queries parsed...
2025-05-31 00:44:28.434 UTC [2049M] INFO: 30000 queries parsed...
2025-05-31 00:44:28.466 UTC [2049M] INFO: 40000 queries parsed...
2025-05-31 00:44:28.499 UTC [2049M] INFO: 50000 queries parsed...
2025-05-31 00:44:28.526 UTC [2049M] INFO: 60000 queries parsed...
2025-05-31 00:44:28.555 UTC [2049M] INFO: 70000 queries parsed...
2025-05-31 00:44:28.586 UTC [2049M] INFO: 80000 queries parsed...
2025-05-31 00:44:28.612 UTC [2049M] INFO: 90000 queries parsed...
2025-05-31 00:44:28.640 UTC [2049M] INFO: 100000 queries parsed...
2025-05-31 00:44:28.663 UTC [2049M] INFO: Imported 108513 queries from the long-term database
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Total DNS queries: 108513
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Cached DNS queries: 62315
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Forwarded DNS queries: 22261
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Blocked DNS queries: 23085
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Unknown DNS queries: 32
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Unique domains: 2697
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Unique clients: 32
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> DNS cache records: 1195
2025-05-31 00:44:28.663 UTC [2049M] INFO: -> Known forward destinations: 5
2025-05-31 00:44:28.852 UTC [2049M] INFO: FTL is running as user pihole (UID 997)
2025-05-31 00:44:28.853 UTC [2049M] INFO: Reading certificate from /etc/pihole/yttrium.combined.pem ...
2025-05-31 00:44:28.853 UTC [2049M] WARNING: SSL/TLS certificate /etc/pihole/yttrium.combined.pem does not match domain pi.hole!
2025-05-31 00:44:28.853 UTC [2049M] INFO: Using SSL/TLS certificate file /etc/pihole/yttrium.combined.pem
2025-05-31 00:44:28.854 UTC [2049M] INFO: Web server ports:
2025-05-31 00:44:28.854 UTC [2049M] INFO: - 0.0.0.0:8080 (HTTP, IPv4, optional)
2025-05-31 00:44:28.854 UTC [2049M] INFO: - 0.0.0.0:8443 (HTTPS, IPv4, optional)
2025-05-31 00:44:28.854 UTC [2049M] INFO: - [::]:8080 (HTTP, IPv6, optional)
2025-05-31 00:44:28.854 UTC [2049M] INFO: - [::]:8443 (HTTPS, IPv6, optional)
2025-05-31 00:44:28.863 UTC [2049M] INFO: Restored 2 API sessions from the database
2025-05-31 00:44:28.901 UTC [2049M] INFO: Blocking status is enabled
2025-05-31 00:44:29.017 UTC [2049/T9607] INFO: Compiled 4 allow and 13 deny regex for 32 clients in 62.4 msec
2025-05-31 00:44:34.187 UTC [2049/T9606] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-05-31 00:44:34.187 UTC [2049/T9606] INFO: Time offset: -3.734112e+00 ms (excluded 0 outliers)
2025-05-31 00:44:34.187 UTC [2049/T9606] INFO: Round-trip delay: 4.029489e+01 ms (excluded 0 outliers)
2025-05-31 00:44:34.188 UTC [2049/T9618] INFO: NTP server listening on 0.0.0.0:123 (IPv4)
2025-05-31 00:44:34.188 UTC [2049/T9619] INFO: NTP server listening on :::123 (IPv6)
2025-05-31 00:47:07.185 UTC [2049/T9637] WARNING: API: The provided IPv4 address is invalid (key: bad_request, hint: 43d4:f5::473c::)
2025-05-31 00:47:07.185 UTC [2049/T9644] WARNING: API: The provided IPv4 address is invalid (key: bad_request, hint: 1748654929)
2025-05-31 00:49:00.690 UTC [2049/T9644] INFO: Restarting FTL: API action request
2025-05-31 00:58:49.619 UTC [10078M] INFO: ########## FTL started on yttrium! ##########
2025-05-31 00:58:49.619 UTC [10078M] INFO: FTL branch: master
2025-05-31 00:58:49.619 UTC [10078M] INFO: FTL version: v6.0.3
2025-05-31 00:58:49.619 UTC [10078M] INFO: FTL commit: 37f9a96e
2025-05-31 00:58:49.619 UTC [10078M] INFO: FTL date: 2025-02-28 09:26:27 +0000
2025-05-31 00:58:49.619 UTC [10078M] INFO: FTL user: pihole
2025-05-31 00:58:49.619 UTC [10078M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 00:58:49.622 UTC [10078M] INFO: Wrote config file:
2025-05-31 00:58:49.622 UTC [10078M] INFO: - 153 total entries
2025-05-31 00:58:49.622 UTC [10078M] INFO: - 134 entries are default
2025-05-31 00:58:49.622 UTC [10078M] INFO: - 19 entries are modified
2025-05-31 00:58:49.622 UTC [10078M] INFO: - 0 entries are forced through environment
2025-05-31 00:58:49.624 UTC [10078M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-05-31 00:58:49.624 UTC [10078M] INFO: PID file does not exist or not readable
2025-05-31 00:58:49.624 UTC [10078M] INFO: No other running FTL process found.
2025-05-31 00:58:49.626 UTC [10078M] INFO: PID of FTL process: 10078
2025-05-31 00:58:49.626 UTC [10078M] WARNING: WARNING in dnsmasq core: ignoring invalid line in lease database, bad address: :80:39:8c39::8c:9993::9a:7d66:9c
2025-05-31 00:58:49.690 UTC [10078M] WARNING: WARNING in dnsmasq core: ignoring invalid line in lease database, bad address: 80:01:39:80:8c:39:99:8c:9a:93:66
2025-05-31 00:58:49.740 UTC [10078M] WARNING: WARNING in dnsmasq core: ignoring invalid line in lease database, bad address: holmium
2025-05-31 00:58:49.790 UTC [10078M] WARNING: WARNING in dnsmasq core: ignoring invalid line in lease database, bad address: 04:1748654244
2025-05-31 00:58:49.840 UTC [10078M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-05-31 00:58:49.840 UTC [10078M] INFO: ----------------------------> FTL crashed! <----------------------------
2025-05-31 00:58:49.840 UTC [10078M] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-05-31 00:58:49.840 UTC [10078M] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-05-31 00:58:49.840 UTC [10078M] INFO: and include in your report already the following details:
2025-05-31 00:58:49.840 UTC [10078M] INFO: FTL has been running for 0 seconds
2025-05-31 01:36:24.246 UTC [19686M] INFO: ########## FTL started on yttrium! ##########
2025-05-31 01:36:24.246 UTC [19686M] INFO: FTL branch: master
2025-05-31 01:36:24.246 UTC [19686M] INFO: FTL version: v6.2
2025-05-31 01:36:24.246 UTC [19686M] INFO: FTL commit: d7ec012f
2025-05-31 01:36:24.247 UTC [19686M] INFO: FTL date: 2025-05-30 22:56:39 +0100
2025-05-31 01:36:24.247 UTC [19686M] INFO: FTL user: pihole
2025-05-31 01:36:24.247 UTC [19686M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-05-31 01:36:24.250 UTC [19686M] INFO: Wrote config file:
2025-05-31 01:36:24.250 UTC [19686M] INFO: - 155 total entries
2025-05-31 01:36:24.250 UTC [19686M] INFO: - 134 entries are default
2025-05-31 01:36:24.250 UTC [19686M] INFO: - 21 entries are modified
2025-05-31 01:36:24.250 UTC [19686M] INFO: - 0 entries are forced through environment
2025-05-31 01:36:24.251 UTC [19686M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-05-31 01:36:24.251 UTC [19686M] INFO: PID file does not exist or not readable
2025-05-31 01:36:24.251 UTC [19686M] INFO: No other running FTL process found.
2025-05-31 01:36:24.253 UTC [19686M] INFO: PID of FTL process: 19686
2025-05-31 01:36:24.253 UTC [19686M] WARNING: dnsmasq: ignoring invalid line in lease database, bad address: :80:39:8c39::8c:9993::9a:7d66:9c
2025-05-31 01:36:24.323 UTC [19686M] WARNING: dnsmasq: ignoring invalid line in lease database, bad address: 80:01:39:80:8c:39:99:8c:9a:93:66
2025-05-31 01:36:24.381 UTC [19686M] WARNING: dnsmasq: ignoring invalid line in lease database, bad address: holmium
2025-05-31 01:36:24.439 UTC [19686M] WARNING: dnsmasq: ignoring invalid line in lease database, bad address: 04:1748654244

There's no report that FTL crashed anymore. By the time I reported the issue, I had already updated to 6.2. A few things to note, my PC is called holmium and my Pi-hole is installed on yttrium.

10

To everyone piggy-backing on this ticket because they have the same issue

A previous version of this message requested that no one post their logs to this thread, but also it sounded like I am a 10-year old.

To keep this thread clean, please try to keep your own logs out of it. If you need more assistance, I encourage you to open your own thread. If you have any information that could help other Pihole users, please include it. If you just want to respond because you have the problem, too, go ahead.

It looks like this issue is widespread, though, and at least there is a hotfix that works for some users.

1 Like
11

There's a hotfix on Github.

mv /usr/bin/pihole-FTL /usr/bin/pihole-FTL-broken
wget -O /usr/bin/pihole-FTL https://ftl.pi-hole.net/v6.1/pihole-FTL-{insert your processor architecture}
chmod 0755 /usr/bin/pihole-FTL
reboot
5 Likes
12

I hope this works for others, but installing the previous version did not resolve my issue. I did see in GH that mentioned it possibly being related to SQLite.

1 Like
13

Possibly related to the embedded sqlite3, which was recently updated.
If confirmed, this needs to be fixed inside FTL code.

2 Likes
14

I can confirm - the updated pihole-FTL does pass the spot where it had been segfaulting continually.

The hotfix listed mitigates the issue.

If I try a "pihole -up" (as the admin page suggested I had an update to v6.2.1 due for FTL) then the misbehaving binary is back in place, as is the line 393 typo for "readonly LOGFILE".

Fixing the typo on line 353 of /usr/local/bin/pihole and re-downloading the fixed pihole-FTL fixes the issue again.

Thank you all for the efforts..
-Cathal.

15

Hotfixes have been released. pihole -up will get you the updated FTL binary and the fix for the readonly errors.

2 Likes
17

Better still:

sudo pihole checkout ftl release/v6.1
1 Like
18

I have the same problem, but pihole -up did nothing. I still get the same Communication error. Is FTL running? Error.

1 Like
19

How do we undo that afterwards?

Running Pihole -up says Warning: You are using FTL from a custom branch (release/v6.1) and might be missing future releases.

pihole -v Core Version is v6.1.1 (Latest: v6.1.1) Branch is master Hash is 4d4195ed (Latest: ec892ec0) Web Version is v6.2.1 (Latest: v6.2.1) Branch is master Hash is cc1cc285 (Latest: cc1cc285) FTL Version is vDev-a331322 (Latest: null) Branch is release/v6.1 Hash is a3313229 (Latest: a3313229)

1 Like
20

Before update Pi-hole you need to return to master running:

sudo pihole checkout ftl master
2 Likes
21

thank you, but I'm still getting the same error as:

Something is going on with Pihole-FTL. I'm running it on Bookworm on a Pi 4B.