Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

Поиск
Список
Период
Сортировка
От Raymond O'Donnell
Тема Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Дата
Msg-id 4EFA1AA1.5030909@iol.ie
обсуждение исходный текст
Ответ на UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Jacques Lamothe <JLamothe@allconnect.com>)
Ответы Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Список pgsql-general
On 27/12/2011 19:07, Jacques Lamothe wrote:
>
>
> Hi, I have 2 cluster databases, running on the same host, Linux with
> redHat. My fist database port is set to default, 5432, but my second
> database port is set to 5436 in the postgresql.conf file. While
> everything is ok with local connections, I cannot connect remotely using
> any of my tools to the second database with port 5436, including
> pgAdmin. Please help. Any parameter that I need to modify for the new
> database with port 5436? I have attached the posgresql.conf.

What error message are you getting when you try to connect?

Have you a suitable rule in pg_hba.conf to allow remote connections?

Any firewall blocking that port?

Ray.

--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie

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

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Detecting uncommitted changes