| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Lane Van Ingen <lvaningen(at)esncc(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Log Messages |
| Date: | 2006-12-15 19:03:46 |
| Message-ID: | 1166209426.3243.203.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2006-12-15 at 12:50, Lane Van Ingen wrote:
> We are running on Windows 2003, version 8.0.4.
>
> Database is up and running, but we are noticing (usually, on a twice a week
> basis) the following error message:
>
> Could not receive data from client: No connection could be made because
> client machine actively refused it.
>
> Can anyone tell me what might be causing this?
More than likely either a port scanner or some program that checks
postgresql for life is simply hitting the port and then dropping the
connection when it sees the answer. For instance, if I telnet to my
pgsql server / port, I see this for a disconnect:
LOG: incomplete startup packet
and this for typing in gobbledly gook:
LOG: invalid length of startup packet
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2006-12-16 16:24:36 | Adding a column with default value possibly corrupting a functional index. |
| Previous Message | Lane Van Ingen | 2006-12-15 18:50:52 | PostgreSQL Log Messages |