Troubleshooting checklist¶
The following questions might help you identify the origin of the problem while using Percona Monitoring and Management:
- Are you using the latest PMM version?
- Did you check the known issues section in the Release Notes for that particular PMM release?
- Are you receiving any error messages?
- Do the logs contain any messages about the problem? See Message logs and Trace logs for more information.
- Does the problem occur while configuring PMM, such as:
- Does the problem occur while you configure a specific function?
- Does the problem occur when you perform a particular task?
- Are you using the recommended authentication method?
- Does your system’s firewall allow TCP traffic on the ports used by PMM?
- Have you allocated enough disk space for installing PMM? If not, check the disk allocation space.
- Are you using a Technical Preview feature? Technical Preview features are not production-ready and should only be used in testing environments. For more information, see the relevant Release Notes.
- For installing the PMM client, are you using a package other than a binary package without root permissions?
- Is your PMM Server installed and running with a known IP address accessible from the client node?
- Is the PMM Client installed, and is the node registered with PMM Server?
- Is PMM Client configured correctly and has access to the config file?
- For monitoring MongoDB, do you have adminUserAnyDatabase or superuser role privilege to any database servers you want to monitor?
- For monitoring Amazon RDS using PMM, is there too much latency between PMM Server and the Amazon RDS instance?
- Have you upgraded the PMM Server before you upgraded the PMM Client? If yes, there might be configuration issues, thus leading to failure in the client-server communication, as PMM Server might not be able to identify all the parameters in the configuration.
- Is the PMM Server version higher than or equal to the PMM Client version? Otherwise, there might be configuration issues, thus leading to failure in the client-server communication, as PMM Server might not be able to identify all the parameters in the configuration.
Get expert help¶
If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.