Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id AB43D9FA463 for ; Fri, 15 Dec 2006 15:03:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 05602-04 for ; Fri, 15 Dec 2006 15:03:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 784669FA456 for ; Fri, 15 Dec 2006 15:03:53 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Fri, 15 Dec 2006 19:03:46 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 15 Dec 2006 13:03:46 -0600 Subject: Re: PostgreSQL Log Messages From: Scott Marlowe To: Lane Van Ingen Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1166209426.3243.203.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 15 Dec 2006 13:03:46 -0600 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/233 X-Sequence-Number: 24025 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