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

**URL:** <https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126>\
**Category:** PMM 1.x\
**Created:** [October 4, 2016, 3:39pm UTC](https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126 "2016-10-04T15:39:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexh](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@alexh](https://forums.percona.com/u/alexh)\
**Post date:** [October 4, 2016, 3:39pm UTC](https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126/1 "2016-10-04T15:39:59Z")

</div>

Hi,

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.

Thanks!  
A.

* * *

[root@xxx-mdb03 mysql]# pmm-admin remove --all --force  
OK, 1 services were removed.  
[root@xxx-mdb03 mysql]# pmm-admin list  
pmm-admin 1.0.4

PMM Server | 172.30.140.10:8080  
Client Name | xxx-mdb03  
Client Address | 172.30.140.85  
Service manager | linux-systemd

* * *

SERVICE TYPE NAME CLIENT PORT RUNNING DATA SOURCE OPTIONS

* * *

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

---

<div class="post-metadata">

**Author:** ![weber](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@weber](https://forums.percona.com/u/weber)\
**Post date:** [October 5, 2016, 2:41am UTC](https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126/2 "2016-10-05T02:41:11Z")

</div>

Hello,

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 [url][http://server/consul/[/url]](http://server/consul/%5B/url%5D) 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.

---

<div class="post-metadata">

**Author:** ![alexh](https://avatars.discourse-cdn.com/v4/letter/a/6f9a4e/32.png) [@alexh](https://forums.percona.com/u/alexh)\
**Post date:** [October 5, 2016, 3:28am UTC](https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126/3 "2016-10-05T03:28:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![weber](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@weber](https://forums.percona.com/u/weber)\
**Post date:** [October 5, 2016, 7:30am UTC](https://forums.percona.com/t/pmm-admin-remove-all-force-not-removing-mysql-queries/5126/4 "2016-10-05T07:30:33Z")

</div>

Great!

The next release will detect orphaned services on either local or remote side and the command “repair” will do the cleanup.