Re: Stats Collector Error 7.4beta1 and 7.4beta2 - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Stats Collector Error 7.4beta1 and 7.4beta2
Date
Msg-id Pine.LNX.4.21.0309041830390.24521-100000@linuxworld.com.au
Whole thread Raw
In response to Re: Stats Collector Error 7.4beta1 and 7.4beta2  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Thu, 4 Sep 2003, Bruce Momjian wrote:

> Tom Lane wrote:
> > "Matthew T. O'Connor" <matthew@zeut.net> writes:
> > > ... Initially I saw an error in the logs about an IPv6 address
> > > error but after I recompiled everthing with a simple ./configure
> > > --prefix=/home/user/somethingelse/ I didn't get the IPv6 error in the
> > > logs anymore.
> > 
> > Hm.  Could it be an IPv6 issue --- that is, the stats collector is alive
> > and faithfully listening on some UDP port, but it's not the same port
> > the backends try to send to?  Given the discussion over the past couple
> > of days about bizarre interpretations of loopback addresses in
> > pg_hba.conf, I could sure believe there's some similar kind of issue for
> > the stats collector.
> 
> Doesn't the stats collector use unix domain sockets, not IP?

Nup.
   for (addr = addrs; addr; addr = addr->ai_next)   {
#ifdef HAVE_UNIX_SOCKETS       /* Ignore AF_UNIX sockets, if any are returned. */       if (addr->ai_family == AF_UNIX)
         continue;
 
#endif       if ((pgStatSock = socket(addr->ai_family, SOCK_DGRAM, 0)) >= 0)           break;   }

I thing I haven't seen asked: is there a packet filter blocking
local<->local UDP traffic by any chance?

Thanks,

Gavin



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Win32 native port
Next
From: "Jeroen T. Vermeulen"
Date:
Subject: Re: Transaction status in default psql prompt?