[FUG-BR] PostgreSql

[andre silva]

Ola!!!!
 
Gostaria de agradecer a todos pela atencao dada, muito obrigado pela ajuda dada, serviram pra resolver o problema. Valeu gente.
 
André Luiz

 

> Date: Thu, 13 Sep 2012 11:17:48 -0300
> From: marcelo at mginformatica.com
> To: freebsd at fug.com.br
> Subject: Re: [FUG-BR] PostgreSql
> 
> opcao listen_addresses
> 
> do postgresql.conf ???????????????
> 
> Em 2012-09-13 09:41, andre silva escreveu:
> > Bom dia!!!
> >
> > Estou com um problema de comunicao onde nao consigo ter acesso na
> > porta 5432do db. Alguem pode ajudar a resolver, pois ate o momento 
> > nao
> > seguir ter exito.
> >
> > Usando a ferramenta pgAdmin III aparece o seguinte erro de conexao:
> >
> > Server doesn't listen
> > The server doesn't accept connections: the connection library reports
> > could not connect to server: Connection refused (0x0000274D/10061) Is
> > the server running on host "192.168.0.70" and accepting TCP/IP
> > connections on port 5432?
> > If you encounter this message, please check if the server you're
> > trying to contact is actually running PostgreSQL on the given port.
> > Test if you have network connectivity from your client to the server
> > host using ping or equivalent tools. Is your network / VPN / SSH
> > tunnel / firewall configured correctly?
> > For security reasons, PostgreSQL does not listen on all available IP
> > addresses on the server machine initially. In order to access the
> > server over the network, you need to enable listening on the address
> > first.
> > For PostgreSQL servers starting with version 8.0, this is controlled
> > using the "listen_addresses" parameter in the postgresql.conf file.
> > Here, you can enter a list of IP addresses the server should listen
> > on, or simply use '*' to listen on all available IP addresses. For
> > earlier servers (Version 7.3 or 7.4), you'll need to set the
> > "tcpip_socket" parameter to 'true'.
> > You can use the postgresql.conf editor that is built into pgAdmin III
> > to edit the postgresql.conf configuration file. After changing this
> > file, you need to restart the server process to make the setting
> > effective.
> > If you double-checked your configuration but still get this error
> > message, it's still unlikely that you encounter a fatal PostgreSQL
> > misbehaviour. You probably have some low level network connectivity
> > problems (e.g. firewall configuration). Please check this thoroughly
> > before reporting a bug to the PostgreSQL community.
> >
> > Grato,
> >
> > André Luiz
> > -------------------------
> > Histórico: http://www.fug.com.br/historico/html/freebsd/
> > Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd
> -------------------------
> Histórico: http://www.fug.com.br/historico/html/freebsd/
> Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd