Please follow the below template, it will help us to help you!
Please ensure that you are running the latest version of the beta code.
Run pihole -up to update to the latest, then verify that the problem still exists before reporting it.
Pi-hole version is release/v5.0 v4.3.5-482-gd42785a (Latest: v4.4)
AdminLTE version is release/v5.0 v4.3.2-472-gfec4550 (Latest: v4.3.3)
FTL version is release/v5.0 vDev-5ad55e8 (Latest: v4.3.1)
Problem with Beta 5.0:
Ran "pihole -flush" and pihole -arpflush" to clean up dashboard to test changes made to Unifi configuration. After Pihole commands were ran, noticed the network table in the Admin UI was no longer populating. Checked the "pihole-FTL" log and noticed this:
[2020-04-27 17:25:00.061 7609] SQLite3 message: database corruption at line 65570 of [18db032d05] (11)
[2020-04-27 17:25:00.061 7609] SQLite3 message: statement aborts at 3: [SELECT MAX(ID) FROM queries] database disk image is malformed (11)
[2020-04-27 17:25:00.062 7609] Encountered step error in get_max_query_ID(): database disk image is malformed
[2020-04-27 17:25:00.062 7609] Encountered error while trying to close database: database is locked
[2020-04-27 17:25:00.062 7609] SQLite3 message: database corruption at line 65570 of [18db032d05] (11)
[2020-04-27 17:25:00.062 7609] SQLite3 message: statement aborts at 3: [INSERT INTO queries VALUES (NULL,?,?,?,?,?,?)] database disk image is malformed (11)
[2020-04-27 17:25:00.062 7609] Encountered error while trying to store queries in long-term database: database disk image is malformed
[2020-04-27 17:25:00.062 7609] dbquery("END TRANSACTION") called but database is not available!
[2020-04-27 17:25:00.062 7609] END TRANSACTION failed when trying to store queries to long-term database
[2020-04-27 17:25:00.063 7609] dbquery("BEGIN TRANSACTION IMMEDIATE") called but database is not available!
[2020-04-27 17:25:00.063 7609] ERROR: Storing devices in network table ("BEGIN TRANSACTION IMMEDIATE") failed
After seeing the db corruption, attempted to run "pihole -reconfingure" and selected the "Repair" option but that did not correct the issue.
Debug Token:
https://tricorder.pi-hole.net/c6wsemo2ll