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).
Instance Creation Faults

Instance Creation Faults

An Instance Fails to Be Created Due to Cluster Faults

Symptom

An internal error is displayed when a cluster is selected on the page for creating an instance.

Possible Causes

Cluster services are abnormal.

Troubleshooting Process
  1. Use PuTTY to log in to the EIS_PublicVM-Service1 and EIS_PublicVM-Service2 management VMs.

    Default username: ads; default password: Cloud12#$

  2. Run the following command to prevent PuTTY logout on system timeout:

    TMOUT=0

  3. Go to the Service node and view background logs.

    cd /opt/dbs/ads/log/run

    vi runtime.log

    Script for searching error logs

Fault Rectification

Apply for an instance again and select a cluster. If no error message is displayed, the instance is successfully applied for.

FusionInsight Cluster Resources Are Insufficient

Symptom

Instances fail to be created.

Troubleshooting Process
  1. Use PuTTY to log in to the EIS_PublicVM-Service1 and EIS_PublicVM-Service2 management VMs.

    Default username: ads; default password: Cloud12#$

  2. Run the following command to prevent PuTTY logout on system timeout:

    TMOUT=0

  3. Go to the Service node and view background logs.

    cd /opt/dbs/ads/log/run

    vi runtime.log

  4. Use the order ID and query the ERROR level logs containing the CPU and memory information.
Fault Rectification

Contact the administrator.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1131

Downloads: 12

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