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-38015 SWR Unavailable

ALM-38015 SWR Unavailable

Description

This alarm is reported when the network connection between the SWR application server and the database is abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

38015

Major

Communications alarm

Parameters

Parameter Name

Parameter Description

alarmName

Indicates the alarm name.

objectInstance

Indicates the abnormal service address and instance.

additionalInformation

Indicates the returned error message.

probableCause

Indicates the possible cause.

Impact on the System

The SWR service is affected.

System Actions

None

Possible Causes

The database stops working, or the network connection between the SWR application server and the database is abnormal.

Procedure

  1. Check whether the alarm "ALM-38003 ETCD Operation Error" is generated.

  2. Check the pod status of SWR.

    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 check whether the pod status of SWR is normal:

      kubectl get pod -n fst-manage |grep swr-api-server

    4. Check whether the SWR service processes are running properly.

      If the SWR service process status is Running, the pod status of SWR is normal. For example:

      [paas@shaphicpra12303 swr]$ kubectl get pod -n fst-manage |grep swr-api-server
      swr-api-server-2921043366-8f0cr               1/1       Running   0          4d
      swr-api-server-2921043366-94zls               1/1       Running   0          4d
      swr-api-server-2921043366-fmzc2               1/1       Running   0          4d

      In the preceding information, the column where swr-api-server-2921043366-8f0cr locates lists the pod names mapping the SWR processes.

      • If the SWR service processes are running properly, go to 3.
      • If the SWR service processes are running improperly, go to 2.e.
    5. If the pod status of SWR is abnormal, perform either of the following operations:
      • If the pod status of SWR is abnormal, perform either of the following operations:
      • Run the following command to manually restart the pod on which abnormal SWR service processes run:

        kubectl delete pod podname -n fst-manage

        For details about podname, see 2.c.

    6. Check whether the pod status of SWR is normal.
      • If yes, go to 3.
      • If no, go to 4.
    7. Check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 3.

  3. Check whether the network is connected.

    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. Check the IP address of the SWR service.
      kubectl get cm -nfst-manage swr-config -oyaml|grep loadbalancer_ip
        loadbalancer_ip: 10.106.68.80

      10.106.68.80 indicates the IP address used by SWR to provide services for external systems.

    3. Run the following command to query the network connection of the SWR service:

      curl -k https://{swr_svc_ip}:20202/dockyard/v2/namespaces

      The IP address of {swr_svc_ip} is the IP address of the SWR service queried in 3.a.

      If no information is returned, the network is faulty. If any information is returned, the network connection is normal.

      • If the network connection is normal, go to 4.
      • If the network is faulty, contact the network administrator to rectify the fault.
    4. If the network is faulty, contact the network administrator to rectify the fault.
      • If yes, no further action is required.
      • If no, go to 4.

  4. Contact technical support for assistance.

Alarm Clearing

This alarm is automatically cleared when SWR is normally used.

Related Information

In the actual environment, the database response delay may occur due to factors such as network or database configurations. In this case, no alarms are generated.

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34756

Downloads: 31

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