Timeout when trying to configure pmm-client agent to the Percona Docker pmm-server image

Percona Monitoring and Management (PMM) PMM 2.x
#1

Hello

I have set up the Docker percona PMM image

PS C:\Windows\system32> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2d6bbf39bba3 percona/pmm-server:2 “/opt/entrypoint.sh” 25 seconds ago Up 22 seconds (healthy) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp pmm-server

:: Have installed the Percona client agent (on a centos 7 running Xtradb cluster 5.7)
[root@pxc01 ~]# yum install pmm2-client

[root@pxc01 ~]# pmm-admin --version
ProjectName: pmm-admin
Version: 2.14.0
PMMVersion: 2.14.0
Timestamp: 2021-01-28 12:36:39 (UTC)
FullCommit: cdf593c6774c3c239aaf22fff27e9e7aa1364a60

:; When running below command to configure an agent with the pmm server, i get timeout.
[root@pxc01 ~]# pmm-admin config --force --server-insecure-tls --server-url=https://admin:admin@172.17.0.2:443
Checking local pmm-agent status…
pmm-agent is running.
Registering pmm-agent on PMM Server…
Failed to register pmm-agent on PMM Server: Post “https://172.17.0.2:443/v1/management/Node/Register”: dial tcp 172.17.0.2:443: i/o timeout.

Any pointers would be most appreciated.

Respectfully
Manni

#2

Hi Manni,

Could you specify your client IP in the config command?

e.g.
pmm-admin config --force --server-insecure-tls --server-url=https://admin:admin@172.17.0.2:443 172.17.0.x generic pxc01

Screenshot_20210206_122957

2 Likes
#3

Hello Adivinho

Thank you for the reply.
pxc01 the ip is 172.42.42.101

So are you suggesting to use
pmm-admin config --force --server-insecure-tls --server-url=https://admin:admin@172.17.0.2:443 --client-address 172.42.42.101

Sorry I am a bit confused.

Respectfully

Manni

1 Like
#4

Usually Docker uses the default 172.17.0.0/16 subnet for container networking.
You may check your docker subnet by performing next commands

docker network ls
docker network inspect -f ‘{{range .IPAM.Config}}{{.Subnet}}{{end}}’ NETWORK

Screenshot_20210207_144244
Screenshot_20210207_1442441009×163 29.6 KB

If it has the default value then your PXC node (172.42.42.101) is out of a network range.
Also please notice that it’s a real IP address. The private network 172.x.x.x has the largest CIDR block 172.16.0.0/12

Screenshot_20210207_145148
Screenshot_20210207_1451481479×334 33.9 KB

1 Like
#5

Hello Advinho,

Below s the output. I thni I will need to re instantiate my cluster nodes with new ips.

PS C:\Users\user> docker network ls
NETWORK ID NAME DRIVER SCOPE
b82f722a45ea bridge bridge local
f7dfb9560eb6 host host local
dc38ebece7f3 none null local
PS C:\Users\user> docker network inspect -f ‘{{range .IPAM.Config}}{{.Subnet}}{{end}}’ b82f722a45ea
172.17.0.0/16

Respectfully
Manni

1 Like
#6

Hello

Below are the ip addr for node 1.

[root@pxc01 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:8a:fe:e6 brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic eth0
valid_lft 63069sec preferred_lft 63069sec
inet6 fe80::5054:ff:fe8a:fee6/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:72:65:33 brd ff:ff:ff:ff:ff:ff
inet 172.42.42.101/24 brd 172.42.42.255 scope global noprefixroute eth1
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe72:6533/64 scope link
valid_lft forever preferred_lft forever

Respectfully
Manni

1 Like