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).
Abnormal Slave DatabaseInstances

Abnormal Slave DatabaseInstances

Symptom

The master database instance is normal and the slave database instance is abnormal. MySQL and Redis directories, as well as physical files of the slave database instance are lost.

Troubleshooting

Initial Installation of Database Software
Re-creating the Slave Database Instance
Procedure
  1. Use PuTTY to log in to the slave database node as the paas user.

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

  2. Run following commands to recreate the database:

    cd /opt/paas/oss/manager/apps/DBAgent/bin

    ./dbsvc_tool -cmd repair-db-node -type mysql

    Information similar to the following is displayed:

     success
    NOTE:
    • When recreating slave database, the database process whose slave instance has been lost must be stopped.
    • type indicates the database type to be restored. If the database is Redis, run the following command instead:

      ./dbsvc_tool -cmd repair-db-node -type redis

    • success indicates that the database instance is restored successfully.

  3. For details, see (Method 3) Rebuild the Slave Database Instance.

    NOTE:

    If database instance is abnormal because the standby instance directories are lost, run the ./dbsvc_tool -cmd repair-db-node -type mysql command on the slave instance node, and then rectify based on the replication of the slave database instance.

Verification
  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 commands to check information about database:

    cd /opt/paas/oss/manager/apps/DBAgent/bin

    ./dbsvc_adm -cmd query-db-instance | grep mysql

    Information similar to the following is displayed:

    DBInstanceId                             ClassId  Service Name               Region        Tenant Stage    IP          Port   State   DBType  Version  Role  Rpl Status   MasterID   
    apmdbsvr-10_90_73_163-3@10_90_73_164-3   primary  apmdbsvr-10_90_73_164-3    cn-global-1   om     Product 10.90.73.164 32082  Up      mysql   5.6.35   Master  Normal       apmdbsvr-10_90_73_163-3   
    apmdbsvr-10_90_73_178-21@10_90_73_179-21 primary  apmdbsvr-10_90_73_179-21   cn-global-1   om     Product 10.90.73.179 32080  Up      mysql   5.6.35   Slave Normal       apmdbsvr-10_90_73_178-21

    You only need to pay attention to the value of Rpl Status.

    If the statuses of Master and Slave are Normal, the database is running properly.

    If the statues are abnormal, contact technical support.

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22715

Downloads: 37

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