Before you modify the configuration or data of an instance, we recommend that you create a snapshot first to improve fault tolerance and ensure data security.

Procedure

Use the following information to troubleshoot instance OOM.

Information point

Method to obtain information

Description

Information point	Method to obtain information	Description
OOM occurrence time and frequency	Linux system log	Log path is as follows: /var/log/messages
OOM occurrence time and frequency		Business application log	Based on the OOM occurrence time, check the OOM cause in the application log of the target business.
System load of Linux instance	Cloud Monitor	It is recommended to use Cloud Monitor to view your instance load information. For details, refer to Viewing cloud product monitoring data.
Business load	Business application log	Based on the OOM occurrence time, check the OOM cause in the application log of the target business.
Application log when OOM occurs	Business application log

Select an appropriate handling method based on the actual OOM cause:

Insufficient memory of the current Linux instance to support business operations: You can upgrade the instance memory. For details, see Changing instance types.

Business application defects: You can optimize the business code based on issues in the application logs of your business.

tip

Here, the business refers to the third-party business in a Linux instance. We recommend contacting the corresponding business provider to fix the issue.

Last updated: 2026.04.13 16:50:03

Public security network record in Beijing: No. 11010802032137