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 Alarm and Event Reference 04

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).
ALM-15016 GaussDB Connection Failure

ALM-15016 GaussDB Connection Failure

Alarm Description

This alarm is reported when the connection to the database fails due to database fault, process stopping, or network disconnection.

Attribute

Alarm ID

Alarm Severity

Alarm Type

15016

Major

Communications alarm

Alarm Parameters

Parameter

Description

apiIp

Specifies the IP address of the APIServer node that fails to connect to the database.

jdbcUrl

Specifies the URL for connecting to the database.

Impact on the System

Functions such as topic creation and deletion and group deletion are not available.

Possible Causes

  • The database is shut down.
  • The database is faulty.
  • The network is disconnected.

Procedure

  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 obtain the project ID:

    kubectl get node | grep dms

    f8fd7a56b3d14234b89870795bd6b571   dms-np-api-4d2cc797-b9w28                        Ready                         <none>    2d        v2.3.27-FusionStage6.5.RP3-B100-dirty

    In the preceding information, the content in bold is the obtained project ID.

  4. Run the following command to obtain the pod of APIServer:

    kubectl get po -n f8fd7a56b3d14234b89870795bd6b571 -owide | grep dms-apiserver

    In the preceding command, f8fd7a56b3d14234b89870795bd6b571 is the project ID obtained in 3.

    dms-apiserver-4d2cc797-5bdf66b69d-425pt           1/1       Running            0          4h        192.168.34.7     dms-np-api-4d2cc797-b9w28
    dms-apiserver-4d2cc797-5bdf66b69d-gx25l           1/1       Running            0          4h        192.168.34.245   dms-np-api-4d2cc797-f6t9l

    In the preceding information, the parts in bold indicate the pod and IP address of two APIServers respectively.

  5. Run the following command to access the APIServer container:

    kubectl exec -it dms-apiserver-4d2cc797-5bdf66b69d-425pt -n f8fd7a56b3d14234b89870795bd6b571 bash

    In the preceding command, dms-apiserver-4d2cc797-5bdf66b69d-425pt is the pod of any APIServer obtained in 4.

    f8fd7a56b3d14234b89870795bd6b571 is the project ID obtained in 3.

  6. Run the following command to obtain the IP address for logging in to the GaussDB database:

    grep -rn db_url

    apiserver/jobs/mas/config/dms.app.properties:5:db_url=jdbc:postgresql://192.168.34.26:32080/dms

    In the preceding information, the content in bold indicates the IP address for logging in to the GaussDB database.

  7. Run the ping command to connect to the GaussDB IP address obtained in 6 and check whether the IP address can be pinged.

    • If yes, go to 10.
    • If no, go to 8.

  8. Run the following command to obtain the IP address and name of the node where the dms-gaussdb is deployed:

    • Region Type III scenario
      1. Run the following command to obtain the IP address and name of the node where the dms-gaussdb is deployed:

        kubectl get po -n f8fd7a56b3d14234b89870795bd6b571 -owide | grep dms-gaussdb

        In the preceding command, f8fd7a56b3d14234b89870795bd6b571 is the project ID obtained in 3.
        dms-gaussdb-service-4d2cc797-858f7c9746-cpt28     1/1       Running            0          2d        192.168.34.85    middleware-gaussdb-nodes-d848247f-qcjwq
        dms-gaussdb-service-4d2cc797-858f7c9746-fkm2r     1/1       Running            0          2d        192.168.34.40    middleware-gaussdb-nodes-d848247f-8znpr

        In the preceding information, the parts in bold indicate the IP address and node name of the node where the dms-gaussdb is deployed.

    • Region Type I and Region Type II scenarios
      1. Perform the operations provided in 8.a.
      2. Run the following command to obtain the IP address and name of the node where the dms-gaussdb is deployed:

        kubectl get node -owide | grep middleware-gaussdb-nodes-d848247f-qcjwq

        In the preceding command, middleware-gaussdb-nodes-d848247f-qcjwq indicates the node name of the node where the dms-gaussdb is deployed obtained in 8.a.

  9. Run the ping command to check whether the queried IP address of the GaussDB database can be pinged.

    • If yes, the VIP binding of GaussDB database is abnormal, and solve the VIP binding problem.
    • If no, solve the network problems and check whether the alarm is automatically cleared when the network connectivity is available. If the alarm is not cleared, go to 10.

  10. Run the following command to log in to the dms-gaussdb node:

    ssh 192.168.34.85

    In the preceding command, 192.168.34.85 is the IP address obtained in 8.

  11. Run the following command to check the database status:

    /opt/gaussdb/ha/tools/had query

    Check whether the values of both RESS and STAT are normal. If yes, the database service is running properly, as shown in Figure 17-5.

    Figure 17-5 Database status
    • If yes, the GaussDB database is not running properly. You need to solve the database running problems.
    • If no, go to 12.

  12. On the node where the GaussDB database is deployed, view the log /var/log/postgresql/gaussdb-xxx.log and rectify the fault based on the log information.
  13. If the alarm persists, contact Huawei technical support.

Alarm Clearing

After the fault is rectified, the system automatically clears the alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 49529

Downloads: 33

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