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 A464248CE14E60408AC030D3CD1790BA02721A@ACMAILNODE01.allconnect.com
Whole thread Raw
In response to Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
thanks

-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@gmail.com]
Sent: Tuesday, December 27, 2011 2:48 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:44 AM, Jacques Lamothe wrote:
> Yes I'm running on amazon.aws and yes I requested my admin to open the port, do you know how I can check its status

The AWS firewall is for an account so it lives outside the instances.
The way I check is using the AWS Management Console. You need account
access for that though, so you may have to talk with the admin.

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Jacques Lamothe
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Next
From: Tomas Vondra
Date:
Subject: Re: invalid memory alloc request size