Ahh, the OOM killer. :)
I typically only run in to this error when students accidentally put a
fork in a loop and create a "fork bomb".
In *nix, you can reduce the chance of this happening by putting a limit
in the /etc/security/limits.conf, like:
* hard nproc 200 # adjust this number to taste
root - # make sure root can still have no limit
That way no single user can have over (say) 200 processes, the second
line allows root to go unlimited.
You can also put some limits on RAM, etc. Some of these settings may be
Having a limit can be bad, but not as bad as having the OOM killer come
out on the loose.
Once the grim reaper comes out bad things happen. :)
East Carolina University
College of Technology and Computer Science
Science and Technology Bldg. Suite 100
Greenville, NC 27858-4353
252-737-1940, Fax 252-328-4250
From: Duhon, Gregory D <gregory.du...@csun.edu>
To: 'firstname.lastname@example.org' <email@example.com>
Cc: Olsen, Chris <chris.ol...@csun.edu>, Lee Thompson
<lee.thomp...@csueastbay.edu>, Tadesse, Berhanu <btade...@calstate.edu>
Subject: Kernel Out of Memory error message
Date: Wed, 6 Oct 2010 13:30:14 -0400
Have any of you experienced this error message within your VCL
environment? If so, how did you solve it?
Oct 5 19:38:05 vclesx02 kernel: Out of memory: Killed process 28055,
UID 0, (vmware-vmx).
We currently have a minimum of 20 vmguest to a maximum of 30 vmguest
allocated per blade within our VCL environment. With 48GB of memory per
blade, we thought this was a ‘no-brainer’. Well, it isn’t.
How many vmguest are most of you running per blade/computer within your
California State University, Northridge