Sqlite3 database disk image is malformed errors in pihole-FTL.log

General Beta 5.0
1

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@pi-hole2:~ $ pihole -up
[i] Checking for updates...
[i] Pi-hole Core: up to date
[i] Web Interface: up to date
[i] FTL: up to date
[i] Warning: You are using FTL from a custom branch (release/v5.0) and might be missing future releases.

[✓] Everything is up to date!
pi@pi-hole2:~ $ pihole -v
Pi-hole version is v4.3.5-457-ga2d2639 (Latest: v4.4)
AdminLTE version is v4.3.2-457-g0a81dadf (Latest: v4.3.3)
FTL version is vDev-81c4eac (Latest: v4.3.1)

Problem with Beta 5.0:
While submitting debug token for different issue I noticed repeating error in pihole-FTL.log:

[2020-04-02 17:59:37.776 600] SQLite3 message: database corruption at line 88527 of [18db032d05] (11)
[2020-04-02 17:59:37.777 600] SQLite3 message: statement aborts at 8: [DELETE FROM queries WHERE timestamp <= 1578070740] database disk image is malformed (11)
[2020-04-02 17:59:58.567 600] ERROR: SQL query "DELETE FROM queries WHERE timestamp <= 1578070740" failed: database disk image is malformed
[2020-04-02 17:59:58.569 600] delete_old_queries_in_DB(): Deleting queries due to age of entries failed!

Should I be worried? How would I go about fixing this in any way?

Debug Token:
https://tricorder.pi-hole.net/jlujkylsu5

2

Well, it depends. If you've maybe (accidentally) tried to do something with the database (like emptying it), then this might have been the consequence of some error. If not, it may ppint to an issue with the file system of your Pi-hole.

There isn't something Pi-hole specific in the database, typical websearch results will all be applicable, for instance:

3

Thanks for pointing me in the right direction, truth is I never did anything with the .db from cli. The check reported many errors none of them of the reindex variety, in the end I took the sledgehammer approach and stopped ftl, deleted the db, started ftl, which recreated the db and checking the newly created db reports no errors.