Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

Output

[root(at)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/0 0.0.0.0/0 tcp dpt:5436

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 43575 packets, 6143K bytes)
pkts bytes target prot opt in out source destination
[root(at)vpdb1 ~]#

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of John R Pierce
Sent: Tuesday, December 27, 2011 2:17 PM
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

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 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.
>

is a linux firewall blocking incoming connections to 5436 ?

iptables -L -vn

to see the full set of firewall rules.

--
john r pierce N 37, W 122
santa cruz ca mid-left coast