[pgpool-general: 8469] Re: Issue in pgpool cluster configuration in AWS enviroment

[Bo Peng]

Hello,

> I have completed the setup till starting of primary postgres and all pgpool nodes. 
> But when I am trying to start standby postgres nodes using recovery command mentioned in section "8.2.9.1. 
> Set up PostgreSQL standby server", the command execution is getting stuck and not processing.

Did you specify the Elastic IP to "-h" option in pcp_recovery_node command?

Because I couldn't find any logs of pcp processes,
I think pgpool can't be connected using Elastic IP.
Can you connect to Pgpool-II using Elastic IP?
  
  psql -h <Elastic IP> -p 9999 -U postgres

Please check your security group settings and 
make sure the traffics on 9898 and 9999 port are allowed.

On Tue, 25 Oct 2022 11:49:27 +0000
Banashree Biswas <banashree.biswas at tcs.com> wrote:

> TCS Confidential
> 
> Dear Team,
> 
> I am new to pgpool and trying to do an HA setup of postgresql DB using pgpool.
> 
> For this setup I have taken three RHEL 8 servers and one elastic IP. Version of postgres and pgpool is 12 and 4.2.1 respectively.
> 
> I have completed the setup till starting of primary postgres and all pgpool nodes. But when I am trying to start standby postgres nodes using recovery command mentioned in section "8.2.9.1. Set up PostgreSQL standby server", the command execution is getting stuck and not processing.
> 
> Command execution screenshot:
> [cid:72501fca-6a7f-4b51-96ac-c077ac6206a6]
> 
> Log getting printed in postgres log:
> Password:
> Password:
> Password:
> Password:
> Password:
> Password:
> 
> Log getting printed in pgpool log:
> 2022-10-25 11:42:01: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:42:11: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:42:22: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:42:32: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:42:42: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:42:52: pid 5677: LOG:  new IPC connection received
> 2022-10-25 11:43:02: pid 5677: LOG:  new IPC connection received
> 
> Please suggest how to proceed with this setup.
> 
> I have followed below links for this configuration:
> https://www.pgpool.net/docs/42/en/html/example-aws.html
> AWS Configuration Example<https://www.pgpool.net/docs/42/en/html/example-aws.html>
> 8.3.4. Try it out. Start Pgpool-II on each server with "-n" switch and redirect log messages to the pgpool.log file. The log message of leader/active Pgpool-II node will show the message of Elastic IP assignment.. LOG: I am the cluster leader node. Starting escalation process LOG: escalation process started with PID:23543 LOG: watchdog: escalation started Assigning Elastic IP 35.163.178.3 to ...
> www.pgpool.net
> 
> 
> 
> https://www.pgpool.net/docs/42/en/html/example-cluster.html
> Pgpool-II + Watchdog Setup Example<https://www.pgpool.net/docs/42/en/html/example-cluster.html>
> 8.2. Pgpool-II + Watchdog Setup Example. This section shows an example of streaming replication configuration using Pgpool-II.In this example, we use 3 Pgpool-II servers to manage PostgreSQL servers to create a robust cluster system and avoid the single point of failure or split brain. PostgreSQL 13 is used in this configuration example. All scripts have been tested with PostgreSQL 95 and later.
> www.pgpool.net
> 
> 
> 
> Thanks & Regards
> Banashree Biswas
> Tata Consultancy Services Limited
> Mail to: banashree.biswas at tcs.com
> 
> 
> TCS Confidential
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you
> 
> 


-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS LLC
https://www.sraoss.co.jp/