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).
Cluster Control Service (AS-Service) Fault

Cluster Control Service (AS-Service) Fault

Symptom

The cluster control service (AS-Service) is faulty. As a result, the data of the service interfaces and AS group and process AS activities cannot be provided.

Possible Causes

  • The file system of the VM where the service is deployed is corrupted.
  • The service process is abnormal.

Fault demarcation methods

Figure 11-1 shows the fault demarcation methods.

Figure 11-1 Fault demarcation methods

Procedure

  1. Check whether you can log in to the VM where AS-Schedule is deployed.

    • If yes, go to 4.
    • If no, go to 2.

  2. Restore the VM. For details, see Cloud Service Management Plane Fault Diagnosis.
  3. Contact technical support to reinstall AS-Service. No further action is required.
  4. Use PuTTY to log in to AS-SVR-SVR01 or AS-SVR-SVR02.

    Default username: admin; default password: IaaS@OS-CLOUD9!

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

    TMOUT=0

  6. Run the following command to check whether the process exists:

    ps -ef|grep autoscaling

    • If yes, go to 7.
    • If no, go to 8.

  7. Run the following command to stop the process:

    sh /opt/autoscaling/autoscaling-api/autoscaling.sh stop

  8. Run the following command to restart the process:

    sh /opt/autoscaling/autoscaling-api/autoscaling.sh restart

  9. Check whether AS-Service is restored.

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

  10. If multiple VMs are faulty, perform 1 to 9 on all the faulty VMs.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22555

Downloads: 37

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