From: | Fabio Pardi <f(dot)pardi(at)portavita(dot)eu> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: postgres port 5434 not being allowed when remote server is accessing |
Date: | 2018-08-02 08:05:46 |
Message-ID: | 31e1a278-3aa8-5576-c8bf-b38e1f4a16ba@portavita.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
From your description looks like a firewall or maybe routing issue.
Could you post the output of tcpdump on both machines while you attempt to open the connections?
Regards,
fabio pardi
On 01/08/18 18:22, Mark Steben wrote:
> Good morning,
>
> We run postgres 9.4.8 on our GNU linux standby server. We run 3 instances receiving data there:
> 1. a slony instance - port 5432
> 2. standby instance 1 - port 5433
> 3. standby instance 2 - port 5434
>
> We run connection strings in another GNU linux server to access the data on our standby server.
>
> We can access the postgres instances on port 5432 and port 5433 but not port 5434.
>
> All the instances are up and running on the standby server. Any insights as to why 5434 does not work?
>
> Thank you
>
> --
> *Mark Steben*
> Database Administrator
> @utoRevenue <http://www.autorevenue.com/> | Autobase <http://www.autobase.net/>
> CRM division of Dominion Dealer Solutions
> 95D Ashley Ave.
> West Springfield, MA 01089
> t: 413.327-3045
> f: 413.383-9567
>
> www.fb.com/DominionDealerSolutions <http://www.fb.com/DominionDealerSolutions>
> www.twitter.com/DominionDealer <http://www.twitter.com/DominionDealer>
> www.drivedominion.com <http://www.autorevenue.com/>
>
>
>
>
>
>
> <https://www.drivedominion.com/transform-your-vision/>
From | Date | Subject | |
---|---|---|---|
Next Message | For@ll | 2018-08-02 09:54:16 | PostgreSQL 9.3 - reindex problem |
Previous Message | babak houman | 2018-08-02 07:50:43 | Optimal SSD based RAID 0 config |