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


To have a better experience, please upgrade your IE browser.


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-73203 Component Fault

ALM-73203 Component Fault


OpenStack periodically (default interval: 90 seconds) checks the statuses of components on each host. This alarm is generated when a component on a host is abnormal. If this alarm is generated and automatically cleared during the host reconstruction or configuration change, ignore the alarm.


Alarm ID

Alarm Severity

Auto Clear







Fault Location Info

host_id: specifies the ID of the host for which the alarm is generated.

Additional Info

  • detail_info:
    • component fault: specifies that the component is faulty.
    • host: specifies the ID of the host for which the alarm is generated.
    • components: specifies the name of the component for which the alarm is generated
  • host_id: specifies the ID of the host for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.

Impact on the System

A component in an abnormal state has adverse impact on services on the host.

Possible Causes

  • The resources on the host are insufficient, which forces the component to stop.
  • A fault occurs on the component.


  1. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

    To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
    • Region Type I scenario:

      Cascading system: Cascading-ExternalOM-Reverse-Proxy

      Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

    • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  2. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

Check system resources.

  1. Run the following command to check whether the system resources are sufficient:

    grep -i 'out of memory' /var/log/messages |grep -v grep

    Information similar to the following is displayed:

    2019-01-03T21:09:41.543181+08:00|err|kernel[-]|[63624.912407] Memory cgroup out of memory: Kill process 26511 (java) score 51 or sacrifice child

    Check whether "out of memory" is contained in the command output.

    • If yes, the system resources are insufficient. In this case, contact technical support for assistance.
    • If no, go to 4.

Check whether components are faulty.

  1. Check whether any of the following alarms is generated. If there is any alarm, clear the alarm.

    1. ALM-6010 Time Difference Between the NTP-Server and the External Clock Source Exceeds Threshold Value
    2. ALM-6015 NTP Server Failed to Connect to the External Clock Source or the External Clock Source Failed
    3. ALM-6017 Faulty Host
    4. ALM-6022 Heartbeat Communication Between the Host and the NTP Server Interrupted
    5. ALM-6028 Time Difference Between the NTP-Client and the NTP-Server Exceeds 60 Seconds
    6. ALM-73010 Faulty File System
    7. ALM-73201 HAProxy Backend Services Fault
    8. ALM-73401 Faulty RabbitMQ Service

  2. Obtain the name of the faulty component based on the components parameter in the alarm additional information. Check whether the component is included in the following components:

    1. GaussDB fault troubleshooting method: GaussDB Component Troubleshooting
    2. Keystone fault troubleshooting method: Keystone Component Troubleshooting
    3. RabbitMQ fault troubleshooting method: RabbitMQ Component Troubleshooting
    4. nova-compute fault troubleshooting method: nova-compute Component Troubleshooting
    5. nova-api fault troubleshooting method: nova-api Component Troubleshooting
    6. nova-scheduler fault troubleshooting method: nova-scheduler Component Troubleshooting
    7. nova-conductor fault troubleshooting method: nova-conductor Component Troubleshooting
    8. nova-proxy fault troubleshooting method: nova-proxy Component Troubleshooting
    9. fc-nova-compute fault troubleshooting method: fc-nova-compute Component Troubleshooting
    10. vmware-nova-compute fault troubleshooting method: vmware-nova-compute Component Troubleshooting
    11. cinder-volume fault troubleshooting method: cinder-volume Component Troubleshooting
    12. cinder-proxy fault troubleshooting method: cinder-proxy Component Troubleshooting
    13. nova-compute-ironic fault troubleshooting method: nova-compute-ironic Component Troubleshooting
    14. Glance fault troubleshooting method: Glance Component Troubleshooting
    15. neutron-server fault troubleshooting method: neutron-server Component Troubleshooting
    16. neutron-l3-service-agent fault troubleshooting method: neutron-l3-service-agent Component Troubleshooting
    17. neutron-vrouter fault troubleshooting method: neutron-vrouter Component Troubleshooting
    18. neutron-l3-nat-agent fault troubleshooting method: neutron-l3-nat-agent Component Troubleshooting
    19. neutron-cascading-proxy fault troubleshooting method: neutron-cascading-proxy Component Troubleshooting
    20. neutron-openvswitch-agent fault troubleshooting method: neutron-openvswitch-agent Component Troubleshooting
    21. neutron-garbage-collector fault troubleshooting method: neutron-garbage-collector Component Troubleshooting
    22. neutron-l3-dummy-agent fault troubleshooting method: neutron-l3-dummy-agent Component Troubleshooting
    23. neutron-dvr-compute-agent fault troubleshooting method: neutron-dvr-compute-agent Component Troubleshooting
    24. neutron-dhcp-agent fault troubleshooting method: neutron-dhcp-agent Component Troubleshooting
    25. neutron-metadata-agent fault troubleshooting method: neutron-metadata-agent Component Troubleshooting
    26. neutron-sriov-nic-agent fault troubleshooting method: neutron-sriov-nic-agent Component Troubleshooting
    27. neutron-evs-agent fault troubleshooting method: neutron-evs-agent Component Troubleshooting
    28. neutron-vc-vswitch-agent fault troubleshooting method: neutron-vc-vswitch-agent Component Troubleshooting
    29. neutron-l3-agent fault troubleshooting method: neutron-l3-agent Component Troubleshooting
    30. neutron-ipv6-vrouter fault troubleshooting: neutron-ipv6-vrouter Component Troubleshooting
    31. neutron-elb-proxy fault troubleshooting: neutron-elb-proxy Component Troubleshooting
    32. neutron-nat-gw-dataplane fault troubleshooting: neutron-nat-gw-dataplane Component Troubleshooting
    33. neutron-nat-gw-data-agent fault troubleshooting: neutron-nat-gw-data-agent Component Troubleshooting
    34. neutron-ipv6-service-agent fault troubleshooting: neutron-ipv6-service-agent Component Troubleshooting
    35. neutron-ngfw-agent fault troubleshooting: neutron-ngfw-agent Component Troubleshooting
    36. neutron-fw-proxy fault troubleshooting: neutron-fw-proxy Component Troubleshooting
    37. neutron-ngfw-vpn-agent fault troubleshooting: neutron-ngfw-vpn-agent Component Troubleshooting
    38. ceilometer-agent-compute fault troubleshooting method: ceilometer-agent-compute Component Troubleshooting
    39. ceilometer-agent-hardware fault troubleshooting method: ceilometer-agent-hardware Component Troubleshooting
    40. MongoDB fault troubleshooting method: MongoDB Component Troubleshooting
    41. ceilometer-collector fault troubleshooting method: ceilometer-collector Component Troubleshooting

  3. If the fault persists, contact technical support for assistance.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 36004

Downloads: 31

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