Cause
The causes for this alarm are:
-
Gigaspaces outage
-
Gigaspaces overload
-
CS Space is not INTACT
Solution
- In the Gigaspaces Web UI, check the CSSpace PU status.
ADDITIONAL INFORMATION:
Ensure that the status displays INTACT.
- If the CSSpace PU status is not intact, check the ContextStoreManager logs for errors related to starting the PU, or check the dcm logs for PU related logs at ./var/log/Avaya/services/ContextStoreManager.
ADDITIONAL INFORMATION:
Note:
The path in this step refers to ContextStoreManager logsand not for the PU logs.
- When the issue is identified, restart the cluster.