Comments on: How to fix the OOM killer crashes under Linux

By: Jerry Champlin

Jerry Champlin — Sat, 01 Oct 2011 20:04:52 +0000

you could put something like this in cron:
passenger-memory-stats | perl -ne ‘if (/(\d+)\s+\d+.\d\sMB\s+(\d+\.\d)\sMB\s+Rails:.*(app1|app2)/) { if ($2 > 180) { print “$1\t$2\t$3\n”; system(“kill $1″);}}’

By: Fran

Fran — Fri, 16 Sep 2011 08:46:44 +0000

Nice one Henrik – I was pulling my hair out over this f&*^^%”ing behaviour. Hopefully this will sort out my own issue (I’m a WordPress user too).

By: Henrik Skupin

Henrik Skupin — Thu, 11 Aug 2011 09:27:45 +0000

As I have said above it was a comment plugin. I don’t remember the name anymore. But whenever you have a high memory usage and Linux overcommits check the ps command for suspicious processes. But well, you could suffer from another issue. It’s hard to tell that way.

By: Robert Pogson

Robert Pogson — Wed, 10 Aug 2011 20:21:29 +0000

I am having a similar problem. What plugin was giving the problem?

By: Henrik Skupin

Henrik Skupin — Tue, 22 Feb 2011 15:07:34 +0000

Well, all the stuff above can be used to prevent a crash of a server. As it turned out the underlying issue here was a WordPress plugin for comments, which didn’t play well with php-cgi. There were a dozen of dead processes hanging around.

By: roger

roger — Mon, 21 Feb 2011 21:35:52 +0000

This might be able to help phusion passenger users too…oh wait maybe they can just setup a monitor to kill large ruby processes, too?

By: Being Linux admin - setting up virtual servers and Samba | ProDevTips - programming tutorials

Mon, 25 Oct 2010 17:05:21 +0000

[...] To fix OOM killer crashes, put the following in /etc/sysctl.conf (original article here): [...]