<html><head></head><body><div class="ydp5a0a2fe9yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>Hi</div><div><br></div><div>Same issue for me but I am not sure how to fix it. Andre can you tell exactly how you check ?</div><div><br></div><div>I cannot add a test using pcp_node_info to check that the status is up, because then follow_master is never doing something. Indeed, in my case, when the follow_master is executed the status of the target node is always down, so my script does the standby follow command and then a pcp_attach_node.</div><div><br></div><div>To solve the issue now I added a check that the command&nbsp;<span>select pg_is_in_recovery(); returns "t" on the node, if it returns "f" then I can assume it is a degenerated master and I don't execute the follow_master command.</span></div><div><br></div><div><br></div><div><br></div><div>So my use case is this<br></div><div><br></div><div>1. node 0 is primary, node 1 and node 2 are standby</div><div>2. node 0 is restarted, node 1 becomes primary and node 2 follows the new primary (thanks to folllow_master). In follow_master of node 2 I have to do pcp_attach_node after because the status of the node is down&nbsp;</div><div>3. in the meantime node 0 has rebooted, the db is started on node 0 but it is down in pgpool and its role is standby (it is a degenerated master)</div><div>4. node 1 is restarted, pgpool executes failover on node 2 and follow_master on node 0 =&gt; the follow_master on node 0 breaks everything because after that node 0 becomes a primary again</div><div>&nbsp;<br></div><div>Thanks and regards</div><div><br></div><div class="ydp5a0a2fe9signature">Pierre</div></div>
        <div><br></div><div><br></div>
        
        </div><div id="ydp2b963b2ayahoo_quoted_1927667633" class="ydp2b963b2ayahoo_quoted">
            <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
                
                <div>
                    On Monday, February 25, 2019, 5:35:11 PM GMT+1, Andre Piwoni &lt;apiwoni@webmd.net&gt; wrote:
                </div>
                <div><br></div>
                <div><br></div>
                <div><div id="ydp2b963b2ayiv5096222534"><div><div dir="ltr"><div dir="ltr">I have already put that check in place.<div><br clear="none"></div><div>Thank you for confirming.</div></div><br clear="none"><div class="ydp2b963b2ayiv5096222534gmail_quote"><div class="ydp2b963b2ayiv5096222534yqt4592847929" id="ydp2b963b2ayiv5096222534yqtfd08537"><div class="ydp2b963b2ayiv5096222534gmail_attr" dir="ltr">On Sat, Feb 23, 2019 at 11:56 PM Tatsuo Ishii &lt;<a shape="rect" href="mailto:ishii@sraoss.co.jp" rel="nofollow" target="_blank">ishii@sraoss.co.jp</a>&gt; wrote:<br clear="none"></div><blockquote class="ydp2b963b2ayiv5096222534gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">Sorry, I was wrong. A follow_master_command will be executed against<br clear="none">
the down node as well. So you need to check whether target PostgreSQL<br clear="none">
node is running in the follow_master_commdn. If it's not, you can skip<br clear="none">
the node.<br clear="none">
<br clear="none">
Best regards,<br clear="none">
--<br clear="none">
Tatsuo Ishii<br clear="none">
SRA OSS, Inc. Japan<br clear="none">
English: <a shape="rect" href="http://www.sraoss.co.jp/index_en.php" rel="nofollow" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br clear="none">
Japanese:<a shape="rect" href="http://www.sraoss.co.jp" rel="nofollow" target="_blank">http://www.sraoss.co.jp</a><br clear="none">
<br clear="none">
&gt; I have added pg_ctl status check to ensure no action is taken when node is<br clear="none">
&gt; down but I'll check 3.7.8 version.<br clear="none">
&gt; <br clear="none">
&gt; Here's the Pgpool log from the time node2 is shutdown to time node1(already<br clear="none">
&gt; dead old primary) received follow master command.<br clear="none">
&gt; Sorry for double date logging. I'm also including self-explanatory<br clear="none">
&gt; failover.log that I my failover and follow_master scripts generated.<br clear="none">
&gt; <br clear="none">
&gt; Arguments passed to scripts for your reference.<br clear="none">
&gt; failover.sh %d %h %p %D %M %P %m %H %r %R<br clear="none">
&gt; follow_master.sh %d %h %p %D %M %P %m %H %r %R<br clear="none">
&gt; <br clear="none">
&gt; Pool status before shutdown of node 2:<br clear="none">
&gt; postgres=&gt; show pool_nodes;<br clear="none">
&gt;&nbsp; node_id |&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; hostname&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | port | status | lb_weight |&nbsp; role<br clear="none">
&gt;&nbsp; | select_cnt | load_balance_node | replication_delay<br clear="none">
&gt; ---------+----------------------------+------+--------+-----------+---------+------------+-------------------+-------------------<br clear="none">
&gt;&nbsp; 0&nbsp; &nbsp; &nbsp; &nbsp;| pg-hdp-node1.kitchen.local | 5432 | down&nbsp; &nbsp;| 0.333333&nbsp; | standby<br clear="none">
&gt; | 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | false&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| 0<br clear="none">
&gt;&nbsp; 1&nbsp; &nbsp; &nbsp; &nbsp;| pg-hdp-node2.kitchen.local | 5432 | up&nbsp; &nbsp; &nbsp;| 0.333333&nbsp; | primary<br clear="none">
&gt; | 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | false&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| 0<br clear="none">
&gt;&nbsp; 2&nbsp; &nbsp; &nbsp; &nbsp;| pg-hdp-node3.kitchen.local | 5432 | up&nbsp; &nbsp; &nbsp;| 0.333333&nbsp; | standby<br clear="none">
&gt; | 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | true&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | 0<br clear="none">
&gt; (3 rows)<br clear="none">
&gt; <br clear="none">
&gt; Pgpool log<br clear="none">
&gt; Feb 22 10:43:27 pg-hdp-node3 pgpool[12437]: [126-1] 2019-02-22 10:43:27:<br clear="none">
&gt; pid 12437: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:27 pg-hdp-node3 pgpool[12437]: [127-1] 2019-02-22 10:43:27:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:27 pg-hdp-node3 pgpool[12437]: [127-2] 2019-02-22 10:43:27:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432"<br clear="none">
&gt; failed<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [128-1] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; Failed to check replication time lag<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [128-2] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; No persistent db connection for the node 1<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [128-3] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: HINT:&nbsp; check sr_check_user and sr_check_password<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [128-4] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: CONTEXT:&nbsp; while checking replication time lag<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [129-1] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [130-1] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:37 pg-hdp-node3 pgpool[12437]: [130-2] 2019-02-22 10:43:37:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432"<br clear="none">
&gt; failed<br clear="none">
&gt; Feb 22 10:43:45 pg-hdp-node3 pgpool[7786]: [6-1] 2019-02-22 10:43:45: pid<br clear="none">
&gt; 7786: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:45 pg-hdp-node3 pgpool[7786]: [7-1] 2019-02-22 10:43:45: pid<br clear="none">
&gt; 7786: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:45 pg-hdp-node3 pgpool[7786]: [7-2] 2019-02-22 10:43:45: pid<br clear="none">
&gt; 7786: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432" failed<br clear="none">
&gt; Feb 22 10:43:45 pg-hdp-node3 pgpool[7786]: [8-1] 2019-02-22 10:43:45: pid<br clear="none">
&gt; 7786: LOG:&nbsp; health check retrying on DB node: 1 (round:1)<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [131-1] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; Failed to check replication time lag<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [131-2] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; No persistent db connection for the node 1<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [131-3] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: HINT:&nbsp; check sr_check_user and sr_check_password<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [131-4] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: CONTEXT:&nbsp; while checking replication time lag<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [132-1] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [133-1] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:47 pg-hdp-node3 pgpool[12437]: [133-2] 2019-02-22 10:43:47:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432"<br clear="none">
&gt; failed<br clear="none">
&gt; Feb 22 10:43:48 pg-hdp-node3 pgpool[7786]: [9-1] 2019-02-22 10:43:48: pid<br clear="none">
&gt; 7786: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:48 pg-hdp-node3 pgpool[7786]: [10-1] 2019-02-22 10:43:48: pid<br clear="none">
&gt; 7786: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:48 pg-hdp-node3 pgpool[7786]: [10-2] 2019-02-22 10:43:48: pid<br clear="none">
&gt; 7786: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432" failed<br clear="none">
&gt; Feb 22 10:43:48 pg-hdp-node3 pgpool[7786]: [11-1] 2019-02-22 10:43:48: pid<br clear="none">
&gt; 7786: LOG:&nbsp; health check retrying on DB node: 1 (round:2)<br clear="none">
&gt; Feb 22 10:43:51 pg-hdp-node3 pgpool[7786]: [12-1] 2019-02-22 10:43:51: pid<br clear="none">
&gt; 7786: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:51 pg-hdp-node3 pgpool[7786]: [13-1] 2019-02-22 10:43:51: pid<br clear="none">
&gt; 7786: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:51 pg-hdp-node3 pgpool[7786]: [13-2] 2019-02-22 10:43:51: pid<br clear="none">
&gt; 7786: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432" failed<br clear="none">
&gt; Feb 22 10:43:51 pg-hdp-node3 pgpool[7786]: [14-1] 2019-02-22 10:43:51: pid<br clear="none">
&gt; 7786: LOG:&nbsp; health check retrying on DB node: 1 (round:3)<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7786]: [15-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7786: LOG:&nbsp; failed to connect to PostgreSQL server on<br clear="none">
&gt; "pg-hdp-node2.kitchen.local:5432", getsockopt() detected error "Connection<br clear="none">
&gt; refused"<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7786]: [16-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7786: ERROR:&nbsp; failed to make persistent db connection<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7786]: [16-2] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7786: DETAIL:&nbsp; connection to host:"pg-hdp-node2.kitchen.local:5432" failed<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7786]: [17-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7786: LOG:&nbsp; health check failed on node 1 (timeout:0)<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7786]: [18-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7786: LOG:&nbsp; received degenerate backend request for node_id: 1 from pid<br clear="none">
&gt; [7786]<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7746]: [253-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7746: LOG:&nbsp; Pgpool-II parent process has received failover request<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7746]: [254-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7746: LOG:&nbsp; starting degeneration. shutdown host<br clear="none">
&gt; pg-hdp-node2.kitchen.local(5432)<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7746]: [255-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7746: LOG:&nbsp; Restart all children<br clear="none">
&gt; Feb 22 10:43:54 pg-hdp-node3 pgpool[7746]: [256-1] 2019-02-22 10:43:54: pid<br clear="none">
&gt; 7746: LOG:&nbsp; execute command: /etc/pgpool-II/failover.sh 1<br clear="none">
&gt; pg-hdp-node2.kitchen.local 5432 /var/lib/pgsql/10/data 1 1 2<br clear="none">
&gt; pg-hdp-node3.kitchen.local 5432 /var/lib/pgsql/10/data<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [257-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; find_primary_node_repeatedly: waiting for finding a primary node<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [258-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; find_primary_node: checking backend no 0<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [259-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; find_primary_node: checking backend no 1<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [260-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; find_primary_node: checking backend no 2<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [261-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; find_primary_node: primary node id is 2<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [262-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; starting follow degeneration. shutdown host<br clear="none">
&gt; pg-hdp-node1.kitchen.local(5432)<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [263-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; starting follow degeneration. shutdown host<br clear="none">
&gt; pg-hdp-node2.kitchen.local(5432)<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [264-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; failover: 2 follow backends have been degenerated<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [265-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; failover: set new primary node: 2<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [266-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; failover: set new master node: 2<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[7746]: [267-1] 2019-02-22 10:43:55: pid<br clear="none">
&gt; 7746: LOG:&nbsp; failover done. shutdown host pg-hdp-node2.kitchen.local(5432)<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12437]: [134-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12437: ERROR:&nbsp; Failed to check replication time lag<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12437]: [134-2] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12437: DETAIL:&nbsp; No persistent db connection for the node 1<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12437]: [134-3] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12437: HINT:&nbsp; check sr_check_user and sr_check_password<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12437]: [134-4] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12437: CONTEXT:&nbsp; while checking replication time lag<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12437]: [135-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12437: LOG:&nbsp; worker process received restart request<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12774]: [267-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12774: LOG:&nbsp; failback event detected<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12774]: [267-2] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12774: DETAIL:&nbsp; restarting myself<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12742]: [265-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12742: LOG:&nbsp; start triggering follow command.<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12742]: [266-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12742: LOG:&nbsp; execute command: /etc/pgpool-II/follow_master.sh 0<br clear="none">
&gt; pg-hdp-node1.kitchen.local 5432 /var/lib/pgsql/10/data 1 1 2<br clear="none">
&gt; pg-hdp-node3.kitchen.local 5432 /var/lib/pgsql/10/data<br clear="none">
&gt; Feb 22 10:43:55 pg-hdp-node3 pgpool[12742]: [267-1] 2019-02-22 10:43:55:<br clear="none">
&gt; pid 12742: LOG:&nbsp; execute command: /etc/pgpool-II/follow_master.sh 1<br clear="none">
&gt; pg-hdp-node2.kitchen.local 5432 /var/lib/pgsql/10/data 1 1 2<br clear="none">
&gt; pg-hdp-node3.kitchen.local 5432 /var/lib/pgsql/10/data<br clear="none">
&gt; Feb 22 10:43:56 pg-hdp-node3 pgpool[12436]: [60-1] 2019-02-22 10:43:56: pid<br clear="none">
&gt; 12436: LOG:&nbsp; restart request received in pcp child process<br clear="none">
&gt; Feb 22 10:43:56 pg-hdp-node3 pgpool[7746]: [268-1] 2019-02-22 10:43:56: pid<br clear="none">
&gt; 7746: LOG:&nbsp; PCP child 12436 exits with status 0 in failover()<br clear="none">
&gt; <br clear="none">
&gt; Pgpool self-explanatory failover.log<br clear="none">
&gt; <br clear="none">
&gt; 2019-02-22 10:43:54.893 PST Executing failover script ...<br clear="none">
&gt; 2019-02-22 10:43:54.895 PST Script arguments:<br clear="none">
&gt; failed_node_id&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1<br clear="none">
&gt; failed_node_host&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;pg-hdp-node2.kitchen.local<br clear="none">
&gt; failed_node_port&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; failed_node_pgdata&nbsp; &nbsp; &nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; old_primary_node_id&nbsp; &nbsp; &nbsp; 1<br clear="none">
&gt; old_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;1<br clear="none">
&gt; new_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;2<br clear="none">
&gt; new_master_node_host&nbsp; &nbsp; &nbsp;pg-hdp-node3.kitchen.local<br clear="none">
&gt; new_master_node_port&nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; new_master_node_pgdata&nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; 2019-02-22 10:43:54.897 PST Primary node running on<br clear="none">
&gt; pg-hdp-node2.kitchen.local host is unresponsive or have died<br clear="none">
&gt; 2019-02-22 10:43:54.898 PST Attempting to stop primary node running on<br clear="none">
&gt; pg-hdp-node2.kitchen.local host before promoting slave as the new primary<br clear="none">
&gt; 2019-02-22 10:43:54.899 PST ssh -o StrictHostKeyChecking=no -i<br clear="none">
&gt; /var/lib/pgsql/.ssh/id_rsa postgres@pg-hdp-node2.kitchen.local -T<br clear="none">
&gt; /usr/pgsql-10/bin/pg_ctl -D /var/lib/pgsql/10/data stop -m fast<br clear="none">
&gt; 2019-02-22 10:43:55.151 PST Promoting pg-hdp-node3.kitchen.local host as<br clear="none">
&gt; the new primary<br clear="none">
&gt; 2019-02-22 10:43:55.153 PST ssh -o StrictHostKeyChecking=no -i<br clear="none">
&gt; /var/lib/pgsql/.ssh/id_rsa postgres@pg-hdp-node3.kitchen.local -T<br clear="none">
&gt; /usr/pgsql-10/bin/pg_ctl -D /var/lib/pgsql/10/data promote<br clear="none">
&gt; waiting for server to promote.... done<br clear="none">
&gt; server promoted<br clear="none">
&gt; 2019-02-22 10:43:55.532 PST Completed executing failover<br clear="none">
&gt; <br clear="none">
&gt; 2019-02-22 10:43:55.564 PST Executing follow master script ...<br clear="none">
&gt; 2019-02-22 10:43:55.566 PST Script arguments<br clear="none">
&gt; detached_node_id&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br clear="none">
&gt; detached_node_host&nbsp; &nbsp; &nbsp; &nbsp;pg-hdp-node1.kitchen.local<br clear="none">
&gt; detached_node_port&nbsp; &nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; detached_node_pgdata&nbsp; &nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; old_primary_node_id&nbsp; &nbsp; &nbsp; 1<br clear="none">
&gt; old_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;1<br clear="none">
&gt; new_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;2<br clear="none">
&gt; new_master_node_host&nbsp; &nbsp; &nbsp;pg-hdp-node3.kitchen.local<br clear="none">
&gt; new_master_node_port&nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; new_master_node_pgdata&nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; 2019-02-22 10:43:55.567 PST Checking if server is running on<br clear="none">
&gt; pg-hdp-node1.kitchen.local host<br clear="none">
&gt; 2019-02-22 10:43:55.569 PST ssh -o StrictHostKeyChecking=no -i<br clear="none">
&gt; /var/lib/pgsql/.ssh/id_rsa postgres@pg-hdp-node1.kitchen.local -T<br clear="none">
&gt; /usr/pgsql-10/bin/pg_ctl -D /var/lib/pgsql/10/data status<br clear="none">
&gt; <br clear="none">
&gt; <br clear="none">
&gt; pg_ctl: no server running<br clear="none">
&gt; 2019-02-22 10:43:55.823 PST Node on pg-hdp-node1.kitchen.local host is not<br clear="none">
&gt; running. It could be old slave or primary that needs to be recovered.<br clear="none">
&gt; 2019-02-22 10:43:55.824 PST Completed executing follow master script<br clear="none">
&gt; <br clear="none">
&gt; 2019-02-22 10:43:55.829 PST Executing follow master script ...<br clear="none">
&gt; 2019-02-22 10:43:55.830 PST Script arguments<br clear="none">
&gt; detached_node_id&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1<br clear="none">
&gt; detached_node_host&nbsp; &nbsp; &nbsp; &nbsp;pg-hdp-node2.kitchen.local<br clear="none">
&gt; detached_node_port&nbsp; &nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; detached_node_pgdata&nbsp; &nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; old_primary_node_id&nbsp; &nbsp; &nbsp; 1<br clear="none">
&gt; old_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;1<br clear="none">
&gt; new_master_node_id&nbsp; &nbsp; &nbsp; &nbsp;2<br clear="none">
&gt; new_master_node_host&nbsp; &nbsp; &nbsp;pg-hdp-node3.kitchen.local<br clear="none">
&gt; new_master_node_port&nbsp; &nbsp; &nbsp;5432<br clear="none">
&gt; new_master_node_pgdata&nbsp; &nbsp;/var/lib/pgsql/10/data<br clear="none">
&gt; 2019-02-22 10:43:55.831 PST Detached node on pg-hdp-node2.kitchen.local<br clear="none">
&gt; host is the the old primary node<br clear="none">
&gt; 2019-02-22 10:43:55.833 PST Slave can be created from old primary node by<br clear="none">
&gt; deleting PG_DATA directory under /var/lib/pgsql/10/data on<br clear="none">
&gt; pg-hdp-node2.kitchen.local host and re-running Chef client<br clear="none">
&gt; 2019-02-22 10:43:55.834 PST Slave can be recovered from old primary node by<br clear="none">
&gt; running /usr/pgsql-10/bin/pg_rewind -D /var/lib/pgsql/10/data<br clear="none">
&gt; --source-server="port=5432 host=pg-hdp-node3.kitchen.local" command on<br clear="none">
&gt; pg-hdp-node2.kitchen.local host as postgres user<br clear="none">
&gt; 2019-02-22 10:43:55.835 PST After successful pg_rewind run cp<br clear="none">
&gt; /var/lib/pgsql/10/data/recovery.done /var/lib/pgsql/10/data/recovery.conf,<br clear="none">
&gt; ensure host connection string points to pg-hdp-node3.kitchen.local, start<br clear="none">
&gt; PostgreSQL and attach it to pgpool<br clear="none">
&gt; 2019-02-22 10:43:55.836 PST Completed executing follow master script<br clear="none">
&gt; <br clear="none">
&gt; On Thu, Feb 21, 2019 at 4:47 PM Tatsuo Ishii &lt;<a shape="rect" href="mailto:ishii@sraoss.co.jp" rel="nofollow" target="_blank">ishii@sraoss.co.jp</a>&gt; wrote:<br clear="none">
&gt; <br clear="none">
&gt;&gt; &gt; Is this correct behavior?<br clear="none">
&gt;&gt; &gt;<br clear="none">
&gt;&gt; &gt; In 3-node setup, node1(primary) is shutdown, failover is executed and<br clear="none">
&gt;&gt; node2<br clear="none">
&gt;&gt; &gt; becomes new primary and node3 follows new primary on node2.<br clear="none">
&gt;&gt; &gt; Now, node2(new primary) is shutdown, failover is executed and node3<br clear="none">
&gt;&gt; becomes<br clear="none">
&gt;&gt; &gt; new primary but fallow_master_command is executed on node1 even though it<br clear="none">
&gt;&gt; &gt; is reported as down.<br clear="none">
&gt;&gt;<br clear="none">
&gt;&gt; No. follow master command should not be executed on an already-down<br clear="none">
&gt;&gt; node (in this case node1).<br clear="none">
&gt;&gt;<br clear="none">
&gt;&gt; &gt; It happens that my script repoints node1 and restarts it which breaks<br clear="none">
&gt;&gt; hell<br clear="none">
&gt;&gt; &gt; because node1 was never recovered after being shutdown.<br clear="none">
&gt;&gt; &gt;<br clear="none">
&gt;&gt; &gt; I'm on PgPool 3.7.4.<br clear="none">
&gt;&gt;<br clear="none">
&gt;&gt; Can you share the log from when node2 was shutdown to when node1 was<br clear="none">
&gt;&gt; recovered by your follow master command?<br clear="none">
&gt;&gt;<br clear="none">
&gt;&gt; In the mean time 3.7.4 is not the latest one. Can you try with the<br clear="none">
&gt;&gt; latest one? (3.7.8).<br clear="none">
&gt;&gt;<br clear="none">
&gt;&gt; Best regards,<br clear="none">
&gt;&gt; --<br clear="none">
&gt;&gt; Tatsuo Ishii<br clear="none">
&gt;&gt; SRA OSS, Inc. Japan<br clear="none">
&gt;&gt; English: <a shape="rect" href="http://www.sraoss.co.jp/index_en.php" rel="nofollow" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br clear="none">
&gt;&gt; Japanese:<a shape="rect" href="http://www.sraoss.co.jp" rel="nofollow" target="_blank">http://www.sraoss.co.jp</a><br clear="none">
&gt;&gt;<br clear="none">
&gt; <br clear="none">
&gt; <br clear="none">
&gt; -- <br clear="none">
&gt; <br clear="none">
&gt; *Andre Piwoni*<br clear="none"><br clear="none"></blockquote></div></div></div></div></div><div class="ydp2b963b2ayqt4592847929" id="ydp2b963b2ayqtfd69905">_______________________________________________<br clear="none">pgpool-general mailing list<br clear="none"><a shape="rect" href="mailto:pgpool-general@pgpool.net" rel="nofollow" target="_blank">pgpool-general@pgpool.net</a><br clear="none"><a shape="rect" href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="nofollow" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br clear="none"></div></div>
            </div>
        </div></body></html>