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).
GaussDB Faults

GaussDB Faults

Symptom

HDCS cannot provide services and fails to access the database. The cluster list is empty or incorrect.

Possible Causes

  • The HDCS environment is abnormal.
  • The GaussDB process is abnormal.

Troubleshooting Process

  1. The database node where the GaussDB database is located is abnormally shut down or the network is abnormal.
  2. Check whether the GaussDB auto-start monitoring process is abnormal or damaged.

Procedure

  1. Log in to FusionSpere OpenStack OM, filter VMs on the HDCS management plane, and check whether the HDCS Database node is normal. If the node is not in the Running state, contact O&M personnel to restore the VM.
  2. Use PuTTY to log in to the HDCS Database node as the datasight user using the IP address of the HDCS Database node.

    Default account: datasight; default password: Cloud12#$

  3. Run the ps -ef|grep gaussdb command to check whether the gaussdb process is running properly. If yes, the following information is displayed:

    (python_env)[datasight@dbs_gauss1 ~]$ ps -ef| grep gaussdb
    gaussco+  6176     1  0 17:49 ?        00:00:04 /opt/gaussdbcore/app/bin/gaussdb -M primary
    gaussco+  6186  6176  0 17:49 ?        00:00:02 gaussdb: logger process   
    gaussco+  6233  6176  0 17:49 ?        00:00:00 gaussdb: checkpointer process   
    gaussco+  6234  6176  0 17:49 ?        00:00:00 gaussdb: writer process   
    gaussco+  6235  6176  0 17:49 ?        00:00:02 gaussdb: wal writer process   
    gaussco+  6236  6176  0 17:49 ?        00:00:00 gaussdb: autovacuum launcher process   
    gaussco+  6237  6176  0 17:49 ?        00:00:00 gaussdb: archiver process   
    gaussco+  6238  6176  0 17:49 ?        00:00:03 gaussdb: stats collector process   
    gaussco+  6239  6176  0 17:49 ?        00:00:00 gaussdb: auditor process   
    gaussco+  6243  6176  0 17:49 ?        00:00:00 gaussdb: wal sender process REPLICATION 8.26.74.124(52366) streaming 0/6000A98

    If the gaussdb process is not started, switch to the root account, and then switch to the gausscore account and run the gs_ctl start command to start the GaussDB service process.

  4. Run the su - root command to switch to the root user and run the netstat -npl | grep gaussdb command to check the listening port 8635 of the GaussDB service. If the port is running properly, message LISTEN is displayed.

    [root@dbs_gauss1 ~]# netstat -npl | grep gaussdb
    tcp        0      0 8.26.74.123:12211       0.0.0.0:*               LISTEN      6176/gaussdb        
    tcp        0      0 8.26.74.122:8635        0.0.0.0:*               LISTEN      6176/gaussdb        
    tcp        0      0 127.0.0.1:8635          0.0.0.0:*               LISTEN      6176/gaussdb        
    tcp6       0      0 ::1:8635                :::*                    LISTEN      6176/gaussdb

    If the port is not in LISTEN state, switch to the gausscore account and run gs_ctl restart command to restart the GaussDB database.

  5. Refresh the HDCS service page, and check whether the fault is rectified.
Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 4164

Downloads: 22

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