Emergency

Unable to start mysql:queries

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to start mysql:queries

    Hello,

    I tried many things but I can't start mysql:queries.
    linux and mysql metrics work as expected, but receiving below error when adding mysql:queries

    root # pmm-admin add mysql:queries
    Error adding MySQL queries: problem with agent registration on QAN API: exit status 1

    root # # pmm-admin check-network
    PMM Network Status

    Server Address | xxxxxxxxxxx
    Client Address | xxxxxxxxxxxxx

    * System Time
    NTP Server (0.pool.ntp.org) | 2017-09-29 10:54:30 +0000 UTC
    PMM Server | 2017-09-29 10:54:30 +0000 GMT
    PMM Client | 2017-09-29 10:54:30 +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 DOWN

    Connection duration | 31.077004ms
    Request duration | 32.748302ms
    Full round trip | 63.825306ms


    * Connection: Client <-- Server
    -------------- ------------------------ ------------------ ------- ---------- ---------
    SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD
    -------------- ------------------------ ------------------ ------- ---------- ---------
    linux:metrics XXXXXXXX xxxxxxxxx:42000 OK YES YES
    mysql:metrics YYYYYYY yyyyyyyyyyy:42002 OK YES YES

  • #2
    Hello,

    I have the same problem and would be interested in a solution as well.

    I am using
    pmm-client 1.3.1-1.jessie amd64 Percona Monitoring and Management Client

    in combination with and EC2 instance
    AMI ID PMM Server [2017-09-28 0152] (ami-c79e54be)


    Regards
    Michael

    Comment


    • #3
      Can you ssh into PMM Server instance and share the output of the following commands?

      Code:
      sudo df -h
      sudo ps ax
      sudo systemctl restart percona-qan-api
      sudo ps ax
      sudo systemctl status percona-qan-api
      sudo journalctl -u percona-qan-api

      Comment


      • #4
        I think I found what it's not working
        Looks like qan-api and orchestrator are now using different usernames and passwords
        The login information in /etc/percona-qan-api.conf is no longer valid

        Comment

        Working...
        X