Re: Stats Collector Won't Start

From: Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Stats Collector Won't Start
Date: 2006-10-18 20:05:42
Message-ID: 1161201942.4138.18.camel@dba5.int.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2006-10-18 at 15:59 -0400, Tom Lane wrote:
> Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> writes:
> > On Wed, 2006-10-18 at 14:31 -0400, Tom Lane wrote:
> >> Would you try strace'ing postmaster start to see what gets passed to the
> >> socket() and bind() calls just before this message comes out?
>
> > Here is the relative output from truss.
>
> > socket(2, 2, 0) = 7
> > bind(7, 0x00000001100E3BF0, 16) Err#13 EACCES
>
> Well, that's pretty odd --- I'd have expected to see something involving
> 127.0.0.1 (ie, 7F000001 in one byte order or another). Does your
> /etc/hosts file map "localhost" to something other than 127.0.0.1?

Nope, it maps localhost to 127.0.0.1

> Also, do regular connections to this postmaster work across TCP/IP?
> If getaddrinfo() is broken I'd expect there to be problems binding
> to the postmaster's listen socket too ...

Yes, TCP/IP connections work fine.

--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-10-18 20:17:24 Re: [GENERAL] query log corrupted-looking entries
Previous Message Jonathan Hedstrom 2006-10-18 20:02:08 Re: column refernce question