Re: listen_addresses = '*' ok, specific address(es) no

Tom,

I omitted the LOG and HINT lines before.

LOG: could not bind IPv4 socket: Can't assign requested address
HINT: Is another postmaster already running on port 5432? If not,
wait a few seconds and retry.
WARNING: could not create listen socket for "192.168.1.33"
FATAL: could not create any TCP/IP sockets

This works fine if I use '*' instead of '192.168.1.33'.

Andrew Sullivan wrote:
> Well, do you actually have an interface with that address?

I think I do, in that the machine's wireless interface is set up with
a 192.168.1.x/24 address and 1.33 is on the same subnet. Or maybe
I'm misunderstanding. I thought the purpose of listen_addresses was
to allowing incoming connections only from listed addresses.

Geoff

On Jun 15, 2006, at 10:40, Tom Lane wrote:

> Geoffrey Knauth <geoff(at)knauth(dot)org> writes:
>> I'm running PostgreSQL 8.1.3. In my postgresql.conf, the following
>> works:
>> listen_addresses = '*'
>
>> but the following does not:
>> listen_addresses = '192.168.1.33'
>
>> I get an error:
>> WARNING: could not create listen socket for "192.168.1.33"
>> FATAL: could not create any TCP/IP sockets
>
> There should be more info than that --- AFAICS all the failure
> paths in
> that code emit LOG messages. Perhaps you have log_min_messages set
> too
> high to allow the info to come out?