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).
Non-Database System Troubleshooting

Non-Database System Troubleshooting

Non-database system faults (for example, an OS fault) cannot be rectified through the database restoration mechanism.

Single Database Node Fault

Symptom

The OS of a single database node cannot be logged in or started. As a result, the database cannot run normally.

Possible Causes

The system disk is read-only.

Troubleshooting Method

Use the same image as the faulty node to rebuild the VM and assign the same IP address to the VM. Then, reinstall the database.

Procedure
  1. Log in to another database node that is not faulty as the database installation user gaussdb.
  2. Run the following command and enter the password of user root as prompted to switch to user root (the default password is Cloud12#$):

    sudo su - root

  3. Run the following commands to check whether the database node status is normal:

    source /etc/profile

    service gaussdb query

    • If the query result is consistent with that shown in the preceding figure, the database node status is normal. Go to 4.
    • If the query result is inconsistent with that shown in the preceding figure, the database node status is abnormal. Rectify the fault by following the instructions provided in section The Master and Slave Database Nodes Are Faulty.

  4. Rebuild the faulty database VM and initialize it.
  5. Enter http://DMK floating IP address:8443 in the address box of the browser and log in to DMK using the DMK account for installing the database.

    The default username is gaussdb, and the default password is Cloud12#$.

  6. In the navigation pane on the left, choose Deploy Guide.
  7. On the Service Configuration page, click GaussdbHA under the Third-Party Components tab and configure the following parameters:

    • Select Version: the same version as that deployed on the master database node
    • Select Action: Deploy
    • Select Region: local
    • Host Repository: NO
    • Blue-Green Deployment: NO

  8. Click Next to switch to the Hosts and User Configuration page.
  9. Select the required team and account.
  10. Modify the configuration file.

    Delete the node that is not faulty in the Hosts Configuration File. Retain only the node where the database needs to be reinstalled.

  11. Click Execute to install the database on the rebuilt VM.
  12. Log in to the database node as the database installation user and run the following commands to check the database status:

    source /etc/profile

    service gaussdb query

    If the command output is similar to the preceding figure, no further action is required. If the command output is different from the preceding figure, contact technical support for assistance.

The Master and Slave Database Nodes Are Faulty

Problem Description

The operating systems of the master and slave database nodes cannot be logged in or cannot be started, and the database cannot run properly.

Possible Causes

The system disk is read-only.

Locating Method

Use the same image as the faulty node to rebuild the VM and assign the same IP address to the VM. Then, reinstall the database.

Procedure
  1. Check whether a recent remote backup of the faulty database is available.

    • If yes, go to 2.
    • If no, contact technical support for assistance.

  2. Recreate the VMs of the master and slave database nodes by performing steps provided in Cloud Service Management Plane Fault Diagnosis.
  3. Contact technical support to install the database on the master and slave database nodes.
  4. Restore data by performing steps provided in section "Backing Up Combined API/VPC/API Gateway/TaskCenter/SDR/CCS Data" > "Full Data Restoration" in FusionCloud 6.3.1.1 Backup and Restoration Guide.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22575

Downloads: 37

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