No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-5000 Redis-OOM

ALM-5000 Redis-OOM


This alarm is generated when the moncalcrdb database for the AMSCalcService service works unexpectedly or data overload occurs.


Alarm ID

Alarm Severity

Alarm Type



Physical violation


Parameter Name

Parameter Description


Indicates the name of an application that generates the alarm.


Indicates the alarm namespace.


Indicates the Redis database instance name.

Impact on the System

  • Metrics fail to be calculated by AMS.
  • The recent metrics fail to be updated on the AMS WebUI.
  • The latest metrics are lost.

System Actions

The system automatically cleans up the database.

Possible Causes

The Redis database works unexpectedly or data overload occurs.


  1. Wait for 5 minutes. The moncalcrdb database of the AMSCalcService service attempts automatic recovery.

    Five minutes later, check whether the alarm is cleared.
    • If yes, no further action is required.
    • If no, go to 2.

  2. Search for the faulty database.

    1. Log in to the OM zone as the op_svc_pom user and choose Application Development > Database > Redis from the main menu.
    2. Enter the database name moncalcrdb in the search box in the upper right corner and click the search icon.
    3. View the database instances and record the detailed information about the database instance whose Project is nameSpace and Role is Master.



      Instance Number

      Indicates the instance ID.

      IP Address

      Indicates the IP address of the database.


      Indicates the database port.

  3. Clean up the faulty database.

    1. Log in to the database node searched in 2.c as the paas user and switch to the root user.
    2. Run the following command to access the database:

      /opt/redis/bin/redis-cli -cipherdir/opt/redis/etc/cipher -p Database port -h Database IP address -a moncalcrdb@dbuser@dbuser user password


      Obtain the database port and database IP address from 2.c. Obtain the initial password of the dbuser user from the database user list. For the new password, contact the system administrator.

    3. Run the flushall command to clean up the database.


    4. Run the exit command to exit the database.


  4. Restart the pod where the faulty database resides.

    1. Log in to the PaaS-lb01 node as the paas user.
    2. Run the following command and enter the password of the root user to switch to the root user:

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to restart the pod:

      kubectl delete po -n nameSpace ` kubectl get pods -n fst-manage |grep -v NAME|grep -E 'ams-calc'|awk '{print $1}'`


      In the preceding command, the value of nameSpace is that of nameSpace in the alarm parameter.

      Wait for 5 minutes until the pod pulls up the database again.

    4. Check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 5.

  5. Contact technical support for assistance.

Alarm Clearing

This alarm is automatically cleared after the moncalcrdb database of the AMSCalcService service is restored.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35622

Downloads: 31

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next