PMM Client 1.2.0 - Started but not running

[tanveermadan]

Hi,

I tried using the pmm-client 1.2.0 with mongodb as target

./pmm-admin config --server 172.19.155.50
OK, PMM server is alive.

PMM Server | 172.19.155.50
Client Name | xsj-clb01
Client Address | 172.19.61.52

Registering mongodb:metrics errors out

./pmm-admin add mongodb --dev-enable --uri mongodb://xxmonitor:xxxxxx@xsj-clb01:27070
[linux:metrics] OK, now monitoring this system.
[mongodb:metrics] OK, now monitoring MongoDB metrics using URI xxmonitor:***@xsj-clb01:27070
[mongodb:queries] Error adding MongoDB queries: problem with agent registration on QAN API: exit status 2
flag provided but not defined: -mysql
Usage of /qan-agent/bin/percona-qan-agent-installer:
-basedir string
Agent basedir (default “/usr/local/percona/qan-agent”)
-listen string
Agent interface address (default “127.0.0.1:9000”)
-pid-file string
PID file
-ping
Ping API
-version
Print version

Listing the service does not show the exporters to be running

./pmm-admin list
pmm-admin 1.2.0

PMM Server | 172.19.155.50
Client Name | xsj-clb01
Client Address | 172.19.61.52
Service Manager | linux-systemd

---

SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS

---

linux:metrics xsj-clb01 42000 NO -
mongodb:metrics xsj-clb01 42003 NO xxmonitor:***@xsj-clb01:27070

Thanks,
Tanveer

[roma.novikov]

Hi,
can you run pmm-admin check-network ?

[kamil-dziedzic]

Hi Tanveer,

How did you install pmm-client? dev/rpm?

[tanveermadan]

Hi roma.novikov output of check-network is below

./pmm-admin check-network
PMM Network Status

Server Address | 172.19.155.50
Client Address | 172.19.108.66

• System Time
  PMM Server | 2017-08-18 16:08:12 +0000 GMT
  PMM Client | 2017-08-18 09:08:17 -0700 PDT
  PMM Client to PMM Server Time Drift | OK

• Connection: Client --> Server

---

SERVER SERVICE STATUS

---

Consul API OK
Prometheus API OK
Query Analytics API OK

Connection duration | 369.409µs
Request duration | 985.301µs
Full round trip | 1.35471ms

• Connection: Client <-- Server

---

SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD

---

linux:metrics xsja 172.19.108.66:42000 DOWN - -
mongodb:metrics xsja 172.19.108.66:42003 DOWN - -

When an endpoint is down it may indicate that the corresponding service is stopped (run ‘pmm-admin list’ to verify).
If it’s running, check out the logs /var/log/pmm-*.log

When all endpoints are down but ‘pmm-admin list’ shows they are up and no errors in the logs,
check the firewall settings whether this system allows incoming connections from server to address:port in question.

Also you can check the endpoint status by the URL: http://172.19.155.50/prometheus/targets

kamil-dziedzic
, I use the tar.gz and not the rpms because on our servers we do not have provision to write to /usr/local and pmm-admin requires /usr/local/percona
directory

Thanks,
Tanveer

[Mykola]

Hi Tanveer,

@tanveermadan;49448

I use the tar.gz and not the rpms because on our servers we do not have provision to write to /usr/local and pmm-admin requires /usr/local/percona
directory

currently PMM Client generate startup scripts into default OS locations.
It is needed because PMM Client services should be started after OS reboot.

we are looking for solution how to start pmm-client without root user and without write access to default OS paths (internal ticket PMM-1317)
that you for this report!

[tanveermadan]

Mykola Thanks !!!