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 01C7F11F6ABE for ; Tue, 4 Apr 2006 17:12:14 -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 50020-04 for ; Tue, 4 Apr 2006 17:12:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from twmail.ESNCC.COM (static-66-173-159-28.t1.cavtel.net [66.173.159.28]) by postgresql.org (Postfix) with SMTP id 2F94811F61FB for ; Tue, 4 Apr 2006 16:43:03 -0300 (ADT) Received: from spawar2i8uvlb9 ([150.125.117.63]) by twmail.ESNCC.COM with Microsoft SMTPSVC(6.0.3790.1830); Tue, 4 Apr 2006 15:43:01 -0400 From: "Lane Van Ingen" To: "Tom Lane" , "Kevin Grittner" Cc: "Jerry Sievers" , , "Peter Brant" Subject: Re: pg_stat_activity showing non-existent processes Date: Tue, 4 Apr 2006 15:39:35 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <13170.1144128543@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: Normal X-OriginalArrivalTime: 04 Apr 2006 19:43:01.0199 (UTC) FILETIME=[FB6B6DF0:01C6581F] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.139 required=5 tests=[AWL=0.139] X-Spam-Score: 0.139 X-Spam-Level: X-Archive-Number: 200604/47 X-Sequence-Number: 21216 Perhaps I might be able to help you track this problem down, but I could use some help. The limited amount of discussion on this I Googled up didn't help. We have never seen these messages before; we are assuming that their appearance now (we have been running OK since last August) is related to two recent changes we made to our Windows 2003 Server (SvcPk 1), PostgreSQL 8.0.4 installation: (1) started capturing statistics with the following config parms; all other parms were installation defaults: debug_pretty_print "on" log_min_duration_statement "60" log_min_error_statement "debug1" log_statement "ddl" log_truncate_on_rotation "on" stats_block_level "on" stats_command_string "on" stats_reset_on_server_start "on" stats_row_level "on" stats_start_collector "on" (2) added additional application workload to this server 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. 2006-04-04 04:16:58 FATAL: could not read from statistics collector pipe: No error 2006-04-04 04:16:58 FATAL: could not write to statistics collector pipe: No connection could be made because the target machine actively refused it. 2006-04-04 05:47:26 FATAL: could not read from statistics collector pipe: No error 2006-04-04 05:47:27 LOG: statistics collector process (PID 1776) was terminated by signal 1 -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Tom Lane Sent: Tuesday, April 04, 2006 1:29 AM To: Kevin Grittner Cc: Jerry Sievers; pgsql-admin@postgresql.org; Peter Brant Subject: Re: [ADMIN] pg_stat_activity showing non-existent processes "Kevin Grittner" writes: > It is probably related to something we've been seeing in the PostgreSQL > logs on the Windows servers: > [2006-04-03 08:28:25.990 ] 2072 FATAL: could not read from statistics > collector pipe: No error > [2006-04-03 08:28:26.068 ] 2012 LOG: statistics collector process (PID > 3268) was terminated by signal 1 We've heard reports of instability in the stats collector on Windows before, though I'm not sure if this is exactly the symptom --- check the list archives. Nobody's been able to track it down yet. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend