hi
i have this problem
please help [F!]
Presumably, the database could not be connected to read the information
How do I start investigating a problem?
Can you check the docker container status?
docker ps -a – it should be healthy
btw, how di you add the node to the PMM server? can you check the pmm-admin list on the client node?
1 Like
1 Like
1 Like
Hi @ApAchi_Traveler , welcome to the Percona forums!
What installation method did you use to deploy PMM Server? It looks like you didn’t use docker as there are no containers visible.
It looks to me like your PMM Server is where the fault lies,as those red tags on every single box seem to indicate a failure of the dashboard to communicate with the backend timeseries database VictoriaMetrics.
what you can do from PMM Server is to go to the /srv/logs directory and share with us the contents of the grafana.log file.
The other quick fix may be simply to restart your PMM Server and hopefully the services come up cleanly.
2 Likes
also to narrow down your issue (assuming Michael’s right on a service failure) you can run supervisorctl status to see if a service failed to start:
alertmanager RUNNING pid 28, uptime 14 days, 1:44:31
clickhouse RUNNING pid 17, uptime 14 days, 1:44:31
cron RUNNING pid 20, uptime 14 days, 1:44:31
dbaas-controller RUNNING pid 246, uptime 14 days, 1:44:27
grafana RUNNING pid 4340, uptime 14 days, 1:39:41
nginx RUNNING pid 19, uptime 14 days, 1:44:31
pmm-agent RUNNING pid 34, uptime 14 days, 1:44:31
pmm-managed RUNNING pid 33, uptime 14 days, 1:44:31
pmm-update-perform STOPPED Not started
pmm-update-perform-init EXITED Jan 28 02:03 PM
postgresql RUNNING pid 16, uptime 14 days, 1:44:31
prometheus STOPPED Not started
qan-api2 RUNNING pid 156, uptime 14 days, 1:44:30
victoriametrics RUNNING pid 25, uptime 14 days, 1:44:31
vmalert RUNNING pid 26, uptime 14 days, 1:44:31
if Victoriametrics failed to start (exited or stopped) you can look at /srv/logs/victoriametrics.log for more clues.
2 Likes