From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: postgres port 5434 not being allowed when remote server is accessing
Date: Wed, 1 Aug 2018 13:00:24 -0500
Message-ID: <d96fa7a1-0eca-48ab-8710-14341fa24763@gmail.com> (raw)
In-Reply-To: <CADyzmyz=e-KNvkCPN7urZ=YZ13oiqnZh8+Ph7MhbmRHHdNk5=Q@mail.gmail.com>
References: <CADyzmyxOoT98kDM6r3UamW1RFCs4CF9i9AawjYPmNmaA+Hzrdg@mail.gmail.com>
<CA+k1dMbJ4bRuXqOLTdAK41zRegUxTbDo3oR6jqv=SaYxLb_aqA@mail.gmail.com>
<CADyzmyyDzkhO-3vyFc17=+ii2MirJcyWg-t74nEeUyg3ioqHTA@mail.gmail.com>
<CA+t6e1kPzqorF=84TWjdvcg90wvSn3qcDQg8DYJk08mCRXATVg@mail.gmail.com>
<CADyzmyz=e-KNvkCPN7urZ=YZ13oiqnZh8+Ph7MhbmRHHdNk5=Q@mail.gmail.com>
nmap to the rescue!!!
It's a go-to tool in cases like this.
On 08/01/2018 12:17 PM, Mark Steben wrote:
> No error - the connection attempt just spins until the attempt times out.
> I now suspect a firewall issue and have reached out to our IT team to
> investigate.
>
> Thank you,
>
> On Wed, Aug 1, 2018 at 1:10 PM, Mariel Cherkassky
> <mariel.cherkassky@gmail.com <mailto:mariel.cherkassky@gmail.com>> wrote:
>
> Hi, what error do you get?
>
>
> On Wed, Aug 1, 2018, 8:05 PM Mark Steben
> <mark.steben@drivedominion.com <mailto:mark.steben@drivedominion.com>>
> wrote:
>
> Hi Arlindo - yes hot_standby is turned on for that server. Thanks
> for quick response.
>
> On Wed, Aug 1, 2018 at 12:26 PM, Arlindo Neto <neto.acs@gmail.com
> <mailto:neto.acs@gmail.com>> wrote:
>
> Hello Mark,
>
> Have you checked the hot_standby parameter? It must be ON so
> you can run queries on a standby.
>
> Regards,
> Arlindo Neto.
>
> Em qua, 1 de ago de 2018 às 13:22, Mark Steben
> <mark.steben@drivedominion.com
> <mailto:mark.steben@drivedominion.com>> escreveu:
>
> 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?
>
>
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: postgres port 5434 not being allowed when remote server is accessing
In-Reply-To: <d96fa7a1-0eca-48ab-8710-14341fa24763@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox