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-38002 Elasticsearch Operation Error

ALM-38002 Elasticsearch Operation Error

Description

This alarm is reported when the ElasticSearch fails to initialize the client connection or the ElasticSearch cluster is abnormal. After the ElasticSearch initializes the client connection or the ElasticSearch cluster is restored to the normal state, the alarm is automatically cleared.

Attribute

Alarm ID

Alarm Severity

Alarm Type

38002

Major

Operational violation 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.

Impact on the System

Application logs and audit logs cannot be queried in the ElasticSearch cluster on the WebUI.

System Actions

The system reports an alarm indicating that ElasticSearch is abnormal when it detects that the connection to the ElasticSearch client is abnormal.

Possible Causes

The node is powered off, the network connection is abnormal, or partial primary shards are lost.

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 Operationsation Operations > Application Operations > Alarm Center > Alarm List. Query alarms whose alarm source is AAD or ALS. If any alarm whose ID is 38002 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 to check the status of the service:

      kubectl get pod -nfst-manage | grep dpa

      As shown in the following command output, Running indicates a normal service status. If the service status is not Running, contact technical support 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 to access the container where the alarm is reported:

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

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

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

      ping dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local

      In this command, dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local is the default domain name of the master node in the ElasticSearch cluster. When this alarm is generated, the client cannot connect to the cluster. Therefore, the IP address of the master node cannot be obtained and the default domain name is used.

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

      PING dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local (172.16.3.53) 56(84) bytes of data.
      64 bytes from dpa-elasticsearch-0.dpa-elasticsearch.fst-manage.svc.cluster.local (172.16.3.53): icmp_seq=1 ttl=64 time=0.027 ms
    4. 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. Run the following command to check the disk space usage:
      df -h /opt
      Filesystem                                          Size  Used Avail Use% Mounted on
      /dev/mapper/docker-202:1-1359881-0862da2296f0d95    10G  681M  9.4G   7% /
    5. If the available space is sufficient, run the following command to collect logs:

      cd /var/paas/sys/log/dpa-elasticsearch/elasticsearch/log

      Collect the root.log file data generated before and after the alarm is reported.

  5. contact technical support for assistance.

Alarm Clearing

After the ElasticSearch initializes the client connection or 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: 47852

Downloads: 33

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