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-2018 Service Running Overloaded

ALM-2018 Service Running Overloaded


This alarm is generated when cse-config-center, cse-governance-service, cse-dashboard-service, or cse-service-center is overloaded.


Alarm ID

Alarm Severity

Alarm Type



Environmental alarm





Indicates the namespace of the service for which the alarm is generated.


Indicates the name of the service for which the alarm is generated.


Indicates the name of the service instance for which the alarm is reported.


Indicates the IP address of the host where the microservice instance is deployed.

Impact on the System

When the service running is overloaded, the API response times out.

Possible Causes

  • The number of concurrent service requests exceeds the service load.
  • System resources are insufficient.


  1. Use PuTTY to log in to the manage_lb1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

  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. Check for the APIs that respond slowly to determine whether services are to be processed.

    View the /var/paas/sys/log/cse-service-center/service-center.log file of the service center and search for the keyword LogNilOrWarnf in the log file to check which APIs respond slowly.

    Alternatively, go to the pod of the CSE service for which the alarm is reported, and run the netstat -nap command to check whether the number of connections is normal. The following uses the pod of cse-service-center-3608034112-ht6lx as an example:

    kubectl -n fst-manage exec -it cse-service-center-3608034112-ht6lx sh

  4. On the node where the service is located, run the top command to check the system load and check whether there are abnormal processes.

    If the value is too large and the service corresponding to the process is not a key service, restart the process.

    kill -9 Process ID

    If the system resources are insufficient, apply for resource expansion.

  5. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Alarm Clearing

This alarm will be automatically cleared after the fault is rectified.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 45790

Downloads: 33

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