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-8508 ES Single Node fault

ALM-8508 ES Single Node fault

Description

This alarm is reported when the ElasticSearch cluster contains only one node. After the abnormal node in the ElasticSearch cluster is restored to the normal state, the alarm is automatically cleared.

Attribute

Alarm ID

Alarm Severity

Alarm Type

8508

Minor

Equipment alarm

Parameters

Parameter Name

Parameter Description

SrvAddr

Indicates the default address of the master node in the ElasticSearch cluster.

Namespace

Indicates the namespace of the service that reports the alarm.

ServiceName

Indicates the name of the service that reports the alarm.

InstanceName

Indicates the name of the service instance that reports the alarm.

MasterNodeHost

Indicates the IP address of the faulty node in the ElasticSearch cluster.

Impact on the System

The single-node fault has no impact on basic system functions but may affect system performance and stability.

System Actions

This alarm is reported when the system detects that the ElasticSearch cluster contains only one node.

Possible Causes

The node is powered off, or the network connection is abnormal.

Procedure

  1. Use a browser to log in to the FusionStage OM zone console.

    1. Log in to ManageOne Maintenance Portal.
      • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
      • The default username is admin, and the default password is Huawei12#$.
    2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.

  2. On the main menu, choose Application Operations > Application Operations> Alarm Center > Alarm List Query alarms whose alarm source is ALS. If any alarm whose ID is 8508 exists, rectify the fault by referring to the following steps.
  3. Check whether the background configuration file and logs contain error information.

    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 check the status of the dpa-elasticsearch service:

      kubectl get pod -n fst-manage | grep dpa

      As shown in the following command output, Running indicates a normal service status. If the service status is not Running, contact the APM service personnel to locate the fault.

      dpa-elasticsearch-0                         1/1       Running   0          1h
      dpa-elasticsearch-1                         1/1       Running   0          1h

  4. Check whether the network connection between the application and the master node of the ElasticSearch cluster is normal.

    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 access the container where the alarm is reported:

      kubectl exec -it dpa-elasticsearch-0 sh -n fst-manage

      In this command, dpa-elasticsearch-0 is the value of InstanceName, and fst-manage is the value of Namespace.

    4. Run the following command to check whether the network connection is normal:

      ping **.**.**.**

      In this command, **.**.**.** is the master node address, which can be found in the additional information.

      If the following information is displayed, the network connection is normal:

      PING dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local(172.16.0.13) 56(84) bytes of data.
      64 bytes from dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local (172.16.0.13): icmp_seq=1 ttl=64 time=0.385 ms
    5. If the network connection is normal, check the disk space usage. If the available space is too small, expand the disk space or delete unnecessary data.
      df -h /opt
      Filesystem                                          Size  Used Avail Use% Mounted on
      /dev/mapper/docker-202:1-1359881-0862da2296f0d95    10G  681M  9.4G   7% /
    6. If the available space is sufficient, If the available space is sufficient, go to 1.
    7. Choose Application Operations > Application Operations > Log Management > Log Collect from the main menu.
    8. Select dap from the drop-down list in Collect Application Logs and set Time Period in Select Time as required.
    9. Click Collect.

  5. Contact technical support for assistance.

Alarm Clearing

After the abnormal node in the ElasticSearch cluster is restored to the normal state, the alarm is automatically cleared.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34251

Downloads: 31

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