Re: BUG #6520: BRT FATAL: COULD NOT CREATE ANY TCP/IP SOCKETS

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: andrre1402(at)msn(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6520: BRT FATAL: COULD NOT CREATE ANY TCP/IP SOCKETS
Date: 2012-03-12 16:02:45
Message-ID: CA+TgmoZ=aE+ScOkvhcHOCrJtVZn1Xv83+j9oe-KT+QiFaHoaSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Mar 5, 2012 at 11:44 AM, <andrre1402(at)msn(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      6520
> Logged by:          André Luis Kuhn
> Email address:      andrre1402(at)msn(dot)com
> PostgreSQL version: 8.3.3
> Operating system:   Windows XP
> Description:
>
> Após ter dado problema no S.O. de não inicializar, foi corrigido o mesmo,
> porem o B.D. postgres não mais inicializou dando um erro ao executar passos
> para recuperar o banco (pg_ctl.exe start -D C:/Banco/8.3/data) BRT FATAL:
> COULD NOT CREATE ANY TCP/IP SOCKETS.
> Gostaria de saber como posso resolver esse erro.

This is an English-language mailing list; you might want to try
pgbr-geral (although listas.postgresql.org.br seems to be down at the
moment?!).

I don't think it's a bug, either. Most likely, you've configured
PostgreSQL to use a socket that is already in use, or listen_addresses
is set improperly. It might help to see a few more lines of the log
output, rather than just the last one.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2012-03-12 16:17:04 Re: BUG #6512: Bug with prepared statement and timestamp + interval
Previous Message Robert Haas 2012-03-12 15:33:33 Re: BUG #6484: pgstat wait timeout