X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B1892D1B436 for ; Thu, 1 Jan 2004 19:10:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 36325-10 for ; Thu, 1 Jan 2004 15:10:05 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 669D4D1B43D for ; Thu, 1 Jan 2004 15:10:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i01JA019028677; Thu, 1 Jan 2004 14:10:00 -0500 (EST) To: Michael Fuhr Cc: Denis Grannell , pgsql-admin@postgresql.org Subject: Re: could not bind socket for statistics collector: In-reply-to: <20040101115021.A4510@quality.qadas.com> References: <20040101110638.A25482@quality.qadas.com> <22021.1072981636@sss.pgh.pa.us> <20040101115021.A4510@quality.qadas.com> Comments: In-reply-to Michael Fuhr message dated "Thu, 01 Jan 2004 11:50:21 -0700" Date: Thu, 01 Jan 2004 14:10:00 -0500 Message-ID: <28675.1072984200@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/5 X-Sequence-Number: 11868 Michael Fuhr writes: > On Thu, Jan 01, 2004 at 01:27:16PM -0500, Tom Lane wrote: >> Is it actually an ERROR, or just a LOG? If the latter, ignore it. >> There's no problem unless you also see >> "LOG: disabling statistics collector for lack of working socket" > Dang...I'm not the original poster, but I thought I remembered the > statistics collector not starting when I saw the "could not bind > socket" message. We did have a problem of that sort in 7.4 beta releases --- pgstats would give up instead of continuing to try additional results from getaddrinfo(). I don't recall at the moment if the fix was in 7.4.0 or not, but it's definitely there in 7.4.1. >> Making the message disappear would require getting your kernel and >> libc on the same page about whether IPv6 is supported or not. I don't >> know enough about Solaris to know how/where to fix that. > That's what commenting out "::1 localhost" from /etc/inet/ipnodes appears > to do. Oh, okay, I misread what you were trying to do. Yeah, that sounds like a plausible fix. regards, tom lane