From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Sav <halsa01(at)ca(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6055: connection refused |
Date: | 2011-06-08 09:24:41 |
Message-ID: | 4DEF3FD9.60606@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 8/06/2011 2:47 PM, Sav wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6055
> Logged by: Sav
> Email address: halsa01(at)ca(dot)com
> PostgreSQL version: 8.3.5
You're running an ancient version of PostgreSQL. Upgrade to the latest
in the 8.3 series at minimum; you are missing lots of bug fixes. It's
entirely possible that one of them might already address your issue.
> EDTFATAL: 57P01: terminating connection due to administrator command.
It looks like this has come up on the mailing lists before.
http://archives.postgresql.org/pgsql-general/2010-09/msg00423.php
Please read that discussion thread, including replies, and see if it
helps. Note in particular:
Tom Lane wrote:
> This is a result of something sending SIGTERM to the backend process.
>
> I have heard reports of "load management" software that SIGTERM's
> processes more or less at random whenever it decides the system is
> overloaded. If you have any such junkware installed on your server,
> try disabling it.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-08 15:09:27 | Re: BUG #5926: information schema dtd_identifier for element_types, columns, parameters views inconsistent |
Previous Message | Sav | 2011-06-08 06:47:15 | BUG #6055: connection refused |