Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Pmm client can't connect to PMM server after upgrade

Description

  1. Install PMM server with authentication:

    nailya.kutlubaeva@bm-dell06-qanqa03:~/download$ ~/percona-qa/pmm-tests/pmm-framework.sh --setup --pmm-server-version=1.7.0 --pmm-server-user=qweqwe --pmm-server-password=1q2w3e

  2. Added PXC to monitoring

    ~/percona-qa/pmm-tests/pmm-framework.sh --addclient=pxc,3

  3. Checked QAN - everything works fine

  4. Updated to 1.8.0 via web (to 201802211555 build)

  5. Updated pmm-client to 1.8
    Result:

    nailya.kutlubaeva@bm-dell06-qanqa03:~/download$ sudo pmm-admin list Unable to connect to PMM server by address: 10.10.11.52 Looks like the server is password protected. Use 'pmm-admin config' to define server user and password. nailya.kutlubaeva@bm-dell06-qanqa03:~/download$ sudo cat /usr/local/percona/pmm-client/pmm.yml server_address: 10.10.11.52 client_address: 10.10.11.52 bind_address: 10.10.11.52 client_name: bm-dell06-qanqa03 server_user: qweqwe server_password: 1q2w3e server_insecure_ssl: true

How to test

None

How to document

None

Confluence content

mentioned on

Activity

Kamil Dziedzic 
February 23, 2018 at 2:41 PM

PMM client was not rebuild.

 

Can we get automatic tags on builds? So I could know what is in which build?

Nailya Kutlubaeva 
February 22, 2018 at 8:48 PM

Unfortunately, I've just reproduced the problem again with STR in description.

Roma Novikov 
February 22, 2018 at 9:46 AM

We  can try to use  

PMM Server   /managed/v1/version  (if it use Authentification ) 

https://sourcegraph.com/github.com/percona/pmm-client/-/blob/pmm/main.go#L151:16

Mykola Marzhan 
February 22, 2018 at 8:59 AM

root of the issue: redirect to grafana home page

Nailya Kutlubaeva 
February 21, 2018 at 9:51 PM

I've just reproduced the bug on ami

Done

Details

Assignee

Reporter

Priority

Fix versions

Affects versions

Created February 21, 2018 at 6:40 PM
Updated March 6, 2024 at 7:51 AM
Resolved February 26, 2018 at 4:08 PM

Flag notifications