Skip to content

Configuration issues

This section focuses on configuration issues, such as PMM-agent connection, adding and removing services for monitoring, and so on.

Client-server connections

There are many causes of broken network connectivity.

The container is constrained by the host-level routing and firewall rules when using using Docker. For example, your hosting provider might have default iptables rules on their hosts that block communication between PMM Server and PMM Client, resulting in DOWN targets in VictoriaMetrics. If this happens, check the firewall and routing settings on the Docker host.

PMM can also generate diagnostics data that can be examined and/or shared with our support team to help solve an issue. You can get collected logs from PMM Client using the pmm-admin summary command.

Logs obtained in this way include PMM Client logs and logs received from the PMM Server, and stored separately in the client and server folders. The server folder also contains its client subfolder with the self-monitoring client information collected on the PMM Server.

Beginning with PMM 2.4.0, there is a flag that enables the fetching of pprof debug profiles and adds them to the diagnostics data. To enable, run pmm-admin summary --pprof.

You can get PMM Server logs with either of these methods:

Direct download

In a browser, visit https://<address-of-your-pmm-server>/logs.zip.

From Help menu

To obtain the logs from the Help menu:

  1. Select Help PMM Logs.

  2. Click PMM Logs to retrieve PMM diagnostics data which can be examined and shared with our support team should you need help.

Connection difficulties

Passwords

When adding a service, the host might not be detected if the password contains special symbols (e.g., @, %, etc.).

In such cases, you should convert any password, replacing special characters with their escape sequence equivalents.

One way to do this is to use the encodeURIComponent JavaScript function in your browser’s web console (commonly found under a Development Tools menu). Run the function with your password as the parameter. For example:

> encodeURIComponent("s3cR#tpa$$worD")

will give:

"s3cR%23tpa%24%24worD"

Password change

When adding clients to the PMM Server, you use the admin user. However, if you change the password for the admin user from the PMM UI, then the clients will not be able to access PMM due to authentication issues. Also, Grafana will lock out the admin user due to multiple unsuccessful login attempts.

In such a scenario, use Service Accounts for authentication. You can use Service Accounts as a replacement for basic authentication and API keys.

Get expert help

If you need assistance, you can find comprehensive and free database knowledge on our community forum or blog posts. For professional support and services, contact our Percona Database Experts.