Issues
- Upgrade to PMM3 Fails on Docker CommandsPMM-13870
- Unable to view metrics in PMM for PostgreSQL (/pgdata) and MongoDB (/data/db) mount points in the Disk Details dashboard when monitoring deployments via Everest (Sidecar Container Issue).PMM-13813
- Need to integrate pt-index-usage tool in PMM to identify duplicate and unused index reports.PMM-13811
- pmm-agent crashed at query.Fingerprint due to query including a column named "value"PMM-13807
- Dashboard "ProxySQL Instance Summary" -> "Queries Execution Time" shows values for multiple proxysql instances even though only one instance is selectedPMM-13799
- High CPU utilization by PMM agentPMM-13772Resolved issue: PMM-13772
- When using a non-default pg_stat_statements.max value, the calculated QPS displayed in QAN may be wrong.PMM-13694
- grpc: received message larger than maxPMM-13686Resolved issue: PMM-13686
- BY clicking on VMware link is getting re-directed to Page Not FoundPMM-13675
- [PMM2] ReplicaSet Summary does not show node that is downPMM-13655
- pmm-dump Binary Does Not Display Version InformationPMM-13654
- No data on some panels and charts on MongoDB dashboardsPMM-13647
- [QA] Verify all panels on MongoDB dashboardsPMM-13645Resolved issue: PMM-13645Nailya Kutlubaeva
- PMM has python vulnerabiltiesPMM-13639
- PMM QAN is Broken when Query having Explain KeywordPMM-13636
- Issues with Dashboard MongoDB Collections OverviewPMM-13635
- Install perl into pmm-client docker containerPMM-13626Resolved issue: PMM-13626talha.rizwan
- Query Analytics shows only "n/a" in Database & User Name filters (only for MySQL/MariaDB nodes)PMM-13609
- Mongodb_exporter uses more Memory with Mongo 8 than with Mongo 7PMM-13604Nurlan Moldomurov
- Mongodb_exporter has increasing memory usage with mongoDB cluster v8.0 and specific conditions setPMM-13602Resolved issue: PMM-13602
- Azure node metrics are not hitting PMM ServerPMM-13585
- Signout url to not redirect to id.percona.comPMM-13582
- QAN - invalid GetActionRequest.ActionId: value length must be at least 1 runesPMM-12784
- Alerts historyPMM-11901
24 of 24
Upgrade to PMM3 Fails on Docker Commands
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Details
Details
Assignee
Unassigned
UnassignedReporter
Jervin R
Jervin RPriority
Labels
Needs QA
Yes
Needs Doc
Yes
Affects versions
Environment
Ξ(uwe2) ~ → docker version
Client:
Version: 25.0.8
API version: 1.44
Go version: go1.22.7
Git commit: 0bab007
Built: Tue Feb 11 22:44:16 2025
OS/Arch: linux/amd64
Context: default
Server:
Engine:
Version: 25.0.8
API version: 1.44 (minimum version 1.24)
Go version: go1.22.7
Git commit: 71907ca
Built: Tue Feb 11 22:44:45 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.25
GitCommit: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc:
Version: 1.2.4
GitCommit: 6c52b3fc541fb26fe8c374d5f58112a0a5dbda66
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Smart Checklist
Smart Checklist
Created 4 hours ago
Updated 4 hours ago
Activity
Show:
Using instructions from https://docs.percona.com/percona-monitoring-and-management/3/pmm-upgrade/migrating_from_pmm_2.html
Ξ(uwe2) ~ → bash get-pmm3.sh -n pmm-server -b Gathering/downloading required components, this may take a moment Checking docker installation - installed. Created PMM Network: pmm-net Found Watchtower Token: Generated Watchtower Token: random-2025-03-16-235713 Pulling percona/pmm-server:3.0.0 Existing PMM Server found, renaming to pmm-server-2025-03-16-235735 pmm-server Backing up existing PMM Data Volume to -2025-03-16-235751 unknown shorthand flag: '2' in -2025-03-16-235751 See 'docker volume create --help'.
I tried without backup:
Ξ(uwe2) ~ → bash get-pmm3.sh -n pmm-server Gathering/downloading required components, this may take a moment Checking docker installation - installed. Found Watchtower Token: Generated Watchtower Token: random-2025-03-16-235811 Pulling percona/pmm-server:3.0.0 Existing PMM Server found, renaming to pmm-server-2025-03-16-235811 pmm-server Migrating PMM Server data from 2.x to 3.x pmm-server vmalert: stopped vmproxy: stopped postgresql: stopped grafana: stopped victoriametrics: stopped alertmanager: stopped qan-api2: stopped pmm-agent: stopped pmm-update-perform-init: stopped nginx: stopped pmm-managed: stopped clickhouse: stopped pmm-server Created PMM Data Volume: Starting PMM Server... docker: invalid spec: :/srv: empty section between colons. See 'docker run --help'.
Unable to reproduce as I lost my PMM install and started from scratch, but it looks like the shell script does not recognize when the PMM data volume is Type:bind.
+ backup_pmm_data ++ date +%F-%H%M%S + pmm_volume_archive=-2025-03-17-002328 + msg 'Backing up existing PMM Data Volume to -2025-03-17-002328' + echo -e 'Backing up existing PMM Data Volume to -2025-03-17-002328'