Unable to get the details of PMM instance configured remotely

Percona Monitoring and Management (PMM)
1

image
image1303×605 19.2 KB

Unable to get the details of PMM instance confirmed remotely.

Logs :

[root@P_Percona_Monitoring ~]# docker logs --tail=20 279242b100af
2022-03-03 07:29:26,232 INFO spawned: ‘createdb2’ with pid 68451
2022-03-03 07:29:27,224 INFO exited: createdb3 (exit status 1; not expected)
2022-03-03 07:29:27,241 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:27,242 INFO spawned: ‘createdb3’ with pid 68473
2022-03-03 07:29:27,242 INFO success: createdb2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:27,443 INFO exited: mysql (exit status 1; not expected)
2022-03-03 07:29:27,613 INFO spawned: ‘mysql’ with pid 68476
2022-03-03 07:29:28,279 INFO success: createdb3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:28,386 INFO exited: qan-api (exit status 1; not expected)
2022-03-03 07:29:28,554 INFO spawned: ‘qan-api’ with pid 68503
2022-03-03 07:29:28,699 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:28,823 INFO exited: mysql (exit status 1; not expected)
2022-03-03 07:29:28,940 INFO spawned: ‘mysql’ with pid 68506
2022-03-03 07:29:29,700 INFO success: qan-api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:29,719 INFO exited: createdb (exit status 1; not expected)
2022-03-03 07:29:29,873 INFO spawned: ‘createdb’ with pid 68527
2022-03-03 07:29:29,957 INFO success: mysql entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-03 07:29:30,214 INFO exited: mysql (exit status 1; not expected)
2022-03-03 07:29:30,219 INFO spawned: ‘mysql’ with pid 68530
2022-03-03 07:29:30,937 INFO success: createdb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[root@P_Percona_Monitoring ~]#

Please help.

Thanks in Advance

1 Like
2

Looks like your PMM was not configured correctly. Are you using the PMM v2? The latest Docker version? Did you follow all steps in our documentation?

1 Like
3

This is old PMM version , docker is also old. & Every other panels are working. Only this is having issue. I have checked list of remote instances way back when had configured from pmm.

1 Like
4

Hi @matthewb ,
Do you have any solution for this ?

1 Like
5

All I can see is that your PMM is crashing and restarting. This could be due to a bug in that old version of PMM that was fixed in later versions. My solution is to upgrade your docker and upgrade to the latest supported PMM version.

2 Likes