Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FTL crashed! #2371

Open
githubsean opened this issue Mar 13, 2025 · 6 comments
Open

FTL crashed! #2371

githubsean opened this issue Mar 13, 2025 · 6 comments
Labels
crash Waiting for feedback

Comments

@githubsean
Copy link

Versions

  • Pi-hole: 6.0.5
  • AdminLTE: 6.0.2
  • FTL: 6.0.4

Platform

  • OS and version: Pi OS (Debian 11 Bullseye)
  • Platform: Raspberry Pi bare metal

Expected behavior

I run two copies of PiHole on two Raspberry Pis. I have them in a Master/Backup configuration using keepalived. I only just noticed that the primary had stopped working - but the secondary picked things up nicely. I looked at the logs and found a crash in the FTL.log file

Actual behavior / bug

Please refer to the attached log file: FTL.log.txt

Steps to reproduce

Steps to reproduce the behavior: Unknown

Debug Token

  • URL:

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.
@githubsean
Copy link
Author

Though I might paste the log here too

2025-03-07 00:36:54.538 AEDT [90990/T91198] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-03-07 00:36:54.538 AEDT [90990/T91198] INFO: Time offset: -8.447170e-01 ms (excluded 1 outliers)
2025-03-07 00:36:54.539 AEDT [90990/T91198] INFO: Round-trip delay: 2.586160e+00 ms (excluded 1 outliers)
2025-03-07 01:36:54.676 AEDT [90990/T91198] INFO: Received 8/8 valid NTP replies from pool.ntp.org
2025-03-07 01:36:54.676 AEDT [90990/T91198] INFO: Time offset: -2.074957e+00 ms (excluded 0 outliers)
2025-03-07 01:36:54.676 AEDT [90990/T91198] INFO: Round-trip delay: 2.836227e+00 ms (excluded 0 outliers)
2025-03-07 01:39:00.336 AEDT [90990/T91199] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-07 01:39:00.336 AEDT [90990/T91199] INFO: ---------------------------->  FTL crashed!  <----------------------------
2025-03-07 01:39:00.336 AEDT [90990/T91199] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-07 01:39:00.336 AEDT [90990/T91199] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: and include in your report already the following details:
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL has been running for 151352 seconds
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL branch: master
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL version: v6.0.4
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL commit: b7eb53bf
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: FTL user: started as pihole, ended as pihole
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: Compiled for linux/arm64/v8 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: Process details: MID: 90990
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO:                  PID: 90990
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO:                  TID: 91199
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO:                  Name: database
2025-03-07 01:39:00.337 AEDT [90990/T91199] INFO: Received signal: Segmentation fault
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO:      at address: 0x28
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO:      with code:  SEGV_MAPERR (Address not mapped to object)
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO: ------ Listing content of directory /dev/shm ------
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO: File Mode User:Group      Size  Filename
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO: rwxrwxrwx root:root       360   .
2025-03-07 01:39:00.338 AEDT [90990/T91199] INFO: rwxr-xr-x root:root         4K  ..
2025-03-07 01:39:00.339 AEDT [90990/T91199] INFO: rw------- pihole:pihole   786K  FTL-90990-recycler
2025-03-07 01:39:00.339 AEDT [90990/T91199] INFO: rw------- pihole:pihole    57K  FTL-90990-dns-cache-lookup
2025-03-07 01:39:00.339 AEDT [90990/T91199] INFO: rw------- pihole:pihole    29K  FTL-90990-domains-lookup
2025-03-07 01:39:00.339 AEDT [90990/T91199] INFO: rw------- pihole:pihole     4K  FTL-90990-clients-lookup
2025-03-07 01:39:00.340 AEDT [90990/T91199] INFO: rw------- pihole:pihole   569K  FTL-90990-fifo-log
2025-03-07 01:39:00.340 AEDT [90990/T91199] INFO: rw------- pihole:pihole     4K  FTL-90990-per-client-regex
2025-03-07 01:39:00.340 AEDT [90990/T91199] INFO: rw------- pihole:pihole   573K  FTL-90990-dns-cache
2025-03-07 01:39:00.340 AEDT [90990/T91199] INFO: rw------- pihole:pihole     8K  FTL-90990-overTime
2025-03-07 01:39:00.340 AEDT [90990/T91199] INFO: rw------- pihole:pihole    12M  FTL-90990-queries
2025-03-07 01:39:00.341 AEDT [90990/T91199] INFO: rw------- pihole:pihole    29K  FTL-90990-upstreams
2025-03-07 01:39:00.341 AEDT [90990/T91199] INFO: rw------- pihole:pihole   348K  FTL-90990-clients
2025-03-07 01:39:00.341 AEDT [90990/T91199] INFO: rw------- pihole:pihole   209K  FTL-90990-domains
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: rw------- pihole:pihole   246K  FTL-90990-strings
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: rw------- pihole:pihole   144   FTL-90990-settings
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: rw------- pihole:pihole   328   FTL-90990-counters
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: rw------- pihole:pihole    88   FTL-90990-lock
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: ---------------------------------------------------
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-03-07 01:39:00.342 AEDT [90990/T91199] INFO: Thank you for helping us to improve our FTL engine!
2025-03-07 01:39:00.343 AEDT [90990/T91199] INFO: Waiting for threads to join
2025-03-07 01:39:00.430 AEDT [90990/T91202] INFO: Terminating timer thread
2025-03-07 01:39:00.820 AEDT [90990/T91201] INFO: Terminating resolver thread
2025-03-07 01:39:01.213 AEDT [90990/T91200] INFO: Terminating GC thread
2025-03-07 01:39:02.343 AEDT [90990/T91199] INFO: Thread database (0) is still busy, cancelling it.
2025-03-07 01:39:02.969 AEDT [90990M] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-03-07 01:39:02.970 AEDT [90990M] ERROR: Error when obtaining inner SHM lock: Previous owner died
2025-03-07 01:39:04.223 AEDT [90990M] ERROR: export_queries_to_disk(): Failed to export queries: database is locked
2025-03-07 01:39:04.223 AEDT [90990M] INFO:     SQL query was: "INSERT INTO disk.query_storage SELECT * FROM query_storage WHERE id > ? AND timestamp < ?"
2025-03-07 01:39:04.223 AEDT [90990M] INFO:     with parameters: id = 2072102, timestamp = 1741271943.221472
2025-03-07 01:39:04.223 AEDT [90990M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.domain_by_id SELECT * FROM domain_by_id): Cannot export subtable: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.client_by_id SELECT * FROM client_by_id): Cannot export subtable: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.forward_by_id SELECT * FROM forward_by_id): Cannot export subtable: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.addinfo_by_id SELECT * FROM addinfo_by_id): Cannot export subtable: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(disk.UPDATE disk.sqlite_sequence SET seq = (SELECT seq FROM sqlite_sequence WHERE disk.sqlite_sequence.name = sqlite_sequence.name)): Cannot export subtable: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: ERROR: SQL query "INSERT OR REPLACE INTO disk.ftl (id, value) VALUES ( 1, 1741271934.929352 );" failed: database is locked (SQLITE_BUSY)
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(): Cannot update timestamp: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: ERROR: SQL query "UPDATE disk.counters SET value = value + 0 WHERE id = 0;" failed: database is locked (SQLITE_BUSY)
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(): Cannot update total queries counter: database is locked
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: ERROR: SQL query "UPDATE disk.counters SET value = value + 0 WHERE id = 1;" failed: database is locked (SQLITE_BUSY)
2025-03-07 01:39:04.224 AEDT [90990M] ERROR: export_queries_to_disk(): Cannot update blocked queries counter: database is locked
2025-03-07 01:39:04.231 AEDT [90990M] INFO: Finished final database update
2025-03-07 01:39:04.231 AEDT [90990M] INFO: Waiting for threads to join
2025-03-07 01:39:04.232 AEDT [90990M] INFO: Thread ntp-client (4) is idle, terminating it.
2025-03-07 01:39:04.232 AEDT [90990M] INFO: All threads joined
2025-03-07 01:39:04.236 AEDT [90990M] INFO: PID file emptied
2025-03-07 01:39:05.239 AEDT [90990M] ERROR: SQL error in backup_db_sessions(): database is locked (5)
2025-03-07 01:39:05.975 AEDT [90990M] INFO: ########## FTL terminated after 1d 18h 2m 37s  (code 0)! ##########

