Statx & Group Managment database error

Tried updating gravity list and was receiving statx error and now my blocklists are gone and am not able to add any. Received a database error as well as I was trying to access the Group Management area in pihole. See screen shot below.

Was just logging into pihole to check queries and update gravity. See debug token below. Running the following versions:
Pihole Core: v6.0.5, FTL: v6.0.4, Web Interface: v6.0.2
Raspberry Pi5:
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

https://tricorder.pi-hole.net/0UDjbpq8/

You have 2 issues:

  1. statx error message:
    As explained on the other issue, the statx error message is expected and this is already being fixed. Also, this is not a fatal issue. Actually this is a harmless issue.

  2. Your gravity database is broken:

    2025-03-25 21:53:21.039 EDT [1353/T9050] ERROR: SQLite3: no such table: info in "SELECT value FROM info WHERE property = 'updated';" (1)
    2025-03-25 21:53:21.039 EDT [1353/T9050] WARNING: gravity_updated(): SELECT value FROM info WHERE property = 'updated'; - SQL error prepare: SQL logic error
    

    info table is missing, which probably means the database is corrupted.

    Move your old gravity database to a new file and let Pi-hole rebuild it running these commands (maybe you need to add sudo before both commands):

    mv /etc/pihole/gravity.db /etc/pihole/gravity_backup.db
    pihole -g
    

Thank you so much for catching this and supplying me with the resolution. This worked instantly and my lists are working. Just curious what would have caused this? I logged in normally just checking logs and went to update the gravity list.

So Pi-hole ran fine for a bit and then the database was broken again. Not sure what is causing this?

Maybe a bad SD card? Causing file corruption?

Rebuilt database and lists are running again fine. When I added my lists back and ran update gravity, it did hang up for a long time. Closed out pihole and logged back in, updated gravity and ran quick and was successful. I’ll keep an eye on it to see if it breaks again.

Could it also be related to the fix that is being worked on?

The statx message is related to the fix, but not the other part (corrupted database).

Something else broke the database, but there's no way of knowing what.

So would it make sense to reinstall raspberrypi os and configure from scratch if it happens again?

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.