Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

From: Jacques Lamothe <JLamothe(at)allconnect(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: "rod(at)iol(dot)ie" <rod(at)iol(dot)ie>, "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:39:11
Message-ID: A464248CE14E60408AC030D3CD1790BA0271B5@ACMAILNODE01.allconnect.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yes I did

-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)gmail(dot)com]
Sent: Tuesday, December 27, 2011 2:39 PM
To: Jacques Lamothe
Cc: rod(at)iol(dot)ie; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

On 12/27/2011 11:31 AM, Jacques Lamothe wrote:
> 1) Error:
> Error connecting to data database. Connection refused. C heck that hostname and port are correct and postmaster is accepting TCP/IP connection.

So did you restart the server listening on port 5436 after changing the
listen_addresses setting?

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-12-27 19:41:34 Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Previous Message Adrian Klaver 2011-12-27 19:38:43 Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL