X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id DD8DC11F620F for ; Tue, 4 Apr 2006 16:51:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71352-08 for ; Tue, 4 Apr 2006 16:51:58 -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 C4C7D11F6265 for ; Tue, 4 Apr 2006 16:51:56 -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 k34Jpro4013816; Tue, 4 Apr 2006 15:51:53 -0400 (EDT) To: "Lane Van Ingen" cc: "Kevin Grittner" , "Jerry Sievers" , pgsql-admin@postgresql.org, "Peter Brant" Subject: Re: pg_stat_activity showing non-existent processes In-reply-to: References: Comments: In-reply-to "Lane Van Ingen" message dated "Tue, 04 Apr 2006 15:39:35 -0400" Date: Tue, 04 Apr 2006 15:51:53 -0400 Message-ID: <13815.1144180313@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.114 required=5 tests=[AWL=0.114] X-Spam-Score: 0.114 X-Spam-Level: X-Archive-Number: 200604/45 X-Sequence-Number: 21214 "Lane Van Ingen" writes: > Don't understand the 'target machine' message, either; in this case, we are > running the application and the database server on the same box. > 2006-04-04 03:12:05 FATAL: could not read from statistics collector pipe: > No error 2006-04-04 03:12:06 FATAL: could not write to statistics collector > pipe: No connection could be made because the target machine actively > refused it. I think that's Microsoftese for ECONNRESET, ie, the kernel bounced a packet for lack of any listening process to deliver it to. The real question is what's causing the collector to fail (the "could not read"). While it'd be easy to make it retry read attempts, the reason it considers that FATAL is that it really should never happen. I'd like to find out exactly what's happening before we try to fix it. As Kevin mentioned, adding some more debug printout would be helpful. regards, tom lane