Thread: BUG #6055: connection refused

The following bug has been logged online:

Bug reference:      6055
Logged by:          Sav
Email address:      halsa01@ca.com
PostgreSQL version: 8.3.5
Operating system:   Solaris 10
Description:        connection refused
Details:

Hi

I have Solaris 10 machine. I get error Connection refused error. The
complete error is "Connection refused. Check that the hostname and port are
correct and that the
postmaster is accepting TCP/IP connections."

And when we check the postgres log we see the below trace.

EDTFATAL:  57P01: terminating connection due to administrator command.

Could you please let me know the reason of this connection refused. Are
there any patches available?


Thanks
Savita

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@ca.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/