Help Center > > FAQs> Usage FAQs> What Can I Do If Resources Are Not Running Properly?

What Can I Do If Resources Are Not Running Properly?

Updated at: Dec 15, 2019 GMT+08:00

The resource status includes Normal, Warning, Alarm, and Silent. Warning, Alarm, or Silent may result in resource exceptions. You can analyze and rectify exceptions based on the following suggestions.

Warning

If a minor alarm or warning exists, the resource status is Warning.

Suggestion: Handle problems based on alarm details.

Alarm

If a critical or major alarm exists, the resource status is Alarm.

Suggestion: Handle problems based on alarm details.

Silent

If the ICAgent fails to collect resource metrics, the resource status is Silent. The causes include but are not limited to:

  • Cause 1: The ICAgent is abnormal.

    Suggestion: In the navigation pane, choose Collection Management > Agent Management. On the page that is displayed, check the ICAgent status, as shown in Figure 1. If the status is not Running, the ICAgent is uninstalled or abnormal. For how to solve the problem, see Table 1.

    Table 1 ICAgent troubleshooting suggestions

    Status

    Suggestion

    Uninstalled

    Install the ICAgent according to Installing the ICAgent.

    Installing

    Wait for 1 minute to install the ICAgent.

    Installation failed

    Uninstall the ICAgent according to Logging In to the Server and Uninstalling the ICAgent and then install it again.

    Updating

    Wait for 1 minute to upgrade the ICAgent.

    Upgrade failed

    Uninstall the ICAgent according to Logging In to the Server and Uninstalling the ICAgent and then install it again.

    Offline

    Ensure that the Access Key ID/Secret Access Key (AK/SK) and Elastic Cloud Server (ECS) agency configurations are correct.

    Faulty

    Submit a service ticket according to Submitting a Service Ticket.

    Figure 1 Checking the ICAgent status
  • Cause 2: Application Operations Management (AOM) cannot monitor the current resource.

    Suggestion: Check whether your resources can be monitored by AOM. Specifically, AOM can monitor hosts, Kubernetes containers, and user processes, but cannot monitor system processes.

  • Cause 3: The local time of the host is not synchronized with the NTP server time.

    NTP Sync Status: indicates whether the local time of the host is synchronized with the NTP server time. The value can be 0 or 1. 0 indicates the synchronized status while 1 indicates the asynchronized status.

    Suggestion: In the navigation pane, choose View Management > Metric Monitoring, and check the NTP Sync Status metric of the host, as shown in Figure 2. If the value of NTP Sync Status is 1, implement synchronization according to Does HUAWEI CLOUD Provide the NTP Server and How Can I Install It.

    Figure 2 Checking the NTP Sync Status metric of the host
  • Cause 4: The resource is deleted or stopped.

    Suggestion:

    • On the ECS page, check whether the host is restarted, stopped, or deleted, as shown in Figure 3.
      Figure 3 Checking whether the host is restarted, stopped, or deleted
    • On the Cloud Container Engine (CCE) page, check whether the service is stopped or deleted, as shown in Figure 4.
      Figure 4 Checking whether the service is stopped or deleted
    • If a service discovery rule is disabled or deleted, the service discovered based on the rule will also be disabled or deleted. On the AOM page, check whether the service discovery rule is disabled or deleted, as shown in Figure 5.
      Figure 5 Checking whether the service discovery rule is disabled or deleted

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel