The current PMM client is a Virtual Appliance on vSphere running 2.21.0 of PMM.
[root@localhost access]# /usr/sbin/percona-qan-api2 --data-retention=30 --debug --trace
stdlog: qan-api2 v2.21.0.
INFO[2021-09-20T14:01:17.038+00:00]qan-api2/main.go:284 main.main Log level: trace.
stdlog: dsn: clickhouse://127.0.0.1:9000?database=pmm&block_size=10000&pool_size=2
stdlog: Migrations: Dirty database version 9. Fix and force version.
[root@localhost access]#
[root@localhost access]# clickhouse-client --query “select * from pmm.schema_migrations”
1 1 1600776273056694360
1 0 1600776273075425791
2 1 1600776273076725910
2 0 1600776273116303743
3 1 1600776273117564041
3 0 1600776273156214628
4 1 1600776273157073358
4 0 1600776273181985508
5 1 1600776273182842458
5 0 1600776273193594158
6 1 1600776273194365739
6 0 1600776273203387813
7 1 1620132085016538511
7 0 1620132085071669360
8 1 1620132085072878986
8 0 1620132085173742781
9 1 1631874203339757424
[root@localhost access]#
thre result of the supervisorctl command is :
[root@localhost ~]# supervisorctl status
alertmanager RUNNING pid 1105, uptime 1:14:25
clickhouse RUNNING pid 1099, uptime 1:14:25
cron RUNNING pid 1102, uptime 1:14:25
dashboard-upgrade EXITED Sep 20 11:44 AM
dbaas-controller STOPPED Not started
grafana RUNNING pid 1100, uptime 1:14:25
nginx RUNNING pid 1101, uptime 1:14:25
pmm-agent RUNNING pid 1109, uptime 1:14:25
pmm-managed RUNNING pid 1174, uptime 1:14:19
pmm-update-perform STOPPED Not started
postgresql RUNNING pid 1098, uptime 1:14:25
prometheus STOPPED Not started
qan-api2 STARTING
victoriametrics RUNNING pid 1103, uptime 1:14:25
vmalert RUNNING pid 1104, uptime 1:14:25
[root@localhost ~]#