OOM killer "Out of Memory: Killed process" SOLUTIONS / SUMMARY

Ray Van Dolson rvandolson at esri.com
Fri Aug 17 21:45:41 UTC 2007


On Fri, Aug 17, 2007 at 05:34:14PM -0400, Cristian Silva wrote:
> This is great info.
> 
> We are having this problem on a RHEL5 server with 8gb of ram (32bits) since
> some time ago.
> 
> I understand that the hugemem kernel is no longer available in RHEL5, so we
> installed the PAE kernel but it makes no difference, we still have the oom.
> 
> 64bits is not an option at the moment, so if i understand correctly, using
> just 4gb of ram instead of the 8gb that we currently have, could potentially
> solve the oom-killer problem ?
> 

Are you able to try some of the following settings (mentioned earlier
in the thread):

vm.min_free_kbytes = 16384
vm.overcommit_memory = 2
vm.overcommit_ratio = 75
vm.lower_zone_protection = 100
vm.vfs_cache_pressure = 10000

In addition, you can always tweak with the /proc/<pid>/oom_(adj|score)
files in RHEL5 and make VMware impervious to the OOM killer.

Ray




More information about the redhat-list mailing list