@githubsean
Copy link
Author

I also noticed that the systemd unit exited successfully, similar to this comment
I ship my logs off machine, I have the following logged (order is newest to oldest). You can see that keepalived picked up that the pihole-FTL service was not running. It tests this using "systemctl is-active pihole-FTL.service", and because the unit had exited and wasn't running, keepalived treated that as a fault.

03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,(VI_2) Entering FAULT STATE
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,(VI_2) Entering FAULT STATE
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,VRRP_Group(SYNC) Syncing instances to FAULT state
03/07/2025,01:39:06,Info,pihole1,daemon,avahi-daemon,Withdrawing address record for 192.168.53.253 on eth0.
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,(VI_1) sent 0 priority
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,(VI_1) Entering FAULT STATE
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,VRRP_Script(chk_pihole) failed (exited with status 3)
03/07/2025,01:39:06,Info,pihole1,user,Keepalived_vrrp,Script `chk_pihole` now returning 3
03/07/2025,01:39:06,Notice,pihole1,daemon,systemd,pihole-FTL.service: Consumed 1h 16min 1.627s CPU time.
03/07/2025,01:39:06,Info,pihole1,daemon,systemd,pihole-FTL.service: Succeeded.

@streamdp streamdp mentioned this issue Mar 15, 2025
Closed
@DL6ER
Copy link
Member

