Re: Server Crash - Mailing list pgsql-admin

From Hajek, Nick
Subject Re: Server Crash
Date
Msg-id AFD16ED07E37C64D963DA24840AA31F2035248C5@EVSCO01.na.vishayint.com
Whole thread Raw
In response to Re: Server Crash  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Responses Re: Server Crash
List pgsql-admin

> -----Original Message-----
> From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
> Sent: Tuesday, April 22, 2008 10:13 AM
> To: Hajek, Nick
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Server Crash
>
> 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.
>

Bingo.  I checked the syslog and found the OOM killer and indications
that the free swap space was zero.  Now I just need to find what's
eating memory.  Thanks for the help.

pgsql-admin by date:

Previous
From: "Peter Koczan"
Date:
Subject: Re: PG 8.3 and kerberos failures
Next
From: Tom Lane
Date:
Subject: Re: Server Crash