Issues

Select view

Select search mode

 
50 of 81

"Failed to get PMM Server parameter" after config.

Done

Description

With the pmm2-client version 2.2 we have this issue:

 

After running `pmm-admin config` i still get the following error:

 

The client is registered in the PMM server and the config exists. I also checked the logs and the config file, nothing shows any problems.

 

Does anyone have a solution for this issue?

How to test

None

How to document

None

Smart Checklist

Details

Assignee

Reporter

Priority

Components

Fix versions

Affects versions

Environment

The server is running in a docker container on Debian Buster. In front of the server, we have an Nginx proxy with a let's encrypt certificate.

The client is directly installed on Debian Buster and we run Percona server 5.7.28.

Smart Checklist

Created January 27, 2020 at 8:58 AM
Updated March 6, 2024 at 4:55 AM
Resolved May 12, 2021 at 12:06 PM

Activity

Dávid MikušMay 12, 2021 at 12:06 PM

Proper error message was already done in another issue.

Dávid MikušMay 5, 2021 at 2:29 PM

I tested with pmm 2.16 and if pmm-agent is set up, but not connected to pmm-server.

Is it enough?

Lalit ChoudharyFebruary 16, 2021 at 12:37 PM

a connection from pmm-client to mysql via proxy , working fix explain here: 

https://forums.percona.com/t/unable-to-setup-proxy-between-pmm-client-and-server/8443/3

Guido LovaSeptember 21, 2020 at 1:47 PM

Hello,

i have got the same issue. Installed server in k8s and trying to configure the first client but after registration that happens successfully i receive always "Failed to get PMM Server parameters from local pmm-agent: pmm-agent is running, but not set up.
Please run `pmm-admin config` with --server-url flag." 

any updates ?

thank you 

Mattia MartinelloJuly 31, 2020 at 7:10 AM

I installed Percona PMM 2 on Docker with a Nginx proxy on top and I can correctly access to the web interface at https://pmm.my.domain (with a trusted SSL certificate).

I installed the pmm2-client version 2.9.0 and I'm having the same problem:

 

 

 

 

The same happens even if I try to setup PMM Agent on the HTTP port of the Docker container (so skipping Nginx), so the problem is not Nginx.