From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Senthil Kumar G <senthil@zoniac.com>
Cc: sivakumar krishnamurthy <sivakumar.mailinglist@gmail.com>
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Unable to start Statistics Collector
Date: Wed, 23 Jun 2010 14:34:14 -0400
Message-ID: <25795.1277318054@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, senthil@zoniac.com, sivakumar.mailinglist@gmail.com, kevin.grittner@wicourts.gov
Subject: Re: Unable to start Statistics Collector
In-Reply-To: <25795.1277318054@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox