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-3008 File Operation Processes Are Abnormal

ALM-3008 File Operation Processes Are Abnormal

Description

This alarm is generated when the background processes related to file operations are abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

3008

Major

Communication 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

Files in the system fail to be stored, downloaded, and synchronized.

System Actions

None

Possible Causes

Data fails to be read due to the network fault.

Procedure

Figure 17-4 shows the process for handling the alarm.

Figure 17-4 Alarm handling flowchart
  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. Check whether SWR instances are working properly.

    Run the kubectl get pod -owide -n fst-manage |grep swr-api-server command to obtain all SWR instances and check whether the instance status is Running.

    swr-api-server-4042020123-g3cx4            1/1       Running   0          9d        172.16.6.6       manage-cluster5-3063fc5a-t4c0v
    swr-api-server-4042020123-nk8x3            1/1       Running   0          9d        172.16.3.6       manage-cluster4-3063fc5a-n41xn
    swr-api-server-4042020123-z53ws            1/1       Running   0          9d        172.16.10.5      manage-cluster4-3063fc5a-bzdfd
    • If yes, go to 4.
    • If no, go to 8.

  4. Locate the SWR instance node. Run the kubectl describe pod swr-api-server-4042020123-g3cx4 -n fst-manage|grep Node command. swr-api-server-4042020123-g3cx4 indicates the instance name, which can be obtained from the dispalyed information in 3.

    Node:           manage-cluster5-3063fc5a-t4c0v/10.154.251.60

  5. Log in to the SWR instance node as the root user.
  6. Run the df -h command to check whether the disk space is insufficient.

    • If the disk space is insufficient, go to 9.
    • If the disk space is sufficient, go to 7.

  7. Run the top command to check whether system resources are insufficient.

    • If system resources are insufficient, go to 9.
    • If system resources are sufficient, go to 8.

  8. Follow the instructions in section ALM-13 Pod Is Abnormal to handle the SWR instance exception if any.
  9. Clear disk or system resources.
  10. Contact technical support for other issues.

Alarm Clearing

This alarm is automatically cleared when the background processes related to file operations are restored.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37764

Downloads: 31

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