From: | Bert <biertie(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: slave restarts with kill -9 coming from somewhere, or nowhere |
Date: | 2013-04-03 06:45:43 |
Message-ID: | CAFCtE1me=Jir4gjvYG4nYMfgFEFRi6vVqLT=4R6LbpzOw1K-7A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Tom,
thanks for the tip! it was indeed the oom killer.
Is it wise to disable the oom killer? Or will the server really go down
withough postgres doing something about it?
currently I already lowered the shared_memory value a bit..
cheers,
Bert
On Tue, Apr 2, 2013 at 8:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bert <biertie(at)gmail(dot)com> writes:
> > I'm running the latest postgres version (9.2.3), and today for the first
> > time I encountered this:
>
> > 12774 2013-04-02 18:13:10 CEST LOG: server process (PID 28463) was
> > terminated by signal 9: Killed
>
> AFAIK there are only two possible sources of signal 9: a manual kill,
> or the Linux kernel's OOM killer. If it's the latter there should be
> a concurrent entry in the kernel logfiles about this. If you find one,
> suggest reading up on how to disable OOM kills, or at least reconfigure
> your system to make them less probable.
>
> regards, tom lane
>
--
Bert Desmet
0477/305361
From | Date | Subject | |
---|---|---|---|
Next Message | Bert | 2013-04-03 08:10:56 | Re: slave restarts with kill -9 coming from somewhere, or nowhere |
Previous Message | Tom Lane | 2013-04-02 18:06:08 | Re: slave restarts with kill -9 coming from somewhere, or nowhere |