# After upgrading Pmm from 2.44 to 3.4 QAN services went down

**URL:** <https://forums.percona.com/t/after-upgrading-pmm-from-2-44-to-3-4-qan-services-went-down/39446>\
**Category:** Uncategorized\
**Created:** [September 24, 2025, 9:14am UTC](https://forums.percona.com/t/after-upgrading-pmm-from-2-44-to-3-4-qan-services-went-down/39446 "2025-09-24T09:14:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![suman\_8864](https://avatars.discourse-cdn.com/v4/letter/s/13edae/32.png) [@suman\_8864](https://forums.percona.com/u/suman_8864)\
**Post date:** [September 24, 2025, 9:14am UTC](https://forums.percona.com/t/after-upgrading-pmm-from-2-44-to-3-4-qan-services-went-down/39446/1 "2025-09-24T09:14:45Z")

</div>

Hi

We upgraded PMM from 2.44 to 3.4 in Rocky9 server, After that all services came up but QAN services went down, Upon checking docker logs identified below error.

”Migrations: Dirty database version 18. Fix and force version.”

Any idea how to fix this issue?

Thanks,

Suman.A

---

<div class="post-metadata">

**Author:** ![Yunus](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus/32/6430_2.png) [@Yunus](https://forums.percona.com/u/Yunus)\
**Post date:** [October 2, 2025, 2:42pm UTC](https://forums.percona.com/t/after-upgrading-pmm-from-2-44-to-3-4-qan-services-went-down/39446/2 "2025-10-02T14:42:32Z")

</div>

> [@suman\_8864](#):
>
> ”Migrations: Dirty database version 18. Fix and force version.”

You might want to check this post with similar error

> [@PMM upgrade from 2.44.1 to 3.2.0 - Migrations: Dirty database version 18](https://forums.percona.com/t/pmm-upgrade-from-2-44-1-to-3-2-0-migrations-dirty-database-version-18/38588):
>
> Hello there, As we plan to upgrade MySQL to version 8.4, we also need to upgrade PMM as MySQL 8.4 has been supported since PMM 3.2. As described here [Migrate PMM 2 to PMM 3 - Percona Monitoring and Management](https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/migrating_from_pmm_2.html), we first updated PMM from 2.43.1 to 2.44.1 (server and clients) and everything works fine. Now when we try to upgrade PMM server to version 3.2.0, the container has a healthy status but when we look at the QAN log we see the following messages time="2025-07-07T12:43:11.585+00:00" level…