After upgrading from latest v5 to v6, I get database errors but Pihole is working

[oe3gwu]

Versions

• Core version is v6.0 (Latest: v6.0.1)
• Web version is v6.0 (Latest: v6.0)
• FTL version is v6.0 (Latest: v6.0)

Platform

• OS and version: Ubuntu 22.04

• Platform: Proxmox LXC Container with a Docker

Expected behavior

A running error free Pihole.

Actual behavior / bug

I just updated pihole with a docker compose down, docker compose pull and docker compose up -d and it is actually running and working, but in the logs, I get errors that should not be there and were not there with v5.

I NEVER connected to the DB and messed with it.

Steps to reproduce

Steps to reproduce the behavior:

1. Update Pihole v5 to v6 using docker compose
2. Start the docker container
3. Check the logs.
4. See error

Debug Token

• URL: https://tricorder.pi-hole.net/A0wKGeHr/

Screenshots

Additional context

pihole.log

Thank you!

[yubiuser]

WARNING: Database /etc/pihole/pihole-FTL.db is damaged and cannot be used.

Stop the container, move the old database to a backup location, restart the container.

[oe3gwu]

WARNING: Database /etc/pihole/pihole-FTL.db is damaged and cannot be used.

Stop the container, move the old database to a backup location, restart the container.

Does the Database reorganize itself again, or do i loose something if I do this?

[yubiuser]

You loose the long-term query database.

[aronmgv]

Screenshots

@oe3gwu Off topic, what app is that on the screenshot? doesnt look like portainer.. thanks!

[oe3gwu]

Screenshots

@oe3gwu Off topic, what app is that on the screenshot? doesnt look like portainer.. thanks!

It's the proxmox console of my lxd container.

[oe3gwu]

You loose the long-term query database.

I even dont got the sqlite database on a persistent volume. I loose this data all time when i stop the container because the db is deleted. So it cant be inconsistent. Because even at a restart those log entries happen.

[terrlinde]

I also saw same Errors as oe3gwu after updating to the new container version 2025.02.4.
Longterm Logs were not saved and Query Logs only showed a short Period (under a minute) of Logs just after fresh bootup.
Additionaly I see entries like "database corruption", "database disk image is malformed" and "database FTL.db is damaged and cannot be used"

@oe3gwu as yubiuser said, try to delete the old database from volume. usually the FTL.db is mounted outside the container and is in /etc/pihole. Check if you mounted it somewhere, stop the container, rename FTL.db to FTL.db.old and start it again. Worked for me, now logs are beeing stored, Querly Log is showing actual data, no Errors in FTL.log.