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

FusionCloud 6.3.1.1 Troubleshooting Guide 02

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).
Failures in Adding, Deleting, or Modifying a VPC

Failures in Adding, Deleting, or Modifying a VPC

Symptom

On the ManageOne operation plane, users can access and query a VPC, but cannot add, delete, or modify a VPC.

Possible Causes

ZooKeeper must be deployed on 2n+1 servers, and at least n+1 servers must be functional (n is an integer). The VPC service requires three ZooKeeper servers, and at least two of them must work properly.

The possible cause of the fault is that only one ZooKeeper server is running properly.

Troubleshooting Process

  1. Check whether the ZooKeeper process is running properly on the node where the ZooKeeper service is deployed. If the process is running improperly, manually restart it to restore the service.
  2. If you cannot log in to the node or fail to manually restart the process, set the ZooKeeper service to work in single node mode before restoring the faulty node. After the node is restored, configure the service to work in multi-node mode.

Procedure

  1. Use PuTTY to log in to the PUB-SRV01 VM.

    Username: vpc; default password: Huawei12#$

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

    TMOUT=0

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

    ps -ef | grep zookeeper

    • If process is running, the ZooKeeper service provided by the node is normal. Perform step 1 to log in to the PUB-SRV02 or PUB-SRV03 VM to check whether the ZooKeeper process is running.
    • If the process is not running, go to 4.

  4. Run the following command to restart the ZooKeeper process:

    sh /home/vpc/zookeeper/bin/startZookeeper.sh

  5. Perform steps 1 to 4 to restart the ZooKeeper process on the second faulty node.
  6. Run the following command on the two faulty nodes respectively to check whether the ZooKeeper process restarts:

    ps -ef | grep zookeeper

    • If the ZooKeeper process restarts, go to 7.
    • If the ZooKeeper process on only one faulty node restarts, contact technical support for assistance to restore the other faulty node.
    • If the ZooKeeper processes on both the two faulty nodes fail to restart, perform steps 8 to 17 to set the ZooKeeper process to work in single node mode.

  7. Check whether a VPC can be added, deleted, and modified on ManageOne Operation Management Portal.

    The functions are normal, and no further action is required.

  8. Use PuTTY to log in to the PUB-SRV01, PUB-SRV02, or PUB-SRV03 VM.

    Username: vpc; default password: Huawei12#$

  9. Back up the following configuration files. After all nodes are restored, use the configuration file backups to set ZooKeeper to work in multi-node mode.

    /home/vpc/zookeeper/conf/zoo.cfg

    /home/vpc/network/WEB-INF/classes/config/networkConfig.xml

  10. Run the following command and press i to enter the editing mode for the zoo.cfg file:

    vi /home/vpc/zookeeper/conf/zoo.cfg

    Modify the server configuration at the end of the ZooKeeper configuration file. Specifically, only retain the configuration of the ZooKeeper server which is running properly.

    For example, if the ZooKeeper service on the only server with IP address 192.168.51.2 among the following servers is running properly, retain only the configuration of this server:

    server.0=192.168.51.2:2888:3888

    server.1=192.168.51.3:2888:3888

    server.2=192.168.51.4:2888:3888

    Retain only the following configuration:

    server.1=192.168.51.2:2888:3888

  11. Press Esc, enter :wq, and press Enter.

    The system saves the configuration and exits the vi editor.

  12. Run the following command and press i to enter the editing mode for the networkConfig.xml file:

    vi /home/vpc/network/WEB-INF/classes/config/networkConfig.xml

    Modify the IP addresses in the configuration file called by the service. Specifically, retain the configuration of only the ZooKeeper server which is running properly.

    For example, if the ZooKeeper service on the only server with IP address 192.168.51.2 among the following servers is running properly, retain only the configuration of this server:

    <zookeeper_address>192.168.51.2:2181,192.168.51.3:2181,192.168.51.4:2181</zookeeper_address>

    Retain only the following configuration:

    <zookeeper_address>192.168.51.2:2181</zookeeper_address>

  13. Press Esc, enter :wq, and press Enter.

    The system saves the configuration and exits the vi editor.

  14. Run the following command to query the ID of the ZooKeeper process:

    ps -ef | grep zookeeper

  15. Run the following commands to restart the ZooKeeper process:

    kill -9 ZooKeeper process ID

    sh /home/vpc/zookeeper/bin/startZookeeper.sh

  16. Run the following command to query the ID of the Tomcat process:

    ps -ef | grep tomcat

  17. Run the following commands to restart the Tomcat process:

    kill -9 Tomcat process ID

    sh /home/vpc/local/tomcat/bin/startup.sh

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22750

Downloads: 37

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