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

No Database or Host on MySQL Instances Overview

Hi, 
Good Day. Today I have installed pmm2 on docker. I have add client with below command. But no client showing on MySQL Instances Overview and PMM Home Page. Would you please help me on this. 
====================================
pmm-admin config --server-insecure-tls --server-url=https://admin:[email protected]:443
====================================
[[email protected] ~]# pmm-admin list
Service type  Service name         Address and port  Service ID
MySQL         sl-mysql             192.168.20.4:3306 /service_id/93186162-37e4-4378-99d8-887bde4df20c

Agent type                  Status     Agent ID                                        Service ID
pmm_agent                   Connected  /agent_id/f89daa2a-db97-453f-af22-82ba1a514140
node_exporter               Running    /agent_id/b8aeb19e-6b32-4829-91f1-9f5e7b4b5138
mysqld_exporter             Running    /agent_id/b3b5b98f-4dcd-4d47-ade3-f2503631359c  /service_id/93186162-37e4-4378-99d8-887bde4df20c
mysql_slowlog_agent         Waiting    /agent_id/1dd591ab-6673-4510-bda8-8574945c09f3  /service_id/93186162-37e4-4378-99d8-887bde4df20c
========================================



Answers

  • vaibhav_upadhyay40vaibhav_upadhyay40 Contributor Current User Role Mentor
    Hi @shohaghbd
    Basically you have to add monitoring service after configuring client with server.
    pmm-admin --config  
    and
    pmm-admin --add 

    --config = Connecting PMM Clients to the PMM Server
    https://www.percona.com/doc/percona-monitoring-and-management/2.x/manage/client-config.html

    --add = add MySQL service to monitoring 
    https://www.percona.com/doc/percona-monitoring-and-management/2.x/manage/client-mysql-metrics.html#

    did you face any issue while performing above steps?

  • steve.hoffmansteve.hoffman Percona Percona Staff Role Beginner
    Since pmm-admin list is showing a stuff running on the node I'm going to assume you DID run the pmm-admin add command.  One thing that can be tricky (which we are working fixing!) is that you can register a pmm-client to a server and make an outgoing TCP connection on 443 and get success BUT that registers the client with the server, fires up the exporters on the local ports of 4200x (42001,42002 in your case) of the client and instructs the PMM server to make a connection TO those ports on the client and that's usually where things break. I'd go to the host for your pmm server and see if you can telnet from 192.168.20.2 to 102.168.20.4 on port 42001 ('telnet 192.168.20.4 42001' gonna guess no) so you would need to look at UFW or iptables or another firewalls that could be interfering.  You can also get a better idea by looking at https://192.168.20.2/prometheus/targets to see if the "unhealthy" targets are complaining about no route to hose, connection timeout or context time exceeded...all of which point to networking getting in the way. 

    When we finish fixing we *should* be able to do everything over the client-->server tcp/443 connection so if you can register your node you WILL get data!  Don't have an ETA for a release yet but designs are all done, scope's defined, just need it worked in with the rest of the priorities (it's high, but not at the top). 
Sign In or Register to comment.

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