From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Michael Korotun <michael(at)softasap(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postmaster crash - another server process exited |
Date: | 2005-05-06 13:57:16 |
Message-ID: | 1115387836.3868.61.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2005-05-06 at 07:54, Michael Korotun wrote:
> Hi Guys,
>
>
>
> I am writing here again. Here is the scenario of my problem:
>
>
>
> I have Postgres 8.0.1 on Linux FC3 and everything goes fine, except
> that a one time per week approximately I am getting server crash with
> a message in log:
>
>
>
> ==========================
>
> LOG: server process (PID 5252) was terminated by signal 9
>
> LOG: terminating any other active server processes
>
> WARNING: terminating connection because of crash of another server
> process
>
> DETAIL: The postmaster has commanded this server process to roll back
> the current transaction and exit, because another server process
> exited abnormally and possibly corrupted shared memory.
>
> HINT: In a moment you should be able to reconnect to the database and
> repeat your command.
Some process other than postgres itself is likely sending this, and it
could well be the kernel OOM killer at work, depending on your memory
usage and pg configuration.
What does dmesg say, if anything?
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2005-05-06 14:14:36 | Re: Adventures in Quest for GUI RAD |
Previous Message | Richard Huxton | 2005-05-06 13:43:52 | Re: postmaster crash - another server process exited abnormally |