-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Oguz Yilmaz said the following on 30/12/2013 09:02:
I have continous oom&panic situation unresolved. I am not sure system fills up all the ram (36GB). Why this system triggered this oom situation? Is it about some other memory? highmem? lowmem? stack size?
Had a similar issue on some CentOS servers and solved by changing the memory overcommit [1] strategy of Linux kernel.
CentOS via its upstream sets /proc/sys/vm/overcommit_memory [2] to zero, better to set il to 2 and play with /proc/sys/vm/overcommit_ratio (some say that it should be 50, other 80)
Try to put this in /etc/sysctl.conf and see if anithing changes
vm.overcommit_memory = 2 vm.overcommit_ratio = 80
Other useful links: http://www.hskupin.info/2010/06/17/how-to-fix-the-oom-killer-crashe-under-li... http://www.win.tue.nl/~aeb/linux/lk/lk-9.html#ss9.6 http://www.dbasquare.com/2012/05/31/mysql-oom-killer-and-everything-related/
Ciao, luigi
[1] http://opsmonkey.blogspot.it/2007/01/linux-memory-overcommit.html [2] http://www.kernel.org/doc/man-pages/online/pages/man5/proc.5.html
- -- / +--[Luigi Rosa]-- \
It is useless to send armies against ideas. --Georg Brandes