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-15418 Abnormal ActiveMQ Instance Status

ALM-15418 Abnormal ActiveMQ Instance Status

Alarm Description

This alarm is reported when the processes of multiple ActiveMQ nodes are abnormal.


Alarm ID

Alarm Severity

Alarm Type



Integrity violation

Alarm Parameters




Specifies the node for which the alarm is reported.


Specifies the ActiveMQ instance name.

Impact on the System

If the status of ActiveMQ physical multi-tenant instances is abnormal, the following functions may become unavailable: destination creation and deletion and message creation and consumption.

Possible Causes

  • The connection between the Server node and the node of physical multi-tenant ActiveMQ is abnormal.
  • The ActiveMQ process is running abnormally.


  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. Run the following command to obtain the project ID:

    kubectl get node | grep dms

    1792b1d9475f4999bd32551d7c43a35e   dms-activemq-ms-9e930725-pl847                   Ready      <none>    14d       v2.3.27-FusionStage6.5.RP3-B100-dirty

    In the preceding information, the content in bold is the obtained project ID.

  4. Query the ActiveMQ IP address.

    • Region Type III scenario
      1. Run the following command to obtain the pod, IP address, and node name of ActiveMQ:

        kubectl get po -n 1792b1d9475f4999bd32551d7c43a35e -owide | grep activemq

        1. 1792b1d9475f4999bd32551d7c43a35e is the project ID obtained in 3.
        activemq-phy-9e930725-6d74899f79-6vbpx            1/1       Running   0          14d   dms-activemq-ms-9e930725-vxshm
        activemq-phy-9e930725-6d74899f79-bkhhc            1/1       Running   0          14d    dms-activemq-ms-9e930725-pl847
        activemq-phy-9e930725-6d74899f79-rjqrq            1/1       Running   0          14d    dms-activemq-ms-9e930725-r2x7z

        The information in bold indicates the pod, IP address, and node name of ActiveMQ.

    • Region Type I and Region Type II scenarios
      1. Perform the operations provided in 4.a.
      2. Run the following command to obtain the IP address of the node where ActiveMQ is installed:

        kubectl get node -owide | grep dms-activemq-ms-9e930725-vxshm

        In the preceding command, dms-activemq-ms-9e930725-vxshm is the node name obtained in 4.a.

  5. Log in to the ActiveMQ node.


    In the preceding information, is the ActiveMQ IP address obtained in 4.

  6. Run the following command to check the running status of the ActiveMQ process:

    ps -aux|grep activemq

  7. If the process is in the D, T, or Z state, the process is abnormal. Run the following command to view the ActiveMQ logs and analyze the cause:

    vi /opt/dms/activemq/logs/run/activemq/activemq.log

  8. If the fault cannot be located by viewing logs, contact technical support.

Alarm Clearing

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

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35997

Downloads: 31

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