pmm-admin add mysql not working...

marciomarcio ContributorActive Member Contributor
Hello !! how are you doing ?
I switch the pmm v1 to new pmm v2, and I can't add the monitoring for mysql with pmm-admin (before working fine with pmm v1). I tried a lot of options and still getting the error for dial tcp connection.  I have running the mysql server with the default port (3306).

I believe this issue may have relation with https://jira.percona.com/browse/PMM-4782

I appreciate any help in advance!! Thank you.

# pmm-admin list
Service type  Service name         Address and port  Service ID

Agent type                  Status     Agent ID                                        Service ID
pmm_agent                   Connected  /agent_id/0488982d-c64a-4076-a53a-6de3acc6f2a3 
node_exporter               Running    /agent_id/fbc96f99-0ad7-403c-80ac-1abac01e2d1e


# pmm-admin add mysql --username=pmm  --password=password --service-name=araguaia 127.0.0.1:3306 --debug
DEBUG 2020-04-03 17:14:26.408993096Z: POST /local/Status HTTP/1.1
Host: 127.0.0.1:7777
User-Agent: Go-http-client/1.1
Content-Length: 3
Accept: application/json
Content-Type: application/json
Accept-Encoding: gzip

{}

DEBUG 2020-04-03 17:14:26.413423518Z: HTTP/1.1 200 OK
Content-Length: 449
Content-Type: application/json
Date: Fri, 03 Apr 2020 17:14:26 GMT
Grpc-Metadata-Content-Type: application/grpc

{"agent_id":"/agent_id/0488982d-c64a-4076-a53a-6de3acc6f2a3","runs_on_node_id":"/node_id/0babb77a-42d9-4f00-9171-5e3bf289e589","server_info":{"url":"https://root:[email protected]:443/","insecure_tls":true,"connected":true,"version":"2.4.0"},"agents_info":[{"agent_id":"/agent_id/fbc96f99-0ad7-403c-80ac-1abac01e2d1e","agent_type":"NODE_EXPORTER","status":"RUNNING"}],"config_filepath":"/usr/local/percona/pmm2/config/pmm-agent.yaml"}
DEBUG 2020-04-03 17:14:26.414132693Z: POST /local/Status HTTP/1.1
Host: 127.0.0.1:7777
User-Agent: Go-http-client/1.1
Content-Length: 3
Accept: application/json
Content-Type: application/json
Accept-Encoding: gzip

{}

DEBUG 2020-04-03 17:14:26.415052048Z: HTTP/1.1 200 OK
Content-Length: 449
Content-Type: application/json
Date: Fri, 03 Apr 2020 17:14:26 GMT
Grpc-Metadata-Content-Type: application/grpc

{"agent_id":"/agent_id/0488982d-c64a-4076-a53a-6de3acc6f2a3","runs_on_node_id":"/node_id/0babb77a-42d9-4f00-9171-5e3bf289e589","server_info":{"url":"https://root:[email protected]:443/","insecure_tls":true,"connected":true,"version":"2.4.0"},"agents_info":[{"agent_id":"/agent_id/fbc96f99-0ad7-403c-80ac-1abac01e2d1e","agent_type":"NODE_EXPORTER","status":"RUNNING"}],"config_filepath":"/usr/local/percona/pmm2/config/pmm-agent.yaml"}
DEBUG 2020-04-03 17:14:26.415637609Z: POST /v1/management/MySQL/Add HTTP/1.1
Host: pmm.server:443
User-Agent: Go-http-client/1.1
Content-Length: 302
Accept: application/json
Authorization: Basic dW5pbGE6c2VuaGFtdWl0b3NlY3JldGEyMDE4
Content-Type: application/json
Accept-Encoding: gzip

{"node_id":"/node_id/0babb77a-42d9-4f00-9171-5e3bf289e589","service_name":"araguaia","address":"127.0.0.1","port":3306,"pmm_agent_id":"/agent_id/0488982d-c64a-4076-a53a-6de3acc6f2a3","username":"pmm","password":"password","qan_mysql_slowlog":true,"max_slowlog_file_size":"0"}

DEBUG 2020-04-03 17:14:26.626416737Z: HTTP/1.1 400 Bad Request
Transfer-Encoding: chunked
Trailer: Grpc-Trailer-Content-Type
Content-Type: application/json
Date: Fri, 03 Apr 2020 17:14:26 GMT
Server: nginx

be
{"error":"Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.","code":9,"message":"Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused."}
0


DEBUG 2020-04-03 17:14:26.626612647Z: Result: <nil>                               
DEBUG 2020-04-03 17:14:26.626661767Z: Error: &my_sql.AddMySQLDefault{_statusCode:400, Payload:(*my_sql.AddMySQLDefaultBody)(0xc0003edb80)}
Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.
#




Answers

  • alexey.palazhchenkoalexey.palazhchenko PMM Tech Lead Percona
    pmm-admin add mysql --username=pmm  --password=password --service-name=araguaia 127.0.0.1:3306 --debug
    In that command both "araguaia" and "127.0.0.1:3306" are service names.
    pmm-admin add mysql --help
    usage: pmm-admin add mysql [<flags>] [<name>] [<address>]
    
    Add MySQL to monitoring
    
    Flags:
    [...]
          --service-name=NAME        Service name (overrides positional argument)
          --host=HOST                Service hostname or IP address (overrides positional argument)
          --port=PORT                Service port number (overrides positional argument)
    [...]
    Positional arguments:
      [<name>]     Service name (autodetected default: mini-mysql)
      [<address>]  MySQL address and port (default: 127.0.0.1:3306)
    "pmm-admin add mysql --username=pmm  --password=password araguaia 127.0.0.1:3306" should work.
  • marciomarcio Contributor Active Member Contributor

    The error still the same, I have tested with this commands:

    # pmm-admin add mysql --username=pmm  --password=password araguaia 127.0.0.1:3306
    Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.

    # pmm-admin add mysql --username=pmm  --password=password araguaia IP_ADDRESS_V4:3306
    Connection check failed: dial tcp IP_ADDRESS_V4:3306: connect: connection refused.




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.