[SAC] OOM killer on tracsvn

Markus Neteler neteler at osgeo.org
Tue Sep 6 04:44:58 PDT 2016


On Tue, Sep 6, 2016 at 10:25 AM, Sandro Santilli <strk at kbt.io> wrote:
>
> I've found the OOM Killer kicking in often on the TracSVN machine,
> and mostly killing Apache:
>
> Sep  1 06:52:56 git kernel: [17261983.933073] Out of memory: Kill process 29329 (apache2) score 254 or sacrifice child
...
> Would it make more sense to disable the OOM killer so to actually
> *refuse* to allocate non-available memory rather than pretending
> memory is infinite and then killing arbitrary processes ?
>
> If not else, it might give processes a chance to do something upon
> ending out of memory (like I guess Apache could spawn less child?).

On a machine short of memory I usually run some cronjob which restarts
the apache server just before the OOM killer starts...
In this case it is likely a bad approach.

In the first place we should optimize the Apache settings and DB(s) to
have a smaller memory footprint.

Markus


More information about the Sac mailing list