Re: Server Crash

From: "Hajek, Nick" <Nick(dot)Hajek(at)Vishay(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Server Crash
Date: 2008-04-22 15:39:51
Message-ID: AFD16ED07E37C64D963DA24840AA31F2035248C5@EVSCO01.na.vishayint.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2008-04-22 16:06:58 Re: Server Crash
Previous Message Peter Koczan 2008-04-22 15:20:56 Re: PG 8.3 and kerberos failures