# 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:** 3

<div class="post-metadata">

**Author:** ![rups](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rups](https://forums.percona.com/u/rups)\
**Post date:** [June 20, 2024, 10:00pm UTC](https://forums.percona.com/t/unable-to-recover-pmm-failed-while-upgrading-2-41-2/31061/3 "2024-06-20T22:00:38Z")

</div>

> [@ademidoff](#):
>
> docker exec -it pmm-server supervisorctl status

# docker exec -it pmm-server supervisorctl status

alertmanager RUNNING pid 32, uptime 2 days, 3:08:58  
clickhouse RUNNING pid 15, uptime 2 days, 3:08:58  
dbaas-controller STOPPED Not started  
grafana FATAL Exited too quickly (process log may have details)  
nginx RUNNING pid 25, uptime 2 days, 3:08:58  
pmm-agent RUNNING pid 293, uptime 2 days, 3:08:57  
pmm-managed RUNNING pid 41, uptime 2 days, 3:08:58  
pmm-update-perform STOPPED Not started  
pmm-update-perform-init EXITED Jun 18 06:50 PM  
postgresql RUNNING pid 14, uptime 2 days, 3:08:58  
prometheus STOPPED Not started  
qan-api2 RUNNING pid 653, uptime 2 days, 3:08:54  
victoriametrics RUNNING pid 27, uptime 2 days, 3:08:58  
vmalert RUNNING pid 28, uptime 2 days, 3:08:58  
vmproxy RUNNING pid 33, uptime 2 days, 3:08:58

---

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