Not the answer you need?
Register and ask your own question!

pmm-client cannot communicate server

liangyu5017liangyu5017 ContributorInactive User Role Novice
pmm-client:172.26.0.149

pmm-server::172.26.0.135

run wget https://172.26.0.149:42000/metrics --no-check-certificate on pmm-client:

- https://172.26.0.149:42000/metrics
Connecting to 172.26.0.149:42000... connected.
WARNING: cannot verify 172.26.0.149’s certificate, issued by “/O=PMM Client”:
Unable to locally verify the issuer’s authority.
HTTP request sent, awaiting response... 401 Unauthorized
Authorization failed.



and netstat -antl|grep 42000

tcp 0 0 172.26.0.149:42000 172.17.0.1:46776 SYN_RECV
tcp 0 0 172.26.0.149:42000 172.17.0.1:46766 SYN_RECV
tcp 0 0 172.26.0.149:42000 172.17.0.1:46768 SYN_RECV
tcp 0 0 172.26.0.149:42000 172.17.0.1:46774 SYN_RECV

why connected to 172.17.0.1?



what should i do now

Comments

  • Michael CoburnMichael Coburn Principal Architect, Percona Percona Staff Role
    Hi liangyu5017
    I'm not positive but is this perhaps related to the docker networking configuration, is this how PMM server NAT's itself out?
  • liangyu5017liangyu5017 Contributor Inactive User Role Novice
    Thank you. It has been solved. There is no automatic firewall rule after starting docker
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.