I’m running version 2.3.5, but I’m then struggling to get the pmm-agent to add MySQL monitoring service for a MySQL database that’s hosted in the same server but on another container.
Thanks when I run that command to create the docker container, I know the --rm flag is supposed to indicate short-lived container. When I execute that command to create the container, it’s only running while I have my terminal open, as soon as I exit the terminal. The container is stopped, how do i get it to continiously run? As I plan to have it keep running so I can monitor the MySQL database that’s hosted on another container?
Any idea what I’m doing wrong? My server is hosted in AWS, I tried using the ipv4 ip-address and the private one but neither works and give timeout error. I recalled your old percona monitoring software had an option to bind-address, which I don’t see as an option.
it seems your pmm-client container cannot reach your mysql server host/port. Are you sure everything is in the same docker network? do you have anything controlling access to your mysql host and port 3308?
Yesn when I run docker network inspect the network id from the container mysql database is running on and the container pmm-client is runing on both return the same network id. I don’t have anything else controlling access to mysql host and port 3308.
Connection check failed: dial tcp: lookup mysql3 on 172.XX.X.X:53: no such host.
“No such host” means that the docker dns is not being able to resolve “mysql3” as hostname, so there’s something wrong with it.
Can you share the exact commands you used to deploy these two containers? Have you also tried connecting from the pmm-client to the (docker) host and port 3308?