thanks
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Tuesday, December 27, 2011 2:48 PM
To: Jacques Lamothe
Cc: r...@iol.ie; pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
On 12/27/2011 11:44 AM
Correct, I'll take off
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Tuesday, December 27, 2011 2:46 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO
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 nee
On 12/27/11 11:34 AM, Jacques Lamothe wrote:
Output
[root@vpdb1 ~]# iptables -L -vn
Chain INPUT (policy ACCEPT 44094 packets, 6327K bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT tcp -- * * 0.0.0.0/00.0.0.0
pt in out source destination
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Tuesday, December 27, 2011 2:42 PM
To: Jacques Lamothe
Cc: r...@iol.ie; pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port
On 12/27/2011 11:39 AM, Jacques Lamothe wrote:
Yes I did
More guesses.
Looks like you may be running on Amazon AWS?
If so, did you change the AWS firewall to allow port 5436?
--
Adrian Klaver
adrian.kla...@gmail.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
T
Yes I did
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@gmail.com]
Sent: Tuesday, December 27, 2011 2:39 PM
To: Jacques Lamothe
Cc: r...@iol.ie; pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
On 12/27/2011 11:31 AM
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 set
: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of John R Pierce
Sent: Tuesday, December 27, 2011 2:17 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
On 12/27/11 11:07 AM, Jacques Lamothe wrote
2:21 PM
To: Jacques Lamothe
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
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 databa
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 connection
On 12/27/2011 11:07 AM, 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 canno
On 12/27/11 11:07 AM, 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 can
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 t
14 matches
Mail list logo
