OOM - seems false?

Maybe I am reading these alerts wrong, but to me they seem like a false positive even though they do very much in fact kill the process they say they killed (problematic). Could someone help break down what the alert is actually telling us please. From the alert below, am I misreading that it detected low memory at 2.35Gb/16 being used? Why is it terminating processes for low memory if 13Gb is free? Thanks for any help in advance!


======================

Out of memory: The process "mysqld" was terminated because the system is low on memory.   
    In order to avoid a system crash due to low memory, the kernel terminated the process named "mysqld" with the PID "16271".
Server    ***************  
Primary IP Address    *****************    
Process Name    mysqld    
Event Time    Thursday, February 9, 2017 at 11:51:18 PM UTC    
PID    16271    
Process Total Virtual Memory    7466628kB    
Process Anonymous Resident Set Size    1125952kB    
Process File Resident Set Size    0kB    
Process OOM Score    116    
Status    Out of Memory ?    
Memory Information    Used    2.35 GB    
Available    13.04 GB    
Installed    15.39 GB    
Load Information    16.19 49.61 34.72   
Uptime    1 day, 8 hours, 44 minutes, and 33 seconds    
IOStat Information    avg-cpu: %user %nice %system %iowait %steal %idle 25.07 0.09 4.85 3.13 21.15 45.72 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn vda 83.91 340.20 1347.72 40100227 158859226 vdb 49.30 1609.61 329.61 189728593 38852296 dm-0 160.02 296.86 1252.35 34992257 147618240 dm-1 34.62 43.12 95.37 5082104 11240964   
Top Processes    PID    Owner    CPU %    Memory %    Command    
14915    mysql    92.98    5.88    /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/vps.err --open-files-limit=10000 --pid-file=/var/lib/mysql/vps.pid   
18909    user1 86.15    1.14    /usr/bin/php /home/user1/public_html/index.php   
3455    root    4.87    0.38    /usr/local/cpanel/3rdparty/bin/clamd   
3021    root    0.12    0.27    cxswatch   
3024    root    5.23    0.15    cxswatch - sleeping   

For addtional details, see the attached dmesg log dump.

Preview of "oom_dmesg.txt"   
[117649.865024] [14668] 99 14668 21715 222 41 415 0 httpd [117649.865026] [14669] 99 14669 21715 230 41 413 0 httpd [117649.865027] [14670] 99 14670 21715 231 41 414 0 httpd [117649.865029] [14671] 99 14671 116 1 5 0 0 suphp [117649.865030] [14672] 99 14672 21715 218 41 417 0 httpd [117649.865031] [14673] 99 14673 21715 553 40 101 0 httpd [117649.865033] [14674] 0 14674 21682 521 39 104 0 httpd [117649.865034] [14675] 99 14675 21715 553 41 101 0 httpd [117649.865036] Out of memory: Kill process 16271 (mysqld) score 116 or sacrifice child [117649.868090] Killed process 16271 (mysqld) total-vm:7466628kB, anon-rss:1125952kB, file-rss:0kB

SB-Nick

February 10, 2017 01:13

Is this a VPS by chance?

thinkshovels

February 10, 2017 02:19

Kvm.

cPanelMichael

February 10, 2017 15:19

Hello, The following document is useful for understanding how the OOM Killer works: OOM Killer - linux-mm.org Wiki You may also find this URL helpful: How to diagnose causes of oom-killer killing processes Thank you.

OOM - seems false?

Comments

Didn't find what you were looking for?