| From: | Raymond O'Donnell <rod(at)iol(dot)ie> |
|---|---|
| To: | Jacques Lamothe <JLamothe(at)allconnect(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |
| Date: | 2011-12-27 19:21:05 |
| Message-ID: | 4EFA1AA1.5030909@iol.ie |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)iol(dot)ie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-12-27 19:22:54 | Re: Detecting uncommitted changes |
| Previous Message | Adrian Klaver | 2011-12-27 19:17:10 | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |