Your log messages may vary depending on Linux distribution and system configuration. The log note here shows the process killed was mysqld with pid 9163 and OOM score of 511 at the time it was killed. kernel: Out of memory: Kill process 9163 (mysqld) score 511 or sacrifice child Actual log marks of OOM killed processes would look something like the following. Grep goes through all logs under the directory and therefore will show at least the just ran command itself from the /var/log/auth.log. sudo grep -i -r 'out of memory' /var/log/ You can search the logs for messages of out of memory alerts. If a task gets killed to save memory, it gets logged into various log files stored at /var/log/ Suddenly killed tasks are often the result of the system running out of memory, which is when the so-called Out-of-memory (OOM) killer steps in. Try UpCloud for free! Deploy a server in just 45 seconds Process stopped unexpectedly This debugging guide aims to explain how to identify how much of the resources are actually being used, and how to recognise real resource outage issues.

The system holds a lot more in RAM than just application data, most importantly mirrored data from storage drives for faster access.

Linux by its design aims to use all of the available physical memory as efficiently as possible, in practice, the Linux kernel follows a basic rule that a page of free RAM is wasted RAM. Some unexpected behaviour on the server side may at times be caused by system resource limitations.

Ubuntu monitor ram usage