Question
DXC Technology
BE
Last activity: 12 Oct 2018 14:34 EDT
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****
Pegasystems Inc.
IN
Hi,
Please verify below:
1. Open the instances of PegaAES-Data-Node and verify that the Connection String values are correctly pointing to the monitored nodes. The Connection String must maintain the following format:
http://host:port/prweb/PRSOAPServlet
2.Open each node instance and ensure that the Enabled option is checked.
3.Also verify AES related agents are running .
Thank you
-Abhishek
Hi,
Please verify below:
1. Open the instances of PegaAES-Data-Node and verify that the Connection String values are correctly pointing to the monitored nodes. The Connection String must maintain the following format:
http://host:port/prweb/PRSOAPServlet
2.Open each node instance and ensure that the Enabled option is checked.
3.Also verify AES related agents are running .
Thank you
-Abhishek
Pegasystems Inc.
US
Per Abishek's comment : Monitored nodes send AES their "best guess" for the URL AES should use to contact the node. The URL (aka, the 'connection string') is stored in the PegaAES-Data-Node records.
Typically, the 'best guess' is wrong - on a multi-homed virtual server, Java typically will provide a 'local-only' URL that won't actually work when AES tries to use it.
From designer studio, manually edit the node records and fill in the appropriate externally / network accessible host:port + /prweb/PRSOAPServlet.
After you make your changes, flush data page D_EnabledNodes and log out / log in. The node URL's are cached in node level data page D_EnabledNodes.
Btw - the AES features that require AES to 'pull' data are deprecated in AES 7.3.
Which version of AES are you using?
DXC Technology
BE
We are using AES 7.13.
I tried doing the manual editing inside the PegaAES-Data-Node and flushed the declare page and even tried restart. But still not causing my AES to monitor the nodes that i wanted.
Some other things to check here ?
regards,
Jagan
Pegasystems Inc.
US
AES does not "monitor nodes". Nodes send data to AES.
The connection string inside the node record is used when AES tries to contact a node based either on a user action (in the Enterprise landing page) or to get information to investigate an issue that was sent to AES by the node.
If you do not see alerts, exceptions or health status from a node in AES, start the trouble-shooting on the node itself.
If a node is sending data to AES, but you can not "soap" to the node from AES, bring up the node in enterprise health, bring up the requestors tab, enable tracer then press search. Tracer / logs should show what's happening with the call from AES to the node.
Also see https://collaborate.pega.com/discussion/troubleshooting-deferred-write-operations