# Unable to get the details of PMM instance configured remotely **URL:** \ **Category:** Percona Monitoring and Management (PMM)\ **Created:** [March 3, 2022, 6:41am UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608 "2022-03-03T06:41:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jyoti\_Rajai](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jyoti_rajai/32/4482_2.png) [@Jyoti\_Rajai](https://forums.percona.com/u/Jyoti_Rajai)\ **Post date:** [March 3, 2022, 6:41am UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608/1 "2022-03-03T06:41:28Z")
![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/5/5afd1c0bc0798655e19780110e953b63e2151917.png) 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 ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [March 3, 2022, 2:01pm UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608/2 "2022-03-03T14:01:55Z")
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? ---
**Author:** ![Jyoti\_Rajai](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jyoti_rajai/32/4482_2.png) [@Jyoti\_Rajai](https://forums.percona.com/u/Jyoti_Rajai)\ **Post date:** [March 3, 2022, 3:08pm UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608/3 "2022-03-03T15:08:29Z")
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. ---
**Author:** ![Jyoti\_Rajai](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jyoti_rajai/32/4482_2.png) [@Jyoti\_Rajai](https://forums.percona.com/u/Jyoti_Rajai)\ **Post date:** [March 4, 2022, 5:59am UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608/4 "2022-03-04T05:59:51Z")
Hi @matthewb , Do you have any solution for this ? ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [March 4, 2022, 3:20pm UTC](https://forums.percona.com/t/unable-to-get-the-details-of-pmm-instance-configured-remotely/14608/5 "2022-03-04T15:20:33Z")
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.