From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | pgsql-general list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Statistics collector failure messages on startup |
Date: | 2011-09-22 22:35:19 |
Message-ID: | 12104.1316730919@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Christophe Pettus <xof(at)thebuild(dot)com> writes:
> On PostgreSQL 9.0.1, on Ubuntu 10.04.2, I'm seeing these on startup:
> 2011-09-22 19:22:15.984 UTC,,,6066,,4e7b8ae7.17b2,1,,2011-09-22 19:22:15 UTC,,0,LOG,08006,"test message did not get through on socket for statistics collector",,,,,,,,,""
> 2011-09-22 19:22:15.984 UTC,,,6066,,4e7b8ae7.17b2,2,,2011-09-22 19:22:15 UTC,,0,LOG,00000,"trying another address for the statistics collector",,,,,,,,,""
> ... along with "WARNING: pgstat wait timeout" when I attempt to use
> any stats-collector-related info. I've confirmed that the loopback
> interface is unfiltered for UDP.
I'd say better check that again. The test that's whining was designed
specifically to detect cases where a packet filter prevents pg_stats
traffic from getting through. Frequently this is an IPv4 vs IPv6 kind
of problem...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Reuven M. Lerner | 2011-09-22 22:38:43 | Re: Speed of lo_unlink vs. DELETE on BYTEA |
Previous Message | Jeff Davis | 2011-09-22 22:33:53 | Re: Is 9.1 considered more stable/robust than 9.0.4 ? |