Обсуждение: postgres port 5434 not being allowed when remote server is accessing
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
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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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-9567www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com
Hello Mark,Have you checked the hot_standby parameter? It must be ON so you can run queries on a standby.Regards,Arlindo Neto.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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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-9567www.fb.com/
DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com
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
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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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-9567www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com--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-9567www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com
Hi, what error do you get?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.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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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-9567www.fb.com/
DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com--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-9567www.fb.com/
DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com
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
It's a go-to tool in cases like this.
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?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.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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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.
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
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 54322. standby instance 1 - port 54333. standby instance 2 - port 5434We 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-9567www.fb.com/DominionDealerSolutions
www.twitter.com/DominionDealer
www.drivedominion.com