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).
Abnormal Applications

Abnormal Applications

Symptom

Applications fail to be deployed and are abnormal.

Possible Causes

  • Management zone nodes are abnormal
  • The node on which the application is deployed is abnormal.

Troubleshooting Method

  1. Log in to FusionStage.

    1. Use a browser to log in to ManageOne Operation Portal (ManageOne Tenant Portal in B2B scenarios) as a VDC administrator or VDC operator.
      Login address:
      • Login address in a non-B2B scenario: https://Address for accessing ManageOne Operation Portal, for example, https://console.demo.com.
      • Login address in the B2B scenario: https://Address for accessing ManageOne Tenant Portal, for example, https://tenant.demo.com
    2. Select your region and then project from the drop-down list on the top menu bar.
    3. Choose Console > Application > FusionStage from the main menu.

  2. Choose Application Publishing > Application Management.
  3. Access the abnormal application details page and choose the Events tab page on the Instances tab page. View the error information to analyze the cause.
  4. Use the logs to analyze the possible causes.

    • Related processes on nodes in the management zone are abnormal.
      1. Use PuTTY to log in to the manage_lb1_ip node.

        The default username is paas, and the default password is QAZ2wsx@123!.

      2. Run the following command to display process statuses:

        monit summary

        • If any process is running, run the following command:

          monit restart {process name}

        • If any process is not started, contact technical support for assistance.
      3. Run the following command and enter the password of the root user to switch to the root user:

        su - root

        Default password: QAZ2wsx@123!

      4. Run the following command to query the pod status:

        kubectl get pod -n fst-manage

        • If the pod is abnormal, run the following command to restart it:

          kubectl delete pod podname-n fst-manage

          podname indicates the queried pod name.

        • If the pod is normal, contact technical support for assistance.
    • Related processes on nodes in the data zone are abnormal.
      1. Log in to the nodes in the data zone as the paas user.
      2. Run the following command to display process statuses:

        monit summary

        • If any process is running, run the following command:

          monit restart {process name}

        • If any process is not started, contact technical support for assistance.
      3. Locate the cause.
        1. Use PuTTY to log in to manage_lb1_ip node.

          The default username is paas, and the default password is QAZ2wsx@123!.

        2. Run the following command and enter the password of the root user to switch to the root user:

          su - root

          Default password: QAZ2wsx@123!

        3. Run the following commands to view events and error information and rectify the fault. Table 20-2 lists error information.

          kubectl describe {resource type} {resource name} -n namespace

          Table 20-2 Error information

          Error Information

          Meaning and Solution

          fit no node

          The scheduling rules are not fulfilled. Modify the affinity rules of the application and redeploy the application.

          Failed to pull image

          Image files or software packages fail to be obtained. Check whether the image address is correct.

          mount volume failed

          Contact technical support for assistance.

    • If the problem persists, contact technical support for assistance.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1242

Downloads: 12

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