OOM Killer Issues Troubleshooting
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use OOM Killer Issues Troubleshooting on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
When receivedload notificationFrom OOM Killer via email, you should investigate the exact cause of the problem and implement some workarounds. To help you solve this problem, we've analyzed the most common problems and determined effective ways to fix them and prevent them from happening again in the future. Three groups as follows:
- General process- Process that runs by default on the Ruk-Com Cloud container and can be destroyed using the OOM tool.
- High risk process- Memory leaks may occur which require special operations or application code optimizations; Arranged by the type of stack/programming language used, each section provides general guidance related to the appropriate engine as well as solutions to specific process breaking issues.
- leak-free process- Actions that may be terminated by the OOM killer even if they do not represent the root of the problem. The general fix for all such issues is to restart the container to restore the involved processes.
So search the document for the name of the process you received the email notification from to find the desired solution.