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).
Container with Residual Canal Component Troubleshooting

Container with Residual Canal Component Troubleshooting

Symptom

Multiple functions of FusionStage are not available for use.

Possible Causes

The service endpoint of the container where the canal component resides fails to be cleared during startup or shutdown of the canal component. As a result, new containers fail to be started.

Troubleshooting Method

  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 and enter the password of the root user to switch to the root user:

    su - root

    Default password: QAZ2wsx@123!

  3. Run the following command to query the node status:

    kubectl get nodes --all-namespaces

  4. If a node is in the NotReady state, run the following command to obtain the IP address of this faulty node:

    kubectl get nodes NODENAME -o yaml -n NAMESPACE|grep address

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

      addresses:
      - address: 10.120.193.1
      - address: 10.120.193.1
      - address: paas-10-120-193-1

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

  5. Determine whether this problem is caused by the failure to clear the service endpoint of the container where the canal component resides.

    Log in to the faulty node as the paas user and run the following command:

    monit summary

    Check whether the canal component is in the Status ok state.

     docker   Status okProgram
     canal    Not monitored  Program

    If no, run the following command to check whether there is error information "service endpoint with name canal_agent already exists" in the log:

    journalctl -n

    level=error msg="Handler for POST /v1.23/containers/77ff5b738be9ce0bee8f53d4745b972ba64589c9785107038b879dc1261b8355/start returned error: service endpoint with name canal_agent already exists" canal    

    If yes, this problem is caused by the failure to clear the service endpoint.

  6. Run the following command to stop starting the canal process:

    monit stop canal

  7. Run the following command to query the ID of the container with the service endpoint not cleared:

    sudo docker ps -a|grep canal

    31b1731582ec        canal-agent:latest                                          "/agent -LogOutput /v"   9 minutes ago       Up 9 minutes                           canal_agent

    ID of the container: 31b1731582ec

  8. Run the following command to delete the container:

    sudo docker rm CONTAINERID

    CONTAINERID indicates the container ID obtained in 5.

  9. Run the following command to clear the service endpoint:

    sudo docker network disconnect -f host canal_agent

  10. Run the following command to start all processes:

    monit start all

  11. If the fault persists, contact technical support for assistance.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1958

Downloads: 12

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