

Memory issues can be resolved by analyzing the logs which are stored in the kernel log /var/log/kern.log or in the syslog /var/log/syslog location. Here are some examples of log data that denote memory issues While troubleshooting memory issues, spotting such events are essential as they help you to understand what process caused the memory problem. The occurrence of such events indicates that the server killed the process intentionally to free up memory. When a critical process is to be initiated and it requires more memory than what's available, the kernel starts killing processes, and records these events with strings such as "Out of Memory" in the log data. As a result, it kills the process that uses the most memory first. The primary objective of OOM killer is to kill the least number of processes while maximizing the memory space.

The next response by the kernel would be to kill the process that takes a lot of memory.The OOM killer (Out Of Memory) is the mechanism that the kernel uses to recover memory on the system. When the RAM and the swap space are full, the server runs out of memory. The performance of a server depends on its memory too.
