Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL - Mailing list pgsql-general

From Jacques Lamothe
Subject Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date
Msg-id A464248CE14E60408AC030D3CD1790BA0271B5@ACMAILNODE01.allconnect.com
Whole thread Raw
In response to Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
List pgsql-general
Yes I did

-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@gmail.com]
Sent: Tuesday, December 27, 2011 2:39 PM
To: Jacques Lamothe
Cc: rod@iol.ie; pgsql-general@postgresql.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
acceptingTCP/IP connection. 

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

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Next
From: Adrian Klaver
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL