Question

4
Replies
347
Views
JagannathR8869 Member since 2016 43 posts
DXC Technology
Posted: May 8, 2018
Last activity: October 12, 2018
Closed

AES error in detecting a cluster

Dears,

I have configured an app cluster to be monitored using AES.

The SearchSoapURI for the cluster is configured with proxy host name, for eg for node 1 is http://bes8z1.bc:18322/BES/PRSOAPServlet

But AES seems to try for a different URL. Though it mentions the actual Websphere name for host instead of proxy name, the port is different than the one configured.

Below is the error i get in the AES server logs. Could you please help me know where is it going wrong.

[5/8/18 14:58:05:295 CEST] 0000002a SystemOut O 2018-05-08 14:58:05,295 [.PRPCWorkManager : 0] [ STANDARD] [ ] [ AES:07.13] (egaAES_Data_AlertOrigin.Action) ERROR - ExecuteGetActivityData: Error. Cluster: BES_PERF Node: c2ac7670ea3e5c967b814295d0e06964 Connection: http://was22222.bc:18422/BES/PRSOAPServlet InsKey: ID: DB-11408 Msg: ** Node is not Reachable
[5/8/18 14:58:05:295 CEST] 0000002a SystemOut O 2018-05-08 14:58:05,295 [.PRPCWorkManager : 0] [ STANDARD] [ ] [ AES:07.13] (egaAES_Data_AlertOrigin.Action) ERROR - Rule data lookup failed for: DB-11408 -- please verify that PegaAESRemote application has been appropriately installed and configured on the monitored system.

***Edited by Moderator Marissa to update platform capability tags****

Pega Autonomic Event Services System Administration
Moderation Team has archived post
Share this page LinkedIn