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-73109 Memory Usage of Key UVP Processes Exceeds the Thresholds

ALM-73109 Memory Usage of Key UVP Processes Exceeds the Thresholds

Description

The system detects the memory usage of the key UVP processes every 5 seconds. This alarm is generated when the memory usage is greater than or equal to the alarm threshold. This alarm is cleared when the memory usage is less than the alarm threshold.

Attribute

Alarm ID

Alarm Severity

Auto Clear

73109

Minor

Yes

Parameters

Name

Meaning

Name

Specifies the alarm name.

Object ID

Specifies the alarm object ID.

If an alarm is generated for a resource, such as a host or VM, the value is the resource ID, for example, the host ID. If an alarm is generated for a service module, the value is the ID of the service module, for example, FusionSphere OpenStack OM.

Object Type

Specifies the alarm object type. Example values: host and heart beat (indicating the heartbeat detection system).

Object Name

Specifies the object for which the alarm is generated.

If an alarm is generated for a resource, such as a host or VM, the value is the resource name, for example, the host name. If the alarm is generated for a service module, the value is the name of the service module, for example, FusionSphere OpenStack OM.

Component Type

Specifies the type of the component that reports the alarm, for example, FusionSphere OpenStack or FusionSphere OpenStack OM.

Component

Specifies the component that reports the alarm.

Fault Location Info

Provides detailed information about the alarm object, usually in the form of key value pairs. For example: host=*****,portName=###, indicating that the alarm is generated on port ### of host ****.

Additional Info

Provides additional information about the alarm, usually in the form of key value pairs. For example: Threshold=70,current_value=75, indicating that the alarm is generated because the threshold is 70 and the current value is 75.

Generated At

Specifies the time when the alarm is generated.

Cleared At

Specifies the time when the alarm is cleared.

Clearance Type

Specifies how the alarm is cleared (manually or automatically).

Cleared By

Specifies the name of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Clearance User ID

Specifies the ID of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Cleared At

Specifies the system view (tenant view or administrator view) in which the alarm is manually cleared.

SN

Specifies the sequence number of the alarm.

Impact on the System

The available memory of UVP is reduced, even insufficient.

Possible Causes

  • The memory of the virtual management process leaks.

Procedure

  1. Determine the name of the abnormal process based on the alarm object.

    • If the process name is libvirtd, hirmd, vBMC_agentd, UVPHostd, virtlogd, systemd-journal, dbus-daemon, rsyslogd, sysalarm, sysmonitor, or getosstat, go to 2.
    • If the process name is systemd, go to 3.
    • If the process name is ovs-vswitchd or ovsdb-server, go to 4.
    • If the process name is a VM name, go to 5.

  2. Use PuTTY to log in to the host, switch to user root, and run the following command to restart the service corresponding to the process (wait for 30 seconds and check whether the alarm is automatically cleared):

    systemctl restart ${SERVER_NAME}
    NOTE:

    ${SERVER_NAME} indicates the name of the service corresponding to the process.

    You need to re-specify ${SERVER_NAME} for the following processes:

    • systemd-journal, corresponding to the systemd-journald service
    • dbus-daemon, corresponding to the dbus service
    • rsyslogd, corresponding to the rsyslog service
    • If yes, no further action is required.
    • If no, go to 6.

  3. Use PuTTY to log in to the host. Then run the following command to re-load systemd (wait for 30s and check whether the alarm is automatically cleared):

    systemctl daemon-reload
    • If yes, no further action is required.
    • If no, go to 6.

  4. Run the uvplog -o host -t hyp command to collect logs and contact Huawei technical support.
  5. Collect logs in /var/log/libvirt/ and contact Huawei technical support.
  6. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47476

Downloads: 33

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