X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 38C929FA6B2 for ; Thu, 17 Aug 2006 21:58:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 99239-01 for ; Thu, 17 Aug 2006 21:58:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B6E1D9FB326 for ; Thu, 17 Aug 2006 21:58:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7I0w16M001235; Thu, 17 Aug 2006 20:58:02 -0400 (EDT) To: "Tomeh, Husam" cc: pgsql-admin@postgresql.org Subject: Re: LOG: could not receive data from client: Connection reset by peer In-reply-to: References: Comments: In-reply-to "Tomeh, Husam" message dated "Thu, 17 Aug 2006 15:42:45 -0700" Date: Thu, 17 Aug 2006 20:58:01 -0400 Message-ID: <1234.1155862681@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.177 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/211 X-Sequence-Number: 22754 "Tomeh, Husam" writes: > I'm getting the following errors on one of my pg server running postgres > 7.4.5 on RedHat AS R4. > LOG: could not receive data from client: Connection reset by peer > LOG: incomplete startup packet > What I found out is that there's a networking VIP monitoring port 5432 > every 15 sec and that's basically used for failover so that the > application will re-direct user requests to another server with > identical pg database in case of database or server failure. As long as you know what's causing it, it's safe to ignore --- it's not harming anything except wasting a process launch each time. If you hadn't known the cause then I'd be worried about whether some hostile is portscanning your network ... What you *should* be worrying about is that you are still running 7.4.5. That's two years old and there are a big pile of known bugs in it, some of which *will* eat your data. regards, tom lane