<div dir="ltr">I have also faced similar issues when running pcp_recovery_node on the master in the below two cases:<div><br></div><div>1. Consider the status below now :</div><br> Postgres Pgpool Status<br> node 1 - standby master up<br> node 2 - primary standby up<br> node 3 - standby standby up<br> <br> Now stop pgpool on node-1, the status becomes as below:<div><br></div><div>Status :<br> Postgres Pgpool Status<br> node 1 - standby standby down<br> node 2 - primary standby up<br> node 3 - standby master up<br><div><br></div><div>Start pgpool on node-1 and run the pcp_recovery_node</div></div><div><br></div><div>Now manually run pcp_recovery for node -0 on node-0<br> # /usr/local/bin/pcp_recovery_node -h 10.198.34.194 -p 9898 -U pgpool -n 0<br>Password:<br>ERROR: node recovery failed, unable to connect to master node: 1<br></div><div><br></div><div><br></div><div>2. Sometimes when master (pgpool n postgres) goes down and a new master is elected.</div><div>When the old master comes back, running pcp_recover_node on the new master for the node 0 (old master ) gives the below error:</div><div><br></div><div>Now manually run pcp_recovery for node -0 on node-0<br> # /usr/local/bin/pcp_recovery_node -h 10.198.34.194 -p 9898 -U pgpool -n 0<br>Password:<br>ERROR: node recovery failed, unable to connect to master node: 1 <br></div><div><br></div><div>Please let us know how to come out of this scenario / make it work</div><div><br></div><div>Thanks And Regards,</div><div><br></div><div> Lakshmi Y M</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 20, 2019 at 12:40 PM <<a href="mailto:pgpool-general-request@pgpool.net">pgpool-general-request@pgpool.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send pgpool-general mailing list submissions to<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://www.sraoss.jp/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.sraoss.jp/mailman/listinfo/pgpool-general</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pgpool-general-request@pgpool.net" target="_blank">pgpool-general-request@pgpool.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pgpool-general-owner@pgpool.net" target="_blank">pgpool-general-owner@pgpool.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of pgpool-general digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. [pgpool-general: 6562] Old master recovery after failover<br>
error "unable to connect to master node" (Lionel Engel)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 20 May 2019 08:55:15 +0200<br>
From: Lionel Engel <<a href="mailto:lionel.engel6@gmail.com" target="_blank">lionel.engel6@gmail.com</a>><br>
To: <a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
Subject: [pgpool-general: 6562] Old master recovery after failover<br>
error "unable to connect to master node"<br>
Message-ID:<br>
<<a href="mailto:CAAPz40A4Hed0Fa1KUaNC2U3OuzD%2BL5dKia1tiDYCwMWADtEs_w@mail.gmail.com" target="_blank">CAAPz40A4Hed0Fa1KUaNC2U3OuzD+L5dKia1tiDYCwMWADtEs_w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hello,<br>
<br>
I have an issue when trying to recover my old master after a failover<br>
occured.<br>
<br>
Automatic recovery failed, so I tried to run *pcp_recovery_node *but an<br>
error return saying "node recovery failed, unable to connect to master<br>
node: 1". Can you please advise me?<br>
<br>
In attachment, you can find my recovery_1st_stage script and my pgpool.conf.<br>
<br>
Thanks in advance. Best regards,<br>
<br>
Lionel Engel<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.html" rel="noreferrer" target="_blank">http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: recovery_1st_stage.sh<br>
Type: application/octet-stream<br>
Size: 1600 bytes<br>
Desc: not available<br>
URL: <<a href="http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.obj" rel="noreferrer" target="_blank">http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.obj</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: pgpool.conf<br>
Type: application/octet-stream<br>
Size: 40804 bytes<br>
Desc: not available<br>
URL: <<a href="http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment-0001.obj" rel="noreferrer" target="_blank">http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment-0001.obj</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
<br>
<br>
End of pgpool-general Digest, Vol 91, Issue 19<br>
**********************************************<br>
</blockquote></div>