Обсуждение: postgres port 5434 not being allowed when remote server is accessing

Поиск
Список
Период
Сортировка

postgres port 5434 not being allowed when remote server is accessing

От
Mark Steben
Дата:
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 | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com






Re: postgres port 5434 not being allowed when remote server is accessing

От
Arlindo Neto
Дата:
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> 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?

Thank you

--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com






Re: postgres port 5434 not being allowed when remote server is accessing

От
Mark Steben
Дата:
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> 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> 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?





--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com






Re: postgres port 5434 not being allowed when remote server is accessing

От
Mariel Cherkassky
Дата:
Hi, what error do you get?


On Wed, Aug 1, 2018, 8:05 PM Mark Steben <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> 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> 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?





--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com






Re: postgres port 5434 not being allowed when remote server is accessing

От
Mark Steben
Дата:
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> wrote:
Hi, what error do you get?


On Wed, Aug 1, 2018, 8:05 PM Mark Steben <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> 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> 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?





--




--
Mark Steben
 Database Administrator
@utoRevenue | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com






Re: postgres port 5434 not being allowed when remote server isaccessing

От
Ron
Дата:
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> wrote:
Hi, what error do you get?


On Wed, Aug 1, 2018, 8:05 PM Mark Steben <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> 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> 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.

Re: postgres port 5434 not being allowed when remote server isaccessing

От
Fabio Pardi
Дата:

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 | Autobase 
  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
www.twitter.com/DominionDealer
 www.drivedominion.com