Unable to register MySQL Replica to PMM Server

Percona Monitoring and Management (PMM)
1

Hi Team,

I have a PMM Server installed on a dedicated server using docker image and it is up and running:

[devops@va-pmm-server ~]$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e9ce18d18145 percona/pmm-server:2 “/opt/entrypoint.sh” 3 months ago Up 3 months (healthy) 80/tcp, 0.0.0.0:443->443/tcp pmm-server
[devops@va-pmm-server ~]$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
percona/pmm-server 2 46a93a43c8be 3 months ago 2.11GB

Now, I have a MySQL Replica Percona MySQL server which on version 5.7.40-43. I have installed the pmm client on this machine and trying to register the client node with the PMM server. I am using the following command :
sudo pmm-admin config --server-insecure-ssl --server=https://admin:admin@192.168.10.xx:443 db-replica-015
Unable to connect to PMM server by address: https://admin:admin@192.168.10.xx:443
Get https://https//admin:admin@192.168.10.xx:443/qan-api/ping: dial tcp: lookup https on 192.168.xx.xx:53: server misbehaving

  • Check if the configured address is correct.
  • If server is running on non-default port, ensure it was specified along with the address.
  • If server is enabled for SSL or self-signed SSL, enable the corresponding option.
  • You may also check the firewall settings.

I am able to do a telnet to PMM server’s host and port 443. We don’t have any SSL configuration on the replica server. There is no firewall settings as such. I had configured 2 databases server initially when I created the PMM servers ~3 months back. Not sure what is causing the issue this time.

2

This issue is resolved. Actually, I was running the command from a wrong server, I should be running the pmm-admin command from the pmm server instead of the db server. I executed the pmm-admin command from the PMM server and the I was able to register the db replica with the pmm server.