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

Reminder

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

upgrade

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-15417 Nodes of Physical Multi-Tenant Kafka Are Faulty

ALM-15417 Nodes of Physical Multi-Tenant Kafka Are Faulty

Alarm Description

This alarm is reported when the nodes of physical multi-tenant Kafka are abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

15417

Major

Integrity violation

Alarm Parameters

Parameter

Description

hostIP

Specifies the node for which the alarm is reported.

instanceName

Specifies the Kafka instance name

Impact on the System

The possible cause of the Kafka node exception is that the SSH connection between the DMS server nodes and the Kafka nodes is abnormal. The Kafka may be running properly, but the DMS server nodes fail to monitor the disk and CPU information of Kafka.

Possible Causes

  • The connection between the server node and the node of physical multi-tenant Kafka is abnormal.
  • The node of physical multi-tenant Kafka is abnormal.

Procedure

  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. Run the following command to obtain the pod IDs of DMS server nodes:

    kubectl get po -n 1792b1d9475f4999bd32551d7c43a35e | grep dms-server

    In the preceding command, 1792b1d9475f4999bd32551d7c43a35e is the project ID obtained in 3.

    dms-server-466c532c-ddfc8cb6d-2n96z               1/1       Running   0          8d
    dms-server-466c532c-ddfc8cb6d-rklzs               1/1       Running   0          14d

    In the preceding information, the content in bold indicates the pod IDs of two DMS server nodes respectively.

  5. Run the following command to go to the container of the DMS server nodes:

    kubectl exec -it dms-server-466c532c-ddfc8cb6d-2n96z -n 1792b1d9475f4999bd32551d7c43a35e bash

    In the preceding information, dms-server-466c532c-ddfc8cb6d-2n96z and 1792b1d9475f4999bd32551d7c43a35e are the pod IDs of the DMS server nodes obtained in 4.

  6. Run the following command to view the scheduled task logs of the DMS server nodes:

    vi server/logs/dms/task/dms_task.log

    If the logs related to the SSH client connection exist, the SSH connections between the DMS server nodes and the Kafka nodes are abnormal. Otherwise, the fault is caused by other network problems.

  7. If the alarm persists, contact technical support for assistance.

Alarm Clearing

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

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35956

Downloads: 31

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