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).
Docker Troubleshooting

Docker Troubleshooting

Symptom

  • Docker is suspended.
  • The node where Docker resides and the corresponding pod are abnormal.

Possible Causes

High-concurrent requests cause Docker suspension.

Troubleshooting Method

  1. Use PuTTY to log in to the om_core1_ip node.

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

  2. Run the following command to check whether the node is normal:

    kubectl get nodes --all-namespaces

    default paas-10-120-193-12 Ready 4h
    default paas-10-120-193-243 Ready 4h
    default paas-10-120-193-9 NotReady 4h
    manage manage-cluster1-42074173-09j3n Ready 2h

    The preceding command output shows that paas-10-120-193-9 is abnormal.

  3. Check whether the abnormality is caused by Docker.

    1. Run the following command to obtain the IP address of the abnormal node:

      kubectl get nodes NODENAME -n NAMESPACE -o yaml

      NODENAME indicates the name of the abnormal node. NAMESPACE indicates the namespace of the abnormal node.

      spec:
      address: 10.120.192.136
      externalID: manage-cluster1-42074173-09j3n
      loginSecret:
      name: manage-cluster1-42074173-09j3n

      The preceding command output shows that the IP address is 10.120.192.136.

    2. Log in to the abnormal node as user paas, switch to user root, and run the following command:
      docker ps
      • If the output is displayed normally, Docker is not suspended.
      • If the output is not displayed for a long time, perform the subsequent step, because Docker is suspended.

  4. Run the following command to restart Docker:

    service docker restart

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23093

Downloads: 37

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