Not the answer you need?
Register and ask your own question!

'pmm-admin remove --all --force' not removing mysql:queries

alexhalexh EntrantInactive User Role Beginner

I'm stuck in a situation where I can't remove a mysql:queries probe, the situation below persists.
I have tried to remove and reinstall pmm-client, no joy.

It seems as if the server is keeping information about the config and is handing it out to the client on first reconnect after re-install.

The workflow/use case that has initially broken this setup was an upgrade of the DB server from CentOS 6 to CentOS 7 with pmm-client re-installation.

Any advice on how I can get out of this trouble would be very much appreciated.


[[email protected] mysql]# pmm-admin remove --all --force
OK, 1 services were removed.
[[email protected] mysql]# pmm-admin list
pmm-admin 1.0.4

PMM Server |
Client Name | xxx-mdb03
Client Address |
Service manager | linux-systemd


mysql:queries xxx -mdb03 42001 NO root:***@unix(/var/run/mysqld/mysqld.sock) query_source=slowlog


  • weberweber Advisor Inactive User Role Beginner

    We will have 1.0.5 release the next week which detects broken installation client side or server side and allows to do a repair.

    In your case, I suggest to do the following: go to Consul web ui http://server/consul/ and deregister this particular service mysql:queries (42001) with alias "xxx-mdb03". After that `pmm-admin list` should not list it and you should be able to re-add.
  • alexhalexh Entrant Inactive User Role Beginner
    Thanks, you are a star! I couldn't remove just the service but had to remove the whole node, but it seems that we're back to normal now, thank you.
  • weberweber Advisor Inactive User Role Beginner

    The next release will detect orphaned services on either local or remote side and the command "repair" will do the cleanup.
This discussion has been closed.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.