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 | A464248CE14E60408AC030D3CD1790BA027137@ACMAILNODE01.allconnect.com Whole thread Raw |
In response to | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL (Raymond O'Donnell <rod@iol.ie>) |
Responses |
Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
|
List | pgsql-general |
1) Error: Error connecting to data database. Connection refused. C heck that hostname and port are correct and postmaster is acceptingTCP/IP connection. 2) pg_hba.conf for both clusters are similar DB2 - Port 5436 -Amzndev01 # IPv4 local connections: host all all 0.0.0.10/10 trust host all all xxx.168.0.10/24 trust host all all xxx.47.37.38/24 trust hostnossl amzndev01 viper_logical_1 xx.0.0.0/8 trust hostnossl amzndev01 viperuser xx.0.0.0/8 trust hostnossl amzndev01 viper_tx xx.0.0.0/8 trust hostnossl amzndev01 viper_reference_1 xx.0.0.0/8 trust hostnossl amzndev01 viper_cache_1 xx.0.0.0/8 trust hostnossl all all xx.32.81.157/10 trust # IPv6 local connections: host all all ::1/18 trust DB1 - Port 5432 - amznvpat1 # IPv4 local connections: host all all 0.0.0.0/10 trust host all all xxx.168.0.0/24 trust host all all xxx.47.37.37/24 trust hostnossl amznvpat1 viper_logical_1 xx.0.0.0/8 trust hostnossl amznvpat1 viperuser xx.0.0.0/8 trust hostnossl amznvpat1 viper_tx xx.0.0.0/8 trust hostnossl amznvpat1 viper_reference_1 xx.0.0.0/8 trust hostnossl amznvpat1 viper_cache_1 xx.0.0.0/8 trust hostnossl all all xx.32.81.157/10 trust # IPv6 local connections: host all all ::1/128 trust 3) [root@vpdb1 ~]# iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination -----Original Message----- From: Raymond O'Donnell [mailto:rod@iol.ie] Sent: Tuesday, December 27, 2011 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 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. What error message are you getting when you try to connect? Have you a suitable rule in pg_hba.conf to allow remote connections? Any firewall blocking that port? Ray. -- Raymond O'Donnell :: Galway :: Ireland rod@iol.ie
pgsql-general by date: