Skip site navigation (1) Skip section navigation (2)

Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date: 2011-12-27 19:16:59
Message-ID: 4EFA19AB.7000905@hogranch.com (view raw or flat)
Thread:
Lists: pgsql-general
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


In response to

Responses

pgsql-general by date

Next:From: Adrian KlaverDate: 2011-12-27 19:17:10
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Previous:From: Jacques LamotheDate: 2011-12-27 19:07:35
Subject: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group