I am using pmm2pmm-server 192.168.1.2pmm-client 192.168.1.3when I runsudo pmm-admin config --server-insecure-tls --server-url=https://admin:xxxx@y.y.y.y:443output success like thisChecking local pmm-agent status…
pmm-agent is running.
Registering pmm-agent on PMM Server…
Registered.
Configuration file /usr/local/percona/pmm2/config/pmm-agent.yaml updated.
Reloading pmm-agent configuration…
Configuration reloaded.
Checking local pmm-agent status…
pmm-agent is running.But, when I see pmm2 dashboard. only show box with ‘N/A’ value
Need help or hint.
Hi Suhar,
Please check pmm-agent logs (/var/log/pmm-agent.log) on client side and statuses of Prometheus targets (https://192.168.1.2/prometheus/targets).
Exporters ports could be blocked by firewalls.
https://192.168.1.2/prometheus/targets show client down. I use docker pmm in pmm-server using virtualbox (seem networking configuration issue)
I will try .rpm version (I use centos os)
https://192.168.1.2/prometheus/targets show client down. I use docker pmm in pmm-server using virtualbox (seem networking configuration issue)
I will try virtual appliance and report the result
It’s likely a firewall issue (iptables or selinux or something) from your PMM server see if you can telnet to 192.168.1.3 on port 42000 or 42001 (‘telnet 192.168.1.3 4200x’) if you get a connection refused I’d look at the iptables or similar on your client machine. we’re working on changing it but registration is a client –> server (dest port 443) call, while retrieval of metrics is a server –> client (dest port 4200x) in about a quarter we’ll be able to do everything over the client –> server (dest port 443) channel and if you can register metrics will flow!!!
Thank for your response, here output from telnet 192.168.1.3
[sihar@pmm-server ~]$ telnet 192.168.1.3 42000Trying 192.168.1.3…
Connected to 192.168.1.3.
Escape character is ‘^]’.
But pmm-server dashboard still N/A
Hmm…ok…rolling up my sleeves a bit here!
Firewall doesn’t appear to be in play - check!
can you send the output of ‘pmm-admin status’? Will be looking at version information (so I can try to recreate it) as well as make sure the node_exporter is running on the client (which it should start by default).
As a test for you to make sure it’s returning data and not errors try the following:
Copy the string (including the /agent_id/) for the node_exporter you saw above with a “Running” next to it…if you’ve not monitored anything else it’ll likely be the only one.
navigate to: http(s)://192.168.1.2/prometheus/targets and see if anything is reporting back as “unhealthy”…assuming not search for “node_exporter” on the page and fine an entry corresponding to your node_name (there will be one for the pmm-server)
click the URL in the endpoint column (hopefully it’s http://192.168.1.3:42000/metrics) and when it prompts for username and password use:
username: pmm
password: that /agent_id/ string you copied earlier
This should return metrics about your system like version, disk activity etc…if that does, can you go back to your dashboard and see if that jumpstarted metrics? Not expecting any of that to fix it per se, but trying to see where the problem is to resolve it so if at any point in the above something isn’t right…post that here as we’ll know better where to look/help!
Thanks for your response Steve.
I am doing fresh install pmm-server v1 using docker version and install pmm-client (pmm-client-1.17.4-1.el7.x86_64.rpm)
After I add port 42000 and port 42002 on pmm client, It works and show in dashboard.
Here I attach screenshot
I hope next time I can install pmm-server version 2