ContextStoreManager_CS_EVT_8

Last Updated : Apr 11, 2021 |
Prolog information
Metadata
Keywords:

Condition

Default event message text
Data replication to GEO linked cluster has failed. See logs for details.
Event level
Major
Trigger component
ContextStoreManager
Log file
/var/log/Avaya/services/ContextStoreManager

Cause

The causes for this alarm are:
  • Gigaspaces outage
  • Gigaspaces overload
  • CS-gateway is not INTACT
  • GEO replicated cluster is misconfigured
  • GEO replicated cluster is in down

Solution

  1. In the Gigaspaces Web UI, check the CSGateway Processing Unit (PU) status.
    ADDITIONAL INFORMATION:
    Ensure that the status displays INTACT.
  2. If the CSGateway 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.
  3. Check GEO attribute section on both the Avaya Oceana® Cluster 1 instances at GEO site 1 and GEO site 2.
  4. Verify that the GEO replicated cluster node state is Accepting.
  5. When the issue is identified, restart the cluster.