To: Alvaro Herrera <alvherre@commandprompt.com>
cc: Senthil Kumar G <senthil@zoniac.com>,
	sivakumar krishnamurthy <sivakumar.mailinglist@gmail.com>,
	Kevin Grittner <kevin.grittner@wicourts.gov>,
	pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Unable to start Statistics Collector 
In-reply-to: <1277313092-sup-4662@alvh.no-ip.org> 
References: <011401cb121c$269abb10$1201a8c0@senthilg>
	<4C20A8B7020000250003280C@gw.wicourts.gov>
	<00b401cb128f$e4f2c5d0$1201a8c0@senthilg>
	<AANLkTinSZFAb4qHsDIrR4VsrZfZ9ksJljtTijAxaVof0@mail.gmail.com>
	<017f01cb12cb$890cf560$1201a8c0@senthilg>
	<1277313092-sup-4662@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Wed, 23 Jun 2010 13:11:44 -0400"
Date: Wed, 23 Jun 2010 14:34:14 -0400
Message-ID: <25795.1277318054@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Senthil Kumar G's message of mié jun 23 07:59:26 -0400 2010:
>> I executed follows. I am able to ping.
>> ping 127.0.0.1

> So can you ping localhost?

I'm betting the problem is kernel-level filter rules that let through
ping packets but not the stats collector traffic.  The reason that the
stats collector goes to such length to test the connection is that stuff
like this isn't uncommon :-(.  You need to look at your firewall packet
filtering settings and back off the restrictions on localhost UDP
traffic.

			regards, tom lane