Skip to content

Database corruption after clear install #2767

@zunov92

Description

@zunov92

Versions

  • Pi-hole: 6.3
  • Web: 6.4
  • FTL: 6.4.1

Platform

  • OS and version: Debian Linux NanoPi-NEO3 6.1.63 SMP Thu Nov 30 20:48:04 CST 2023 aarch64 GNU/Linux
  • Platform: NanoPi-NEO3

Expected behavior

Clear istall of instance by curl -sSL https://install.pi-hole.net | bash command

Actual behavior / bug

FTL base have been corrupted after start migrations

#Logs form FTL

2026-01-21 10:49:01.574 INFO PID of FTL process: 702
2026-01-21 10:49:01.584 INFO listening on 0.0.0.0 port 53
2026-01-21 10:49:01.585 INFO listening on :: port 53
2026-01-21 10:49:01.587 INFO PID of FTL process: 702
2026-01-21 10:49:01.621 ERROR SQLite3: recovered 11 frames from WAL file /etc/pihole/pihole-FTL.db-wal (283)
2026-01-21 10:49:01.624 INFO Database version is 21
2026-01-21 10:49:01.643 INFO Database successfully initialized
2026-01-21 10:49:01.664 INFO Imported 0 queries from the on-disk database (it has 0 rows)
2026-01-21 10:49:01.664 INFO Parsing queries in database
2026-01-21 10:49:01.665 INFO Imported 0 queries from the long-term database
2026-01-21 10:49:01.665 INFO  -> Total DNS queries: 0
2026-01-21 10:49:01.665 INFO  -> Cached DNS queries: 0
2026-01-21 10:49:01.665 INFO  -> Forwarded DNS queries: 0
2026-01-21 10:49:01.665 INFO  -> Blocked DNS queries: 0
2026-01-21 10:49:01.665 INFO  -> Unknown DNS queries: 0
2026-01-21 10:49:01.665 INFO  -> Unique domains: 0
2026-01-21 10:49:01.666 INFO  -> Unique clients: 0
2026-01-21 10:49:01.666 INFO  -> DNS cache records: 0
2026-01-21 10:49:01.666 INFO  -> Known forward destinations: 0
2026-01-21 10:49:02.161 INFO FTL is running as user pihole (UID 999)
2026-01-21 10:49:02.163 INFO Reading certificate from /etc/pihole/tls.pem ...
2026-01-21 10:49:02.164 INFO Using SSL/TLS certificate file /etc/pihole/tls.pem
2026-01-21 10:49:02.166 INFO Web server ports:
2026-01-21 10:49:02.166 INFO   - 0.0.0.0:80 (HTTP, IPv4, optional, OK)
2026-01-21 10:49:02.166 INFO   - 0.0.0.0:443 (HTTPS, IPv4, optional, OK)
2026-01-21 10:49:02.167 INFO   - [::]:80 (HTTP, IPv6, optional, OK)
2026-01-21 10:49:02.167 INFO   - [::]:443 (HTTPS, IPv6, optional, OK)
2026-01-21 10:49:02.167 INFO Restored 0 API sessions from the database
2026-01-21 10:49:02.178 INFO Blocking status is enabled
2026-01-21 10:49:02.274 INFO Compiled 0 allow and 0 deny regex for 2 clients in 0.2 msec
2026-01-21 10:49:06.322 INFO Received 8/8 valid NTP replies from pool.ntp.org
2026-01-21 10:49:06.323 INFO Time offset: 5.852913e+04 ms (excluded 1 outliers)
2026-01-21 10:49:06.324 INFO Round-trip delay: 1.279197e+01 ms (excluded 1 outliers)
2026-01-21 10:50:04.853 INFO Local time is too inaccurate, retrying in 600 seconds before launching NTP server
2026-01-21 10:50:04.907 ERROR SQLite3: database corruption at line 75837 of [fb2c931ae5] (11)
2026-01-21 10:50:04.907 ERROR SQLite3: database disk image is malformed in "SELECT vendor FROM macvendor WHERE mac LIKE ?;" (11)
2026-01-21 10:50:04.907 ERROR getMACVendor("04:ec:d8:ac:f2:1f") - SQL error prepare "SELECT vendor FROM macvendor WHERE mac LIKE ?;": database disk image is malformed
2026-01-21 10:50:04.908 WARNING Database /etc/pihole/pihole-FTL.db is damaged and cannot be used.
2026-01-21 10:51:00.068 ERROR SQLite3: statement aborts at 1: cannot start a transaction within a transaction; [BEGIN TRANSACTION] (1)
2026-01-21 10:51:00.068 ERROR ERROR: SQL query "BEGIN TRANSACTION" failed: SQL logic error (SQLITE_ERROR)
2026-01-21 10:51:00.069 WARNING Starting first transaction failed during ARP parsing
2026-01-21 10:52:00.073 ERROR SQLite3: statement aborts at 1: cannot start a transaction within a transaction; [BEGIN TRANSACTION] (1)
2026-01-21 10:52:00.074 ERROR ERROR: SQL query "BEGIN TRANSACTION" failed: SQL logic error (SQLITE_ERROR)
2026-01-21 10:52:00.074 WARNING Starting first transaction failed during ARP parsing

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions