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 93F1AD1B444 for ; Thu, 1 Jan 2004 18:51:11 +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 36424-04 for ; Thu, 1 Jan 2004 14:50:22 -0400 (AST) Received: from quality.qadas.com (quality.qadas.com [204.227.16.4]) by svr1.postgresql.org (Postfix) with ESMTP id F3C1AD1B43A for ; Thu, 1 Jan 2004 14:50:20 -0400 (AST) Received: from quality.qadas.com (localhost [127.0.0.1]) by quality.qadas.com (8.12.10/8.12.10) with ESMTP id i01IoLJM007377; Thu, 1 Jan 2004 11:50:21 -0700 (MST) Received: (from mfuhr@localhost) by quality.qadas.com (8.12.10/8.12.10/Submit) id i01IoLdT007376; Thu, 1 Jan 2004 11:50:21 -0700 (MST) Date: Thu, 1 Jan 2004 11:50:21 -0700 From: Michael Fuhr To: Tom Lane Cc: Denis Grannell , pgsql-admin@postgresql.org Subject: Re: could not bind socket for statistics collector: Message-ID: <20040101115021.A4510@quality.qadas.com> References: <20040101110638.A25482@quality.qadas.com> <22021.1072981636@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22021.1072981636@sss.pgh.pa.us>; from tgl@sss.pgh.pa.us on Thu, Jan 01, 2004 at 01:27:16PM -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/4 X-Sequence-Number: 11867 On Thu, Jan 01, 2004 at 01:27:16PM -0500, Tom Lane wrote: > > On Thu, Jan 01, 2004 at 04:58:39PM +0100, Denis Grannell wrote: > >> I have just upgraded to 7.4.1 and since restarting > >> postmaster I am getting the following error message > >> in the logfile: > >> "could not bind socket for statistics collector: > >> "Cannot assign requested address". > > 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. However, I just backed out the "fix" I mentioned in my previous post (the fix being to comment out "::1 localhost" from /etc/inet/ipnodes), and although the "could not bind socket" message is now logged, the statistics collector nevertheless appears to be running. Must be a memory fault on my part, unless that behavior changed recently. > 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. -- Michael Fuhr http://www.fuhr.org/~mfuhr/