Tried to open aws probe using admin console but it throws PPM-025 error
search cancel

Tried to open aws probe using admin console but it throws PPM-025 error

book

Article ID: 185393

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Unable to read configuration. Configuration was unable to be retrieved.



ppm v3.51

ppm.log shows:

Mar 02 14:23:46:411 [attach_socket, ppm] Delegating get_ctd_configuration to probe at /NMS/hubNP01/prdnimnp03/aws

Mar 02 14:23:46:536 [attach_socket, ppm] Exception calling /NMS/hubNP01/prdnimnp03/aws.get_ctd_configuration(    crdta=É8cC†ìeº°Šj?^

½¥7Ì3âEu;÷», crlen=1127) :(120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'get_ctd_configuration'

Mar 02 14:23:46:536 [attach_socket, ppm] (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'get_ctd_configuration'

                at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:627)

                at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:573)

                at com.nimsoft.nimbus.NimClientSession.send(NimClientSession.java:173)

                at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:264)

                at com.nimsoft.pf.common.PfNimRequest.sendImpersonate(PfNimRequest.java:29)

                at com.nimsoft.nimbus.NimRequest.send(NimRequest.java:219)

                at com.nimsoft.ppm.operation.PfRemoteOperation.execute(PfRemoteOperation.java:98)

                at com.nimsoft.ppm.PPM.callPfProbeGetCtdConfiguration(PPM.java:421)

                at com.nimsoft.ppm.PPM.getCtdConfigurationFromProbe(PPM.java:385)

                at com.nimsoft.ppm.PPM.cbGetCtdConfiguration(PPM.java:302)

Environment

Release : 9.0.2

Component : UIM - PPM

Cause

- ppm probe memory

Resolution

The aws probe had a fairly large aws.cfg and the ppm probe was set to default java memory, 32/1024 MB memory so we increased the ppm probe memory to 2048/4096 and cold started it, and the ppm error was then resolved the next time we opened the aws probe in the Admin Console.