ContextStoreManager_CS_EVT_6

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

Condition

Default event message text
EDM PU is unavailable
Event level
Major
Trigger component
ContextStoreManager
Log file
/var/log/Avaya/services/ContextStoreManager

Cause

The causes for this alarm are:
  • Gigaspaces outage
  • Gigaspaces overload
  • Incorrect EDM attribute settings
  • EDM PU is not INTACT
    • For example, if the Persistence Type is set to JOURNEY, then the alarm is raised if the Journey PU is not INTACT, because the EDM PU does not exist.
    • If the Persistence Type is set to AUDIT, then only the EDM PU is considered.
    The alarm text displays the following message: EDM PU is not available.

Solution

  1. In the Gigaspaces Web UI, check the EDM PU status.
    ADDITIONAL INFORMATION:
    Ensure that the status displays INTACT.
  2. If the EDM 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 logs and not for the PU logs.
  3. When the issue is identified, restart the cluster.