BUG #13400: Unable to connect postgresql using remote machine

Поиск
Список
Период
Сортировка
От rajivmehta0201@gmail.com
Тема BUG #13400: Unable to connect postgresql using remote machine
Дата
Msg-id 20150605065448.9471.83085@wrigleys.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #13400: Unable to connect postgresql using remote machine  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-bugs
The following bug has been logged on the website:

Bug reference:      13400
Logged by:          Rajiv
Email address:      rajivmehta0201@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system:   Linux (Fedora 13)
Description:

Hi,

I have installed postgresql 8.2 in linux machine(Fedora 13).
Packages are:

postgresql-debuginfo-8.2.18-1PGDG.f13.i686
postgresql-odbcng-0.99.101-0.4.test1.fc13.i686
postgresql-docs-8.2.18-1PGDG.f13.i686
postgresql-test-8.2.18-1PGDG.f13.i686
postgresql-plperl-8.2.18-1PGDG.f13.i686
postgresql-odbc-08.04.0200-2.fc13.i686
postgresql-libs-8.2.18-1PGDG.f13.i686
postgresql-devel-8.2.18-1PGDG.f13.i686
postgresql-pltcl-8.2.18-1PGDG.f13.i686
postgresql-server-8.2.18-1PGDG.f13.i686
postgresql-contrib-8.2.18-1PGDG.f13.i686
postgresql-plpython-8.2.18-1PGDG.f13.i686
postgresql-8.2.18-1PGDG.f13.i686

I have configuration in postgresql.conf file  as under:

listen_addresses = '*'
port = 5432

and In pg_hba.conf file i have added the ip of local machine and one remote
machine as under:

#local machine IP and Port
host    all         all         172.16.1.55/32      trust
#remote machine IP and Port
host    all         all         172.16.3.85/32      trust
host    all         all         0.0.0.0/0          md5

now i am trying to connect postgresql from remote machine using pgadmin III
but getting following error:

--------------
Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection timed out (0x0000274C/10060) Is the
server running on host "172.16.1.55" 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.
-----------
I have checked there is no firewall configured.

When i tried connecting the machine using putty i was able to do and
connected to postgresql as well.

 psql -h 172.16.1.55 -p 5432 -U postgres

But unable to connect using pgadmin III in remote machine.

Kindly help me on this.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master
Следующее
От: heliotec2008@gmail.com
Дата:
Сообщение: BUG #13403: Erro na instalção