Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm seeing the following message in PostgreSQL server log:

LOG: could not receive data from client: No connection could be made because the target machine actively refused it.

There are (seemingly) no errors on the client side, so what is this message and is it safe to ignore it?

share|improve this question

closed as too localized by dezso, Max Vernon, Paul White, StanleyJohns, RolandoMySQLDBA Jun 19 '13 at 18:30

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Probably a libpq trying an SSL connection and failing back to regular protocol. It could also be a server-side firewall doing outbound filtering at fault though particularly if you're on Windows and have a 3rd party firewall installed (the built-in Microsoft one is fine). – Craig Ringer Feb 17 '13 at 12:22

Note you say this is in the server log and there are no known problems with clients. Consequently, I don't think that it is libpq per se. Additionally on doing some additional searches, it looks like this is a standard Windows "connection refused" message, which suggests that PostgreSQL is trying to connect to something and being refused.

If you are getting no error messages on the clients, I think this can be a relatively low priority to solve, but I would wonder about concerns regarding performance hits down the road (if you get a connection that times out and it causes clients to hang). Consequently I do think it is worth trying to resolve if only because it takes aim at a problem hiding in the shadows that could under the right circumstances cause some grief.

A few things to check before you go further might include:

What sort of authentication are you using? SSPI? Is it possible the KDC is not up when these errors occur? Are there any stored procedures (say, written in untrusted languages like pl/perlu) which make network connections to other hosts> Do these errors happen frequently or sporadically around certain times?

The key questions to be asked now are basically "what system is this connecting to and why?" From there you should be able to resolve the issue easily enough.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.