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-3500 Source-proxy Service Is Unavailable

ALM-3500 Source-proxy Service Is Unavailable

Description

This alarm is reported when access to the Source-proxy service is abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

3500

Major

Communications alarm

Parameters

Parameter Name

Parameter Description

serviceName

Specifies the name of the service that reports the alarm.

namespace

Specifies the namespace of the service that reports the alarm.

Instancename

Specifies the name of the service instance for which the alarm is reported.

srvAddr

Specifies the access address of the service that reports the alarm.

Impact on the System

Source2image fails to bind the code source.

System Actions

None

Possible Causes

The Source-proxy pod is abnormal, or Source2image cannot communicate with Source-proxy.

Procedure

  1. Check the Source-proxy pod status.

    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 Source-proxy pod status is running properly:

      kubectl get pod -n{namespace} |grep source

      {namespace} is the ID of source2image, which you can obtain it by running kubectl get ns -oyaml |grep source2image -C 1 command.

      If the status of the Source-proxy process is Running, the Source-proxy pod is running properly.

      Information similar to the following is displayed, in which swr-source-proxy-8457b4747d-v6l26 indicates the pod name of the Source-proxy process:

      swr-source-proxy-8457b4747d-v6l26   0/1       Running                0          24s
      • If the Source-proxy pod is running properly, go to 3.
      • If the Source-proxy pod is not running properly, go to 1.d.
    4. If the Source-proxy pod is not running properly, perform either of the following operations:
      • Wait about 10 minutes for the health check service to restart.
      • Run the following command to manually restart the pod of the faulty Source-proxy process:

        kubectl delete pod {podname} -n {namespace}

        {podname} and {namespace} indicates the pod name and namesapce value obtained in 1.c.

    5. Check again whether the Source-proxy pod is running properly.
      • If the Source-proxy pod is running properly, go to 1.f.
      • If the Source-proxy pod is not running properly, go to 2.
    6. Perform the Source-proxy operation.
      1. Use a browser to log in to the FusionStage OM zone console.
        1. Log in to ManageOne Maintenance Portal.
          • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
          • The default username is admin, and the default password is Huawei12#$.
        2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
      2. Choose Marketplace > Image Building > Source Code Hosting from the main menu.
      3. Click Bind on the right of the page.
      4. Configure the SVN information by referring to Table 17-2. (Parameters marked with an asterisk (*) are mandatory.)
        Table 17-2 Parameters for binding the SVN information

        Parameter

        Description

        *Binding Name

        Specifies the alias of the bound SVN. The bound name must be unique under each tenant.

        *SVN address

        Specifies the SVN address.

        *Username

        Specifies the username for logging in to the SVN.

        *Password

        Specifies the password for logging in to the SVN.

      5. Click Bind.
    7. Check whether the alarm is cleared.
      • If the alarm is cleared, no further action is required.
      • If the alarm is not cleared, go to 3.

  2. 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. 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 query the IP address of the Source-proxy service:

      kubectl get svc -n {namespace} |grep source

      {namespace} is the ID of source2image, which you can obtain it by running kubectl get ns -oyaml |grep source2image -C 1 command.

      Information similar to the following is displayed, in which 10.247.217.77 indicates the IP address used by Source-proxy to provide services externally.

      swr-source-proxy   NodePort   10.248.206.63   10.247.217.77   31990:31991/TCP   33m
    4. Run the following command to query the network connection of the Source-proxy service:

      curl -k https://{Source-proxy_svc_ip}:31991

      {Source-proxy_svc_ip} indicates the IP address of Source-proxy service queried in 2.c.

      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 3.
      • If the network connection is faulty, go to 2.f.
    5. Contact the network administrator to rectify the network fault. Then perform the operation in 1.f.
    6. Check whether the alarm is cleared.
      • If the alarm is cleared, no further action is required.
      • If the alarm is not cleared, go to 3.

  3. Contact technical support for other issues.

Alarm Clearing

After the alarm is cleared and the Source-proxy operation is performed again, the system automatically clears the alarm.

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: 45035

Downloads: 33

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