Comments on: Running PMM1 and PMM2 Clients on the Same Host

By: Vadim Yalovets

Vadim Yalovets — Wed, 13 May 2020 13:41:56 +0000

In reply to Rohit Khurana. Hi Rohit, Please modify the ports range for exporters in the file pmm-agent.yaml ... ports: min: 42000 max: 51999 ...

By: Rohit Khurana

Rohit Khurana — Fri, 08 May 2020 09:25:53 +0000

getting below while running two PMM agents

msg=”listen tcp :42000: bind: address already in use” source=”server.go:141″

By: Vadim Yalovets

Vadim Yalovets — Wed, 22 Jan 2020 21:05:57 +0000

In reply to smit. Hello Smit, Could you make sure that exporters have the correct path in the configuration file pmm-agent.yaml? It looks like pmm-agent can't start exporters.

By: smit

smit — Tue, 21 Jan 2020 07:26:15 +0000

Hi, I always got waiting state no values are fetched to grafana
node_exporter waiting /agent_id/a7130b1a-cb43-499a-a0a3-e6d9840566dd
mysqld_exporter waiting /agent_id/5fcdf261-3e74-47ad-8196-76de02f7a63f /service_id/81584871-9ea0-4844-a414-2d989884986b

By: Vadim Yalovets

Vadim Yalovets — Wed, 18 Dec 2019 11:09:27 +0000

In reply to Kirill. It will be add in some later releases.

By: Kirill

Kirill — Wed, 18 Dec 2019 10:45:30 +0000

In reply to Vadim Yalovets. ok, i found trouble, thanks and have small question why pmm2 don't have option for connections on socket ?

By: Vadim Yalovets

Vadim Yalovets — Tue, 17 Dec 2019 20:31:06 +0000

In reply to Daniel Guzmán Burgos. Thank you for your comments. You are right.

By: Daniel Guzmán Burgos

Daniel Guzmán Burgos — Tue, 17 Dec 2019 15:59:26 +0000

Hi Vadim, thanks for the info! couple of comments:

1. The section “Register and Generate Configuration File” have a problem: you are repeating the directory name in the path. For example, instead of “$PWD/pmm2-client-2.1.0/bin/node_exporter” it should be “$PWD/bin/node_exporter”. Full command fixed:

./bin/pmm-agent setup –config-file=config/pmm-agent.yaml \
–paths-node_exporter=”$PWD/bin/node_exporter” \
–paths-mysqld_exporter=”$PWD/bin/mysqld_exporter” \
–paths-mongodb_exporter=”$PWD/bin/mongodb_exporter” \
–paths-postgres_exporter=”$PWD/bin/postgres_exporter” \
–paths-proxysql_exporter=”$PWD/bin/proxysql_exporter” \
–server-insecure-tls –server-address=172.17.0.2:443 \
–server-username=admin –server-password=”admin” 172.17.0.1 generic node8.ca

2. And the other is that, if pmm-client (for PMM 1) is already running, the 42000 port is already in use and the PMM2 client will keep trying to connect to it but it won’t. The fix is to edit the config/pmm-agent.yaml and change the starting port. It will look like this:

ports:
min: 42005
max: 51999

By: Vadim Yalovets

Vadim Yalovets — Tue, 17 Dec 2019 15:28:42 +0000

In reply to Kirill. Hi Kirill, It looks like your server doesn't allow access through the default mysql port 3306 or mysql service is configured on a different port. Could you check it and try with a different port? e.g. $ ./bin/pmm-admin add mysql myMySQLService 127.0.0.1:3307 Please notice that a service name has to be specify before an address

By: Kirill

Kirill — Mon, 16 Dec 2019 16:32:24 +0000

Hi
I installed PMM2

But i can’t add mysql agent, have error:

DEBUG 2019-12-16 16:15:23.107100383Z: HTTP/1.1 400 Bad Request
Transfer-Encoding: chunked
Trailer: Grpc-Trailer-Content-Type
Connection: keep-alive
Content-Type: application/json
Date: Mon, 16 Dec 2019 16:15:23 GMT
Server: nginx

be
{“error”:”Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.”,”code”:9,”message”:”Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.”}
0

DEBUG 2019-12-16 16:15:23.107172147Z: Result:
DEBUG 2019-12-16 16:15:23.107186033Z: Error: &my_sql.AddMySQLDefault{_statusCode:400, Payload:(*my_sql.AddMySQLDefaultBody)(0xc0005d9440)}
Connection check failed: dial tcp 127.0.0.1:3306: connect: connection refused.