Portainer Database problem

[Twiederh]

Ask a Question!

Hi,
today I noticed that I could not access portainer anymore. It restarts all the time and in the logs I see an issue with the portainer database:
2025/08/22 12:28PM INF github.com/portainer/portainer@v0.6.1-0.20241105012540-458d722d4754/api/database/boltdb/db.go:133 > loading PortainerDB | filename=portainer.db
panic: assertion failed: Page expected to be: 40, but self identifies as 8017289335592021100

I found a database backup from two days ago but unfortunately I get the same error with the backup. I renamed the database file and when restarting Portainer the database was recreated. So far so good, but how do I import my 14 stacks from before now? I had an issue once where I manually searched for the compose files and rebuilt the stacks. Is there a better way maybe? All stacks are shown with limited access now. All the necessary compose files are in the right place, the new instance of Portainer just does not know about them.

Many thanks for any help.

Regards,
Thomas.

[Nick-Portainer]

Hello @Twiederh Are you storing your Portainer data on an NFS/CIFS/Network share?

[Twiederh]

No, it is stored in a volume in a local SSD.

[Nick-Portainer]

Can you please provide more details regarding your environment and versions?

[Twiederh]

The environment is running in an LXC Container based on Debian 12 on a Proxmox host. The Portainer Version is 2.33.0, Business Edition. The VM has 4vCPUs, 12Gig of Memory and 80Gig of diskspace on a WD RED NVME SSD. The latest versions of Debian and docker are installed (the Docker version is 28.3.3).

[Nick-Portainer]

Besides the database backup you found, were you also taking backups within the Portainer UI or API? If so, is this the backup you attempted to use, and did it fail to restore as well?