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-2000471 ZooKeeper Process Does Not Exist

ALM-2000471 ZooKeeper Process Does Not Exist

Description

This alarm is generated when the ZooKeeper process is not running on a ZooKeeper node.

Attribute

Alarm ID

Alarm Severity

Auto Clear

2000471

Critical

Yes

Parameters

Parameter

Description

Alarm Name

Alarm name

Source Device

Name of the device for which the alarm is generated

Monitoring System

Type of the interconnected system

Source System

Name of the interconnected system

IP Address

IP address of the node for which the alarm is generated

Possible Causes

Possible causes of the alarm

Additional Information

Supplementary information about the alarm

First Occurred At

Time when the alarm was generated for the first time

Impact on the System

The alarmed node cannot provide services.

Possible Causes

  • The crontab job is abnormal.
  • The ZooKeeper configuration file is incorrect.

Procedure

  1. Log in to ManageOne Maintenance Portal using a browser.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin; default password: Huawei12#$

  1. On the menu bar in the upper part of the page, choose Alarms > Current Alarms.
  2. In the alarm list, locate the alarm to be handled, and click on the left of the alarm. The Details page is displayed.
  3. Choose Location Info, obtain the host IP address, that is, the IP address of the node where the alarm is generated.
  4. Use PuTTY to log in to the node for which the alarm is generated. Ensure that the management IP address of the node obtained in 4 is used to establish the connection.

    The default account is hermes, and the default password is Hermes@123.

  5. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  6. Run the following command to switch to the root user:

    sudo su - root

    The default password is Cloud12#$.

  7. Run the following command to check whether the crontab job is disabled:

    cat /etc/crontab | grep zookeeper

    [root@SMN-KFK-ZK01 hermes]# cat /etc/crontab | grep zookeeper
    */1 * * * * root su hermes -c /opt/hermes/service/zookeeper/bin/start_zookeeper.sh >/dev/null 2>&1

    If # is displayed at the beginning of the command output, the crontab job is disabled.

    • If yes, delete # to enable the crontab job.
    • If no, go to 9.

  8. Run the following commands to open the zoo.cfg file and check whether the values of server.* are configured to the correct ZooKeeper node IP addresses and port 8880:7770:

    cd /opt/hermes/service/zookeeper/conf

    vi zoo.cfg

    #autopurge.purgeInterval=1
    server.0=162.129.187.31:8880:7770
     server.1=162.129.187.32:8880:7770
     server.2=162.129.187.33:8880:7770

  9. Run the following commands to switch to user hermes and manually start the ZooKeeper process:

    su - hermes

    sh /opt/hermes/service/zookeeper/bin/start_zookeeper.sh

  10. Run the following command to check whether the ZooKeeper process is running properly:

    ps -ef|grep zoo.cfg

    [root@SMN-KFK-ZK01 ~]# ps -ef|grep zoo.cfg
    root      1169   929  0 16:37 pts/0    00:00:00 grep --color=auto zoo.cfg
    hermes    9299     1  0 Apr25 ?        00:05:16 /opt/hermes/jre/bin/java -Dzookeeper.log.dir=/var/log/hermes/zookeeper -Dzookeeper.root.logger=INFO,ROLLINGFILE -cp /opt/hermes/service/zookeeper/bin/../build/classes:/opt/hermes/service/zookeeper/bin/../build/lib/*.jar:/opt/hermes/service/zookeeper/bin/../lib/wcc_log-1.2.4.jar:/opt/hermes/service/zookeeper/bin/../lib/slf4j-log4j12-1.6.1.jar:/opt/hermes/service/zookeeper/bin/../lib/slf4j-api-1.6.1.jar:/opt/hermes/service/zookeeper/bin/../lib/netty-3.7.0.Final.jar:/opt/hermes/service/zookeeper/bin/../lib/log4j-1.2.16.jar:/opt/hermes/service/zookeeper/bin/../lib/jline-0.9.94.jar:/opt/hermes/service/zookeeper/bin/../zookeeper-3.4.6.jar:/opt/hermes/service/zookeeper/bin/../src/java/lib/*.jar:/opt/hermes/service/zookeeper/bin/../conf: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false org.apache.zookeeper.server.quorum.QuorumPeerMain /opt/hermes/service/zookeeper/bin/../conf/zoo.cfg
    [root@SMN-KFK-ZK01 ~]#
    • If yes, go to 12.
    • If no, contact technical support for assistance.

  11. Ten minutes later, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Reference

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47593

Downloads: 33

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