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-31002 Failed to connect ZooKeeper

ALM-31002 Failed to connect ZooKeeper

Description

  • This alarm is reported when dbhaswitchservice fails to connect to ZooKeepers.
  • This alarm is automatically cleared when dbhaswitchservice successfully connects to ZooKeepers.

Attribute

Alarm ID

Alarm Severity

Alarm Type

31002

Major

Integrity alarm

Parameters

Parameter Name

Parameter Description

deploymentName

Service name

nameSpace

Namespace

alarmName

Alarm name

Impact on the System

The DBAgent and DBHA services will be unavailable.

Possible Causes

  • Two out of the three ZooKeepers or all the three ZooKeepers are running abnormally.
  • The DBHA service is not properly connected to the ZooKeeper service.

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 check whether ZooKeeper is running properly:

    kubectl get pod -n fst-manage -o wide | grep dbm-zk

    NOTE:

    If the status is Running, ZooKeeper is running properly. Otherwise, contact technical support for assistance.

  4. Run the following command to check whether the status of the node where ZooKeeper resides is normal:

    kubectl get nodes --all-namespaces

    NOTE:

    If the status is Ready, the status of the node where ZooKeeper resides is normal. Otherwise, the node may be abnormal or the network may be faulty. In this case, contact technical support for assistance.

Alarm Clearing

This alarm is automatically cleared after connections to the ZooKeepers recover.

Related Information

None.

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 44934

Downloads: 33

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