how can I delete the dashboard of the hosts that are no longer monitored

I have some hosts that are no longer used. I want to delete the dashboard of the hosts that are no longer monitored. What shoud i do? I tried this :
pmm-admin remove --all
pmm-admin purge linux:metrics --verbose

2018/11/07 15:26:50 request:

GET /qan-api/ping HTTP/1.1
Host: xx.xxx.xxx.xxx
User-Agent: Go-http-client/1.1
Authorization: Basic YWRtaW46YWRtaW4=
Accept-Encoding: gzip

2018/11/07 15:26:50 response:
< HTTP/1.1 200 OK
< Access-Control-Allow-Headers: Content-Type,Authorization
< Access-Control-Allow-Methods: GET,PUT,POST,DELETE
< Access-Control-Allow-Origin: *
< Cache-Control: no-store
< Connection: keep-alive
< Content-Type: text/plain; charset=utf-8
< Date: Wed, 07 Nov 2018 07:26:50 GMT
< Pragma: no-cache
< Server: nginx
< Strict-Transport-Security: max-age=63072000; includeSubDomains
< X-Content-Type-Options: nosniff
< X-Frame-Options: DENY
< X-Percona-Qan-Api-Version: 1.14.1-1809060744.89a7875
< X-Xss-Protection: 1; mode=block
< Content-Length: 0
<
<
2018/11/07 15:26:50 request:

GET /v1/status/leader HTTP/1.1
Host: xx.xxx.xxx.xxx
User-Agent: Go-http-client/1.1
Authorization: Basic YWRtaW46YWRtaW4=
Accept-Encoding: gzip

2018/11/07 15:26:50 response:
< HTTP/1.1 200 OK
< Content-Length: 16
< Connection: keep-alive
< Content-Type: application/json
< Date: Wed, 07 Nov 2018 07:26:50 GMT
< Server: nginx
< X-Remote-Ip: xx.xxx.xxx.xxx
< X-Server-Time: Wednesday, 07-Nov-2018 07:26:50 GMT
<
< “127.0.0.1:8300”
2018/11/07 15:26:50 request:

GET /qan-api/ping HTTP/1.1
Host: xx.xxx.xxx.xxx
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

2018/11/07 15:26:50 response:
< HTTP/1.1 401 Unauthorized
< Content-Length: 188
< Connection: keep-alive
< Content-Type: text/html
< Date: Wed, 07 Nov 2018 07:26:50 GMT
< Server: nginx
< Www-Authenticate: Basic realm=“on”
<
<
< 401 Authorization Required
<
<

401 Authorization Required


<
nginx
<
<
<
2018/11/07 15:26:50 request:

GET /v1/catalog/node/ic-mysql-notice-master01 HTTP/1.1
Host: xx.xxx.xxx.xxx
User-Agent: Go-http-client/1.1
Authorization: Basic YWRtaW46YWRtaW4=
Accept-Encoding: gzip

2018/11/07 15:26:50 response:
< HTTP/1.1 200 OK
< Content-Length: 184
< Connection: keep-alive
< Content-Type: application/json
< Date: Wed, 07 Nov 2018 07:26:50 GMT
< Server: nginx
< X-Consul-Index: 292420
< X-Consul-Knownleader: true
< X-Consul-Lastcontact: 0
< X-Remote-Ip: xx.xxx.xxx.xxx
< X-Server-Time: Wednesday, 07-Nov-2018 07:26:50 GMT
<
< {“Node”:{“ID”:“”,“Node”:“ic-mysql-notice-master01”,“Address”:“xx.xxx.xxx.xxx”,“Datacenter”: “” ,“TaggedAddresses”:null,“Meta”:null,“CreateInde x”: 253953,“ModifyIndex”:253953},“Services”:{}}
2018/11/07 15:26:50 request:

DELETE /prometheus/api/v1/series?match={job=“linux”,instance=“ic-mysql-notice-master01”} HTTP/1.1
Host: xx.xxx.xxx.xxx
User-Agent: Go-http-client/1.1
Authorization: Basic YWRtaW46YWRtaW4=
Accept-Encoding: gzip

2018/11/07 15:26:50 response:
< HTTP/1.1 500 Internal Server Error
< Access-Control-Allow-Headers: Accept, Authorization, Content-Type, Origin
< Access-Control-Allow-Methods: GET, OPTIONS
< Access-Control-Allow-Origin: *
< Access-Control-Expose-Headers: Date
< Connection: keep-alive
< Content-Type: application/json
< Date: Wed, 07 Nov 2018 07:26:50 GMT
< Server: nginx
<
< {“status”:“error”,“errorType”:“internal”,“error “:” not implemented”}
panic: interface conversion: interface {} is nil, not map[string]interface {}

goroutine 1 [running]:
github.com/percona/pmm-client/pmm.(*Admin).PurgeMetrics(0xc288c0, 0x7ffddd4f78a0, 0xd, 0xc42019cb28, 0xc42014bb48, 0x81da62)
/tmp/go/src/github.com/percona/pmm-client/pmm/pmm.go:431 +0x5a4
main.glob…func43(0xc225a0, 0xc42011ae80, 0x1, 0x2)
/tmp/go/src/github.com/percona/pmm-client/pmm-admin.go:1295 +0xd1
github.com/percona/pmm-client/vendor/github.com/spf13/cobra.(*Command).execute(0xc225a0, 0xc42011ae40, 0x2, 0x2, 0xc225a0, 0xc42011ae40)
/tmp/go/src/github.com/percona/pmm-client/vendor/github.com/spf13/cobra/command.go:654 +0x2a2
github.com/percona/pmm-client/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc1cde0, 0xc42014bdb0, 0x49ba52, 0x0)
/tmp/go/src/github.com/percona/pmm-client/vendor/github.com/spf13/cobra/command.go:729 +0x2d4
github.com/percona/pmm-client/vendor/github.com/spf13/cobra.(*Command).Execute(0xc1cde0, 0xc460aa, 0x9524d8)
/tmp/go/src/github.com/percona/pmm-client/vendor/github.com/spf13/cobra/command.go:688 +0x2b
main.main()
/tmp/go/src/github.com/percona/pmm-client/pmm-admin.go:1563 +0x13b1

thank you~

Hi mengweike

What versions of pmm-client, PMM Server are you running?

Sorry mengweike

I see 1.14.1 on the Server:

< X-Percona-Qan-Api-Version: 1.14.1-1809060744.89a7875

Can you upgrade to 1.16.0 and let us know if the problem remains? If so we’d appreciate a bug report to [url]http://jira.percona.com/browse/PMM[/url]

Thanks!

Hi mengweike

roma.novikov brought to my attention that we fixed a similar purge bug in 1.15.0, definitely upgrade and let us know if problem persists. Thanks

[url][PMM-2845] pmm-admin purge causes client to panic - Percona JIRA

When i upgraed 1.17.0 ,the problem is solved… Thanks.

You’re welcome mengweike !