Is using a hostname supported instead of an ip? We have a mesos/marathon deploy so the server container does not have a dedicated ip, rather it is routed via haproxy. I can browse the server container fine but when I try and add via the client I get.
Unable to connect to PMM server by address: pmm-server.prdmesos..com
Even though the server is reachable it does not look to be PMM server.
Check if the configured address is correct.
I can also ping that address on pmm-server.prdmesos..com
$ ping pmm-server.prdmesos..com
PING pmm-server.prdmesos..com (10.1.202.165) 56(84) bytes of data.
Yes, hostname is supported as client address.
To access PMM server, you should be able to connect to pmm-server.prdmesos..com on port 80 (default, if not changed) from the client side.
Any idea why this wouldn’t work then, any tips for what we should check? We can browse the site on port 80 in a browser as well as curl, but when trying to add to the client we get the error
Unable to connect to PMM server by address: pmm-server.prdmesos.<redacted>.com
Even though the server is reachable it does not look to be PMM server.
Check if the configured address is correct.
Hi, I’m working with jasbar on this. We do get responses on /v1/status/leader, /prometheus/, /v1, /qan, but /qan-api, /graph, /orchestrator don’t respond. I’ve taken a look at some of the the logs in the container, and it looks like there are permission issues with the volumes.
I suspect that there is an issue with the fact that I have set up pmm-server to use normal host volumes instead a persistent data container. Do any of you have experience with this?
The volumes should be initialized by the image. So empty ones do not work.
It works for Prometheus, Consul but not for Grafana, QAN API, Orchestrator where mysql datadir should be initialized and loaded.
In our marathon/mesos setting the connection has to be by hostname and not ip otherwise it won’t route to the correct container. Does this mean it needs a dedicated IP after all?
sudo pmm-admin list
pmm-admin 1.0.6
PMM Server | pmm-server.prdmesos..com
Client Name | prdmesos-db01.
Client Address | 192.168.101.8
Service manager | linux-systemd
SERVICE TYPE NAME CLIENT PORT RUNNING DATA SOURCE OPTIONS
linux:metrics prdmesos-db01. 42000 NO -
mysql:metrics prdmesos-db01. 42002 NO root:***@unix(/var/lib/mysql/mysql.sock) tablestats=OFF
For mysql:metrics to work, PMM Server should be able to connect back to the client to 192.168.101.9:42002, check out pmm-admin check-network output.
Note, this is a requirement for all metric services, i.e. server > client connection. You may need to configure firewall settings or port forwarding.
For mysql:queries the connection is done from client > server.