# Unable to recover pmm failed while upgrading 2.41.2

**URL:** <https://forums.percona.com/t/unable-to-recover-pmm-failed-while-upgrading-2-41-2/31061>\
**Category:** Percona Monitoring and Management (PMM)\
**Tags:** pmm\
**Created:** [June 17, 2024, 8:58pm UTC](https://forums.percona.com/t/unable-to-recover-pmm-failed-while-upgrading-2-41-2/31061 "2024-06-17T20:58:37Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ademidoff](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ademidoff/32/14234_2.png) [@ademidoff](https://forums.percona.com/u/ademidoff)\
**Post date:** [June 21, 2024, 4:38pm UTC](https://forums.percona.com/t/unable-to-recover-pmm-failed-while-upgrading-2-41-2/31061/6 "2024-06-21T16:38:02Z")

</div>

> [@rups](#):
>
> Connecting to DB” dbtype=sqlite3

I see Grafana tries to connect to sqlite3 database and fails. What version of PMM Server did you migrate from?

Please note that recent versions of PMM Server use a PostgreSQL database for persistence. Sqlite3 won’t work.

Can it be that you mounted your own `grafana.ini` config file to the container? If that is the case, please check this [thread](https://forums.percona.com/t/after-upgrading-from-2-41-1-to-2-41-2-postgresql-db-grafana-db-is-empty-inside-pmm-server-container/30195/13)

Alex

---

_[View the full topic](https://forums.percona.com/t/unable-to-recover-pmm-failed-while-upgrading-2-41-2/31061)._