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).
Operations Before Troubleshooting

Operations Before Troubleshooting

Background

If you have located the cause of the database fault before troubleshooting, skip this chapter. If you need to analyze the cause of the fault after troubleshooting, perform the following operations to collect the required information.

Procedure

Collect the run logs of the etcd database.

  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 IP of the node where the exception pod resides:

    kubectl get po -nfst-manage -owide | grep etcd | grep -v cse-etcd | grep -v apm-etcd

    etcd-backup-server-paas-10-118-29-146        1/1       Running   0          1d        10.118.29.146   paas-10-118-29-146
    etcd-backup-server-paas-10-118-29-196        1/1       Running   0          1d        10.118.29.196   paas-10-118-29-196
    etcd-backup-server-paas-10-118-29-67         1/1       Running   0          1d        10.118.29.67    paas-10-118-29-67
    etcd-event-server-paas-10-118-29-146         1/1       err       0          1d        10.118.29.146   paas-10-118-29-146
    etcd-event-server-paas-10-118-29-196         1/1       Running   0          1d        10.118.29.196   paas-10-118-29-196
    etcd-event-server-paas-10-118-29-67          1/1       Running   0          1d        10.118.29.67    paas-10-118-29-67
    etcd-network-server-paas-10-118-29-146       1/1       Running   0          1d        10.118.29.146   paas-10-118-29-146
    etcd-network-server-paas-10-118-29-196       1/1       Running   0          1d        10.118.29.196   paas-10-118-29-196
    etcd-network-server-paas-10-118-29-67        1/1       Running   0          1d        10.118.29.67    paas-10-118-29-67
    etcd-server-paas-10-118-29-146               1/1       Running   0          1d        10.118.29.146   paas-10-118-29-146
    etcd-server-paas-10-118-29-196               1/1       Running   0          1d        10.118.29.196   paas-10-118-29-196
    etcd-server-paas-10-118-29-67                1/1       Running   0          1d        10.118.29.67    paas-10-118-29-67

  4. Log in to the node where the exception pod resides as the paas user.
  5. Run the following commands on each VM to collect run logs:

    mkdir -p /tmp/cfe/etcd

    cp /var/paas/sys/log/etcd*/*etcd*.log /tmp/cfe/etcd

  6. Run the following commands to package the run logs:

    cd /tmp/cfe

    tar -zcvf etcd-log-"$(date "+%Y-%m-%d-%H-%M")".tar.gz etcd

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 1143

Downloads: 12

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