You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started a backup, and during the process, my MySQL server restarted. Since then, the backup process seems to be stuck in a loop. Restarting PMM (Percona Monitoring and Management) doesn't resolve the issue, and even after an update, the backup process continues to run.
Expected Results
Backup will be automatically canceled by pmm
Actual Results
Backup is stuck in a loop, even when I reboot the pmm server or delete the data of the backup on the storage server
Version
First detected on version 2.40.1 also happening in version 2.41.0
Steps to reproduce
Start the backup process, restart your mysql server and check if the backup process is looping
Relevant logs
No logs available since pmm doesn't recognize any error
Code of Conduct
I agree to follow Percona Community Code of Conduct
The text was updated successfully, but these errors were encountered:
Hello @MarvinStelter, thank you for report, we are aware about this problem but unfortunately didn't address it yet. You can track this issue progress in this ticket: https://perconadev.atlassian.net/browse/PMM-12474
For now the only way to get rid of hanged backup artifact is to connect to PMM internal database and remove record from artifacts table manually. 😔
Description
I started a backup, and during the process, my MySQL server restarted. Since then, the backup process seems to be stuck in a loop. Restarting PMM (Percona Monitoring and Management) doesn't resolve the issue, and even after an update, the backup process continues to run.
Expected Results
Backup will be automatically canceled by pmm
Actual Results
Backup is stuck in a loop, even when I reboot the pmm server or delete the data of the backup on the storage server
Version
First detected on version 2.40.1 also happening in version 2.41.0
Steps to reproduce
Start the backup process, restart your mysql server and check if the backup process is looping
Relevant logs
No logs available since pmm doesn't recognize any error
Code of Conduct
The text was updated successfully, but these errors were encountered: