[pgpool-general: 6565] Re: pgpool-general Digest, Vol 91, Issue 19

[Lakshmi Raghavendra]

I have also faced similar issues when running pcp_recovery_node on the
master in the below two cases:

1. Consider the status below now :

                Postgres   Pgpool  Status
node 1 - standby   master    up
node 2 - primary   standby   up
node 3 - standby   standby   up

Now stop pgpool on node-1, the status becomes as below:

Status :
               Postgres   Pgpool  Status
node 1 - standby   standby    down
node 2 - primary   standby  up
node 3 - standby   master   up

Start pgpool on node-1 and run the pcp_recovery_node

Now manually run pcp_recovery for node -0 on node-0
 # /usr/local/bin/pcp_recovery_node -h 10.198.34.194 -p 9898 -U pgpool -n 0
Password:
ERROR:  node recovery failed, unable to connect to master node: 1


2. Sometimes when master (pgpool n postgres) goes down and a new master is
elected.
When the old master comes back, running pcp_recover_node on the new master
for the node 0 (old master ) gives the below error:

Now manually run pcp_recovery for node -0 on node-0
 # /usr/local/bin/pcp_recovery_node -h 10.198.34.194 -p 9898 -U pgpool -n 0
Password:
ERROR:  node recovery failed, unable to connect to master node: 1

Please let us know how to come out of this scenario / make it work

Thanks And Regards,

    Lakshmi Y M

On Mon, May 20, 2019 at 12:40 PM <pgpool-general-request at pgpool.net> wrote:

> Send pgpool-general mailing list submissions to
>         pgpool-general at pgpool.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://www.sraoss.jp/mailman/listinfo/pgpool-general
> or, via email, send a message with subject or body 'help' to
>         pgpool-general-request at pgpool.net
>
> You can reach the person managing the list at
>         pgpool-general-owner at pgpool.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pgpool-general digest..."
>
>
> Today's Topics:
>
>    1. [pgpool-general: 6562] Old master recovery after failover
>       error     "unable to connect to master node" (Lionel Engel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 20 May 2019 08:55:15 +0200
> From: Lionel Engel <lionel.engel6 at gmail.com>
> To: pgpool-general at pgpool.net
> Subject: [pgpool-general: 6562] Old master recovery after failover
>         error   "unable to connect to master node"
> Message-ID:
>         <
> CAAPz40A4Hed0Fa1KUaNC2U3OuzD+L5dKia1tiDYCwMWADtEs_w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello,
>
> I have an issue when trying to recover my old master after a failover
> occured.
>
> Automatic recovery failed, so I tried to run *pcp_recovery_node *but an
> error return saying "node recovery failed, unable to connect to master
> node: 1". Can you please advise me?
>
> In attachment, you can find my recovery_1st_stage script and my
> pgpool.conf.
>
> Thanks in advance. Best regards,
>
> Lionel Engel
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.html
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: recovery_1st_stage.sh
> Type: application/octet-stream
> Size: 1600 bytes
> Desc: not available
> URL: <
> http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment.obj
> >
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: pgpool.conf
> Type: application/octet-stream
> Size: 40804 bytes
> Desc: not available
> URL: <
> http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190520/b3560099/attachment-0001.obj
> >
>
> ------------------------------
>
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
>
>
> End of pgpool-general Digest, Vol 91, Issue 19
> **********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20190522/c0b9cd9d/attachment.htm>