DL6ER commented Mar 16, 2025

We have meanwhile found that a crash in a thread leads to the incorrect exit with code 0 and, hence, no restarting. It is fixed in development for about two weeks. Unfortunately, we don't have the capacities in the team right now for another release, however, you could try

sudo pihole checkout ftl development

to get the most recent state. There is no breaking incompatibility in it so you can go back using

sudo pihole checkout ftl master

at any point.

@DL6ER DL6ER added the crash label Mar 16, 2025
@r4tt4
Copy link

r4tt4 commented Mar 21, 2025

Got the same issue. Tried the mentioned fix with the FTL-DEV. Brings me into another ERR. Got an Apache running on the same host on the alternative port 8008 which is not reachable as long the FTL-DEV is used. Going back to the normal master fixed that behavior. My resolution for now: monitoring if the service is stopped and try to restart it via a bash/cron voodoo.

@DL6ER
Copy link
Member

DL6ER commented Mar 22, 2025

You can use webserver.ports in pihole.toml to configure which ports are used by your Pi-hole. Only one process can use the same port at the same time.

@networkerict
Copy link

Just had the exact same problem. See log file below. I switched to FTL DEV as suggested here already to see how this goes.

2025-03-28 11:59:00.133 CET [21064/T250715] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: ----------------------------> FTL crashed! <----------------------------
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: Please report a bug at https://github.com/pi-hole/FTL/issues
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: and include in your report already the following details:
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL has been running for 177920 seconds
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL branch: master
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL version: v6.0.4
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL commit: b7eb53b
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: FTL user: started as pihole, ended as pihole
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: Process details: MID: 21064
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: PID: 21064
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: TID: 250715
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: Name: database
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: Received signal: Segmentation fault
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: at address: 0x28
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: with code: SEGV_MAPERR (Address not mapped to object)
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: !!! INFO: pihole-FTL has not been compiled with glibc/backtrace support, not generating one !!!
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: ------ Listing content of directory /dev/shm ------
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: File Mode User:Group Size Filename
2025-03-28 11:59:00.145 CET [21064/T250715] INFO: rwxrwxrwx root:root 360 .
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rwxr-xr-x root:root 480 ..
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 88 FTL-21064-lock
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 328 FTL-21064-counters
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 144 FTL-21064-settings
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 246K FTL-21064-strings
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 229K FTL-21064-domains
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 348K FTL-21064-clients
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 29K FTL-21064-upstreams
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 9M FTL-21064-queries
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 8K FTL-21064-overTime
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 696K FTL-21064-dns-cache
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 4K FTL-21064-per-client-regex
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 569K FTL-21064-fifo-log
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 4K FTL-21064-clients-lookup
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 41K FTL-21064-domains-lookup
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 102K FTL-21064-dns-cache-lookup
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: rw------- pihole:pihole 786K FTL-21064-recycler
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: ---------------------------------------------------
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: Please also include some lines from above the !!!!!!!!! header.
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: Thank you for helping us to improve our FTL engine!
2025-03-28 11:59:00.146 CET [21064/T250715] INFO: Waiting for threads to join
2025-03-28 11:59:00.184 CET [21064/T250718] INFO: Terminating timer thread
2025-03-28 11:59:00.247 CET [21064/T250717] INFO: Terminating resolver thread
2025-03-28 11:59:01.091 CET [21064/T250716] INFO: Terminating GC thread
2025-03-28 11:59:02.146 CET [21064/T250715] INFO: Thread database (0) is still busy, cancelling it.
2025-03-28 11:59:02.146 CET [21064M] ERROR: Error when obtaining outer SHM lock: Previous owner died
2025-03-28 11:59:02.146 CET [21064M] ERROR: Error when obtaining inner SHM lock: Previous owner died
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(): Failed to export queries: database is locked
2025-03-28 11:59:03.398 CET [21064M] INFO: SQL query was: "INSERT INTO disk.query_storage SELECT * FROM query_storage WHERE id > ? AND timestamp < ?"
2025-03-28 11:59:03.398 CET [21064M] INFO: with parameters: id = 2859053, timestamp = 1743159542.397067
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.domain_by_id SELECT * FROM domain_by_id): Cannot export subtable: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.client_by_id SELECT * FROM client_by_id): Cannot export subtable: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.forward_by_id SELECT * FROM forward_by_id): Cannot export subtable: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(disk.INSERT OR IGNORE INTO disk.addinfo_by_id SELECT * FROM addinfo_by_id): Cannot export subtable: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(disk.UPDATE disk.sqlite_sequence SET seq = (SELECT seq FROM sqlite_sequence WHERE disk.sqlite_sequence.name = sqlite_sequence.name)): Cannot export subtable: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: ERROR: SQL query "INSERT OR REPLACE INTO disk.ftl (id, value) VALUES ( 1, 1743159539.833270 );" failed: database is locked (SQLITE_BUSY)
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(): Cannot update timestamp: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: ERROR: SQL query "UPDATE disk.counters SET value = value + 0 WHERE id = 0;" failed: database is locked (SQLITE_BUSY)
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(): Cannot update total queries counter: database is locked
2025-03-28 11:59:03.398 CET [21064M] ERROR: ERROR: SQL query "UPDATE disk.counters SET value = value + 0 WHERE id = 1;" failed: database is locked (SQLITE_BUSY)
2025-03-28 11:59:03.398 CET [21064M] ERROR: export_queries_to_disk(): Cannot update blocked queries counter: database is locked
2025-03-28 11:59:03.400 CET [21064M] INFO: Finished final database update
2025-03-28 11:59:03.400 CET [21064M] INFO: Waiting for threads to join
2025-03-28 11:59:03.400 CET [21064M] INFO: All threads joined
2025-03-28 11:59:03.402 CET [21064M] INFO: PID file emptied
2025-03-28 11:59:03.403 CET [21064M] INFO: Stored 0 API sessions in the database
2025-03-28 11:59:04.208 CET [21064M] INFO: ########## FTL terminated after 2d 1h 25m 24s (code 0)! ##########
2025-03-28 12:38:13.904 CET [185M] INFO: ########## FTL started on pihole-lxc! ##########
2025-03-28 12:38:13.906 CET [185M] INFO: FTL branch: master
2025-03-28 12:38:13.906 CET [185M] INFO: FTL version: v6.0.4
2025-03-28 12:38:13.906 CET [185M] INFO: FTL commit: b7eb53b
2025-03-28 12:38:13.906 CET [185M] INFO: FTL date: 2025-03-04 17:22:10 +0000
2025-03-28 12:38:13.906 CET [185M] INFO: FTL user: pihole
2025-03-28 12:38:13.906 CET [185M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-28 12:38:13.908 CET [185M] INFO: Wrote config file:
2025-03-28 12:38:13.908 CET [185M] INFO: - 153 total entries
2025-03-28 12:38:13.908 CET [185M] INFO: - 143 entries are default
2025-03-28 12:38:13.908 CET [185M] INFO: - 10 entries are modified
2025-03-28 12:38:13.908 CET [185M] INFO: - 0 entries are forced through environment
2025-03-28 12:38:13.909 CET [185M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-03-28 12:38:13.909 CET [185M] INFO: PID file does not exist or not readable
2025-03-28 12:38:13.909 CET [185M] INFO: No other running FTL process found.
2025-03-28 12:38:13.909 CET [185M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-03-28 12:38:13.911 CET [185M] INFO: PID of FTL process: 185
2025-03-28 12:38:13.911 CET [185M] INFO: listening on 0.0.0.0 port 53
2025-03-28 12:38:13.911 CET [185M] INFO: listening on :: port 53
2025-03-28 12:38:13.911 CET [185M] INFO: PID of FTL process: 185
2025-03-28 12:38:13.914 CET [185M] ERROR: SQLite3: recovered 569 frames from WAL file /etc/pihole/pihole-FTL.db-wal (283)
2025-03-28 12:38:13.914 CET [185M] INFO: Database version is 21
2025-03-28 12:38:13.921 CET [185M] INFO: Database successfully initialized
2025-03-28 12:38:14.404 CET [185M] INFO: Imported 81764 queries from the on-disk database (it has 2380970 rows)
2025-03-28 12:38:14.404 CET [185M] INFO: Parsing queries in database
2025-03-28 12:38:14.425 CET [185M] INFO: 10000 queries parsed...
2025-03-28 12:38:14.441 CET [185M] INFO: 20000 queries parsed...
2025-03-28 12:38:14.455 CET [185M] INFO: 30000 queries parsed...
2025-03-28 12:38:14.468 CET [185M] INFO: 40000 queries parsed...
2025-03-28 12:38:14.482 CET [185M] INFO: 50000 queries parsed...
2025-03-28 12:38:14.493 CET [185M] INFO: 60000 queries parsed...
2025-03-28 12:38:14.507 CET [185M] INFO: 70000 queries parsed...
2025-03-28 12:38:14.521 CET [185M] INFO: 80000 queries parsed...
2025-03-28 12:38:14.524 CET [185M] INFO: Imported 81764 queries from the long-term database
2025-03-28 12:38:14.524 CET [185M] INFO: -> Total DNS queries: 81764
2025-03-28 12:38:14.524 CET [185M] INFO: -> Cached DNS queries: 53211
2025-03-28 12:38:14.524 CET [185M] INFO: -> Forwarded DNS queries: 14571
2025-03-28 12:38:14.524 CET [185M] INFO: -> Blocked DNS queries: 13748
2025-03-28 12:38:14.524 CET [185M] INFO: -> Unknown DNS queries: 7
2025-03-28 12:38:14.524 CET [185M] INFO: -> Unique domains: 2528
2025-03-28 12:38:14.524 CET [185M] INFO: -> Unique clients: 49
2025-03-28 12:38:14.524 CET [185M] INFO: -> DNS cache records: 647
2025-03-28 12:38:14.524 CET [185M] INFO: -> Known forward destinations: 2
2025-03-28 12:38:14.564 CET [185M] INFO: NTP sync is disabled
2025-03-28 12:38:14.564 CET [185M] INFO: FTL is running as user pihole (UID 999)
2025-03-28 12:38:14.564 CET [185M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-03-28 12:38:14.564 CET [185M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-03-28 12:38:14.564 CET [185M] INFO: Web server ports:
2025-03-28 12:38:14.564 CET [185M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2025-03-28 12:38:14.564 CET [185M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2025-03-28 12:38:14.564 CET [185M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
2025-03-28 12:38:14.564 CET [185M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
2025-03-28 12:38:14.564 CET [185M] INFO: Restored 0 API sessions from the database
2025-03-28 12:38:14.566 CET [185M] INFO: Blocking status is enabled
2025-03-28 12:38:14.697 CET [185/T338] INFO: Compiled 2 allow and 14 deny regex for 49 clients in 32.4 msec
2025-03-28 13:19:00.099 CET [185/T338] INFO: Gravity database has been updated, reloading now
2025-03-28 13:19:00.258 CET [185/T338] INFO: Compiled 2 allow and 14 deny regex for 49 clients in 30.9 msec
2025-03-28 13:30:05.630 CET [185M] INFO: Asked to terminate by "/sbin/init" (PID 1, user root UID 0)
2025-03-28 13:30:05.631 CET [185/T338] INFO: Terminating database thread
2025-03-28 13:30:05.653 CET [185/T341] INFO: Terminating timer thread
2025-03-28 13:30:05.766 CET [185/T340] INFO: Terminating resolver thread
2025-03-28 13:30:05.945 CET [185M] INFO: Finished final database update
2025-03-28 13:30:05.945 CET [185M] INFO: Waiting for threads to join
2025-03-28 13:30:05.945 CET [185M] INFO: Thread housekeeper (1) is idle, terminating it.
2025-03-28 13:30:05.945 CET [185M] INFO: All threads joined
2025-03-28 13:30:05.946 CET [185M] INFO: PID file emptied
2025-03-28 13:30:05.946 CET [185M] INFO: Stored 0 API sessions in the database
2025-03-28 13:30:06.866 CET [185M] INFO: ########## FTL terminated after 51m 52s (code 0)! ##########
2025-03-28 13:30:06.967 CET [6578M] INFO: ########## FTL started on pihole-lxc! ##########
2025-03-28 13:30:06.967 CET [6578M] INFO: FTL branch: development
2025-03-28 13:30:06.967 CET [6578M] INFO: FTL version: vDev-d3ecfb6
2025-03-28 13:30:06.967 CET [6578M] INFO: FTL commit: d3ecfb6
2025-03-28 13:30:06.967 CET [6578M] INFO: FTL date: 2025-03-28 09:42:24 +0100
2025-03-28 13:30:06.967 CET [6578M] INFO: FTL user: pihole
2025-03-28 13:30:06.967 CET [6578M] INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
2025-03-28 13:30:06.970 CET [6578M] INFO: Wrote config file:
2025-03-28 13:30:06.970 CET [6578M] INFO: - 156 total entries
2025-03-28 13:30:06.970 CET [6578M] INFO: - 146 entries are default
2025-03-28 13:30:06.970 CET [6578M] INFO: - 10 entries are modified
2025-03-28 13:30:06.970 CET [6578M] INFO: - 0 entries are forced through environment
2025-03-28 13:30:06.971 CET [6578M] INFO: Config file written to /etc/pihole/pihole.toml
2025-03-28 13:30:06.972 CET [6578M] INFO: Parsed config file /etc/pihole/pihole.toml successfully
2025-03-28 13:30:06.972 CET [6578M] INFO: PID file does not exist or not readable
2025-03-28 13:30:06.972 CET [6578M] INFO: No other running FTL process found.
2025-03-28 13:30:06.972 CET [6578M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0
2025-03-28 13:30:06.973 CET [6578M] INFO: PID of FTL process: 6578
2025-03-28 13:30:06.974 CET [6578M] INFO: listening on 0.0.0.0 port 53
2025-03-28 13:30:06.974 CET [6578M] INFO: listening on :: port 53
2025-03-28 13:30:06.974 CET [6578M] INFO: PID of FTL process: 6578
2025-03-28 13:30:06.976 CET [6578M] INFO: Database version is 21
2025-03-28 13:30:06.976 CET [6578M] INFO: Database successfully initialized
2025-03-28 13:30:07.444 CET [6578M] INFO: Imported 83091 queries from the on-disk database (it has 2384367 rows)
2025-03-28 13:30:07.444 CET [6578M] INFO: Parsing queries in database
2025-03-28 13:30:07.466 CET [6578M] INFO: 10000 queries parsed...
2025-03-28 13:30:07.483 CET [6578M] INFO: 20000 queries parsed...
2025-03-28 13:30:07.497 CET [6578M] INFO: 30000 queries parsed...
2025-03-28 13:30:07.510 CET [6578M] INFO: 40000 queries parsed...
2025-03-28 13:30:07.524 CET [6578M] INFO: 50000 queries parsed...
2025-03-28 13:30:07.536 CET [6578M] INFO: 60000 queries parsed...
2025-03-28 13:30:07.550 CET [6578M] INFO: 70000 queries parsed...
2025-03-28 13:30:07.565 CET [6578M] INFO: 80000 queries parsed...
2025-03-28 13:30:07.569 CET [6578M] INFO: Imported 83090 queries from the long-term database
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Total DNS queries: 83090
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Cached DNS queries: 54293
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Forwarded DNS queries: 14980
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Blocked DNS queries: 13551
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Unknown DNS queries: 8
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Unique domains: 2542
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Unique clients: 49
2025-03-28 13:30:07.569 CET [6578M] INFO: -> DNS cache records: 651
2025-03-28 13:30:07.569 CET [6578M] INFO: -> Known forward destinations: 2
2025-03-28 13:30:07.683 CET [6578M] INFO: NTP sync is disabled
2025-03-28 13:30:07.683 CET [6578M] INFO: FTL is running as user pihole (UID 999)
2025-03-28 13:30:07.684 CET [6578M] INFO: Reading certificate from /etc/pihole/tls.pem ...
2025-03-28 13:30:07.684 CET [6578M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem
2025-03-28 13:30:07.684 CET [6578M] INFO: Web server ports:
2025-03-28 13:30:07.684 CET [6578M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: Web server ports:
2025-03-28 13:30:07.685 CET [6578M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - [::]:80 (HTTP, IPv6, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK)
2025-03-28 13:30:07.685 CET [6578M] INFO: Restored 0 API sessions from the database
2025-03-28 13:30:07.686 CET [6578M] INFO: Blocking status is enabled
2025-03-28 13:30:07.819 CET [6578/T6598] INFO: Compiled 2 allow and 14 deny regex for 49 clients in 35.2 msec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crash Waiting for feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@githubsean @DL6ER @r4tt4 @networkerict