# PMM server cannot collect metrics from a client **URL:** \ **Category:** PMM 1.x\ **Created:** [February 18, 2018, 3:08am UTC](https://forums.percona.com/t/pmm-server-cannot-collect-metrics-from-a-client/6201 "2018-02-18T03:08:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![PavelZeger](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@PavelZeger](https://forums.percona.com/u/PavelZeger)\ **Post date:** [February 18, 2018, 3:08am UTC](https://forums.percona.com/t/pmm-server-cannot-collect-metrics-from-a-client/6201/1 "2018-02-18T03:08:10Z")
Hi. I have Ubuntu 14.04. I installed PMM server via Docker and running up to 10 client successfully anc get all metrics from Percona Server 5.6. I also cannot collect metrics from one Percona XtraDB Cluster and Percona server after client installation. I have telnet from the PMM server to clients and from clients to PMM server. There are ouputs from pmm-admin: pmm-admin list pmm-admin 1.5.2 PMM Server | [az] Client Name | [az] Client Address | [az] Service Manager | linux-upstart * * * SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS * * * mysql:queries [az] - YES root:_**@unix(/var/run/mysqld/mysqld.sock) query\_source=slowlog, query\_examples=true linux:metrics [az] 42000 YES - mysql:metrics [az] 42002 YES root:**_@unix(/var/run/mysqld/mysqld.sock) pmm-admin check-network PMM Network Status Server Address | [server] Client Address | [server] [LIST] [_]System Time NTP Server ([0.pool.ntp.org](http://0.pool.ntp.org)) | 2017-12-17 09:59:04 +0000 UTC PMM Server | 2017-12-17 09:59:03 +0000 GMT PMM Client | 2017-12-17 09:43:31 +0000 UTC PMM Server Time Drift | OK PMM Client Time Drift | 933s Time is out of sync. Please make sure the client time is correct to see the metrics. PMM Client to PMM Server Time Drift | 932s Time is out of sync. Please make sure the server time is correct to see the metrics. [/LIST] [LIST] [_]Connection: Client → Server [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_]------- SERVER SERVICE STATUS [_]------- Consul API OK Prometheus API OK Query Analytics API OK [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] Connection duration | 271.3088ms Request duration | 276.327ms Full round trip | 547.6358ms [LIST] [_]Connection: Client ← Server [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_] [LIST] [_]---------- ----------------- ------- ---------- --------- SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD [_]---------- ----------------- ------- ---------- --------- linux:metrics [server][server]:42000 DOWN YES - mysql:metrics [server][server]:42002 DOWN YES - [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] [/LIST] When an endpoint is down it may indicate that the corresponding service is stopped (run ‘pmm-admin list’ to verify). If it’s running, check out the logs /var/log/pmm-_.log When all endpoints are down but ‘pmm-admin list’ shows they are up and no errors in the logs, check the firewall settings whether this system allows incoming connections from server to address:port in question. Also you can check the endpoint status by the URL: [http://[server]/prometheus/targets] Logs time=“2017-12-17T09:23:20Z” level=info msg=“Starting node\_exporter (version=0.14.0+percona.2, branch=master, revision=8ea8a4521f8f42d581847ee3d271dbb2a1fe8146)” source=“node\_exporter.go:142” time=“2017-12-17T09:23:20Z” level=info msg=“Build context (go=go1.9.2, user=jenkins@os-centos-6-x64-2404, date=20171130-13:11:09)” source=“node\_exporter.go:143” time=“2017-12-17T09:23:20Z” level=info msg=“Enabled collectors:” source=“node\_exporter.go:162” time=“2017-12-17T09:23:20Z” level=info msg=" - meminfo" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - netdev" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - netstat" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - time" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - loadavg" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - filefd" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - filesystem" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - stat" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - uname" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - vmstat" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=" - diskstats" source=“node\_exporter.go:164” time=“2017-12-17T09:23:20Z” level=info msg=“Starting HTTPS server of 10.53.7.20:42000 …” source=“server.go:106” 2017/12/17 09:25:29 http: TLS handshake error from 10.53.7.20:60804: tls: first record does not look like a TLS handshake 2017/12/17 09:43:32 http: TLS handshake error from 10.53.7.20:60840: tls: first record does not look like a TLS handshake time=“2017-12-17T09:23:22Z” level=info msg=“Starting mysqld\_exporter (version=1.5.2, branch=master, revision=c5b2f15a2b2b46eb53192c6aded039c90f406733)” source=“mysqld\_exporter.go:798” time=“2017-12-17T09:23:22Z” level=info msg=“Build context (go=go1.9.2, user=, date=)” source=“mysqld\_exporter.go:799” time=“2017-12-17T09:23:22Z” level=info msg=“HTTPS/TLS is enabled” source=“mysqld\_exporter.go:843” time=“2017-12-17T09:23:22Z” level=info msg=“Listening on 10.53.7.20:42002” source=“mysqld\_exporter.go:846” 2017/12/17 09:25:29 http: TLS handshake error from 10.53.7.20:47937: tls: first record does not look like a TLS handshake 2017/12/17 09:30:03 http: TLS handshake error from 10.53.7.20:47943: EOF 2017/12/17 09:43:32 http: TLS handshake error from 10.53.7.20:47973: tls: first record does not look like a TLS handshake [LIST] [_][LIST=1] [_]Version: percona-qan-agent 1.5.2\* [_]Basedir: /usr/local/percona/qan-agent_ [_]PID: 63403_ [_]API: 10.51.7.23/qan-api_ [_]UUID: f8b058d3e1c5470063e05fb7155207c1_ 2017/12/17 09:23:27.833911 main.go:163: Starting agent… 2017/12/17 09:23:27.834629 main.go:331: Agent is ready 2017/12/17 09:23:28.661498 main.go:204: API is ready [/LIST] [/LIST] ---
**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\ **Post date:** [February 20, 2018, 5:15am UTC](https://forums.percona.com/t/pmm-server-cannot-collect-metrics-from-a-client/6201/2 "2018-02-20T05:15:48Z")
Hello PavelZeger, are you still having this issue? In the first instance, I can share with you a couple of links that might help you track down your issues. If you run through these and don’t sort things, please post back… If you do manage to work out the problem, though, it would be good to hear how you fixed things! Thanks. [LIST] [_][url][https://www.percona.com/blog/2018/01/17/troubleshooting-percona-monitoring-and-management-pmm-metrics/[/url]](https://www.percona.com/blog/2018/01/17/troubleshooting-percona-monitoring-and-management-pmm-metrics/%5B/url%5D) [_][url][Percona Monitoring and Management](https://www.percona.com/doc/percona-monitoring-and-management/faq.html%5B/url%5D) [\*][url][https://www.percona.com/blog/2017/02/24/installing-percona-monitoring-and-management-pmm-for-the-first-time-2/[/url]](https://www.percona.com/blog/2017/02/24/installing-percona-monitoring-and-management-pmm-for-the-first-time-2/%5B/url%5D) [/LIST] ---
**Author:** ![PavelZeger](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@PavelZeger](https://forums.percona.com/u/PavelZeger)\ **Post date:** [March 22, 2018, 8:03am UTC](https://forums.percona.com/t/pmm-server-cannot-collect-metrics-from-a-client/6201/3 "2018-03-22T08:03:19Z")
Hi. I still have this issues and now with three new servers with MariaDB cluster. I have ping from the container to each node and also telnet to 42000 and 42002. I also have telnet from each node to the default port 80 on PMM server. I checked firewall rules and we have permissions to inbound connections from PMM sever to clients. I also don’t have time drift between these servers. What can I do to monitor my Cluster?