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 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).
VPC Console Faults

VPC Console Faults

Symptom

The VPC page is not displayed properly.

Possible Causes

  • The file systems on the service VMs are corrupted.
  • A VPC-Console process exception has occurred.

Troubleshooting Process

Figure 14-1 shows the troubleshooting process.

Figure 14-1 Troubleshooting process

Procedure

  1. Check whether you can normally log in to the VM (CONSOLE01 or CONSOLE02) where the VPC-Console service is deployed.

    • If you can normally log in to the VM, go to 4.
    • If you cannot normally log in to the VM, go to 2.

  2. Contact technical support for assistance to repair the VM OS.

    • If the VM OS is successfully repaired, go to 4.
    • If the VM OS fails to be repaired, go to 3.

  3. Contact technical support for assistance to reinstall the VPC-Console service.
  4. Use PuTTY to log in to the CONSOLE01 or CONSOLE02 VM.

    Username: vpc; default password: Huawei12#$

  5. Run the following command and enter the password Cloud12#$ of the root user to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the Tomcat process is running:

    ps -ef | grep tomcat|grep vpc

    • If the process is running, no further action is required.
    • If the process is not running, go to 8.

  8. Run the following command as the vpc user to restart the Tomcat process:

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

  9. Check whether the alarm is cleared after the restart.

    • If the alarm is cleared, no further action is required.
    • If the alarm is not cleared, contact technical support for assistance to reinstall the service. After the reinstallation, no further action is required.

  10. If multiple VMs are faulty, perform 1 to 9 for each faulty VM.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 4204

Downloads: 22

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