Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Jeremy Lewis (JeremyL4)
Accenture Federal

Accenture Federal
US
JeremyL4 Member since 2015 18 posts
Accenture Federal
Posted: May 15, 2017
Last activity: May 23, 2017
Posted: 15 May 2017 16:14 EDT
Last activity: 23 May 2017 10:08 EDT
Closed

AES not showing alerts or node information

Hello,

We are currently have in issue with our AES. Originally we were able to see all the alerts for the system, but now it is not showing us any information about or nodes. I have check the configuration and everything is in order for AES to receive the alerts from our nodes. I looked into the logs on our AES server and I am seeing a lot a stack trace errors which I have pasted below. All the servers are up and running. If any one can help us with this issue it would be must appreciated.

Thanks,

-Jeremy L.

2017-05-14 02:12:59,459 [fault (self-tuning)'] [ STANDARD] [ ] [ PegaRULES:07.10] ( internal.mgmt.Executable) ERROR - Exception
com.pega.pegarules.priv.search.nextgen.FTSIllegalStateException: Full text search cluster is not in a ready state. Possible reason(s): Initialization failed / master node not reachable.
at com.pega.pegarules.search.internal.es.AbstractIndexer.buildIndex(AbstractIndexer.java:400)
at com.pega.pegarules.search.internal.es.AbstractIndexer.buildIndex(AbstractIndexer.java:196)
at com.pega.pegarules.search.internal.es.AbstractIndexer.buildIndex(AbstractIndexer.java:191)

To see attachments, please log in.
System Administration

Posted: 7 years ago
Posted: 16 May 2017 5:00 EDT
Raviteja Chatakondu (Raviteja_CH)
PEGA
Principal Technical Support Engineer
Pegasystems Inc.
US

Hi Jeremy,

Is your AES installed over a cluster?

If it is installed over a cluster and search is enabled, the master node must be started first followed by other nodes.

From the error stack trace that you have given, it is clear that the master node might not be up or not reachable.

Please try to fix that and check if the issue still persists.

--Ravi

To see attachments, please log in.
Posted: 7 years ago
Posted: 23 May 2017 9:12 EDT
Jeremy Lewis (JeremyL4)
Accenture Federal

Accenture Federal
US

Hey Ravi,

So I did check to make sure the nodes are up and running. AES is currently not installed over a cluster it is on its own server but the server that it is looking at they are clustered. We have the remote user configured in the nodes. I have tried restarting the nodes and we are still getting the same error.

Thanks,

-Jeremy L.

To see attachments, please log in.
Posted: 7 years ago
Posted: 23 May 2017 10:08 EDT
Basavaraj Kadakol (BASAVARAJ)
PEGA
Senior Manager of Technical Support Engineering
Pegasystems Inc.
AU

Hello Jeremy,


Can you check with the "Search Index Host Node ID" whether it is pointing to the correct NodeID. Also check the below SA articles on PDN

SA-19505

SA-17770

Regards,

Basavaraj

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice