Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-2639

mysql:metrics does not work on Ubuntu 18.04

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Pending Release
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.13.0
    • Component/s: PMM Client
    • Labels:
      None

      Description

      I'm working on pmm configuration for my needs and faced an issue.

      So I successfully got pmm-client up and running on Ubuntu 16.04.

      But now I'm trying to run it on Ubuntu 18.04 and "mysql:metrics" is not working there.

      Below are some details.

      $ cat /etc/lsb-release
      DISTRIB_ID=Ubuntu
      DISTRIB_RELEASE=18.04
      DISTRIB_CODENAME=bionic
      DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"

       

      $ sudo pmm-admin check-network
      PMM Network Status
      
      Server Address | localhost:8080
      Client Address | 172.17.0.1
      
      * System Time
      NTP Server (0.pool.ntp.org) | 2018-06-19 12:23:21 +0000 UTC
      PMM Server | 2018-06-19 12:23:21 +0000 GMT
      PMM Client | 2018-06-19 12:23:21 +0000 UTC
      PMM Server Time Drift | OK
      PMM Client Time Drift | OK
      PMM Client to PMM Server Time Drift | OK
      
      * Connection: Client --> Server
      -------------------- -------
      SERVER SERVICE STATUS
      -------------------- -------
      Consul API OK
      Prometheus API OK
      Query Analytics API OK
      
      Connection duration | 133.812µs
      Request duration | 193.858057ms
      Full round trip | 193.991869ms
      
      
      * Connection: Client <-- Server
      -------------- ------------------- ----------------- ------- ---------- ---------
      SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD
      -------------- ------------------- ----------------- ------- ---------- ---------
      linux:metrics <instance_name> 172.17.0.1:42000 OK YES -
      mysql:metrics <instance_name> 172.17.0.1:42002 DOWN - -
      
      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://localhost:8080/prometheus/targets
      $ sudo pmm-admin list
      pmm-admin 1.11.0
      
      PMM Server | localhost:8080
      Client Name | RDS
      Client Address | 172.17.0.1
      Service Manager | linux-systemd
      
      -------------- ------------------- ----------- -------- --------------------------------------------------------------------------- ---------------------------------------------
      SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS
      -------------- ------------------- ----------- -------- --------------------------------------------------------------------------- ---------------------------------------------
      mysql:queries <instance_name> - YES pmm:***@tcp(<db_instance_url>:3306) query_source=perfschema, query_examples=true
      linux:metrics <instance_name> 42000 YES -
      mysql:metrics <instance_name> 42002 NO pmm:***@tcp(<db_instance_url>:3306)
      

       

      From pmm-mysql-metrics-42002.log:

      time="2018-06-19T12:19:43Z" level=fatal msg="failed reading ini file: open .my.cnf: no such file or directory" source="mysqld_exporter.go:300"

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                atymoshyk Andrii Tymoshyk
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour, 55 minutes
                  1d 1h 55m