From: Scott Marlowe <scott.marlowe@gmail.com>
To: Hajek, Nick <Nick.Hajek@vishay.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Server Crash
Date: Tue, 22 Apr 2008 09:13:09 -0600
Message-ID: <dcc563d10804220813m21facfbfx17ab52a0e1de2743@mail.gmail.com> (raw)
In-Reply-To: <AFD16ED07E37C64D963DA24840AA31F203524511@EVSCO01.na.vishayint.com>
References: <AFD16ED07E37C64D963DA24840AA31F203524511@EVSCO01.na.vishayint.com>
On Tue, Apr 22, 2008 at 8:14 AM, Hajek, Nick <Nick.Hajek@vishay.com> wrote:
>
>
> All,
> We experienced a crash of a Postgresql server which from the log appears to
> have began with this entry:
>
> Log: background writer process (PID 3457) was terminated by signal 9
Kill -9 is the "shoot it in the head" signal. It is not generated by
postgresql in normal operation. It can be generated by "pg_ctl -m
immediate stop" . At least I think that's what signal it sends.
Anyway, the most common cause of kill -9s randomly showing up in linux
is the OOM killer.
It's quite possible you're running your machine out of memory / swap
somehow and linux is killing the biggest, fattest process it can find,
which is pgsql.
you might wanna run vmstat 1 to see what's happening during these times.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, Nick.Hajek@vishay.com
Subject: Re: Server Crash
In-Reply-To: <dcc563d10804220813m21facfbfx17ab52a0e1de2743@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox