<div dir="ltr">I looked into pgpool log from node 1 (which is the master now) and attached part of it.<div>From what it seems, it does both stage 1 and 2, but failback request is canceled by other pgpool.</div><div>Don't know why this is happening.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em ter., 18 de ago. de 2020 às 08:59, Rinaldo Akio Uehara <<a href="mailto:rinaldo.uehara@gmail.com">rinaldo.uehara@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">After a maintenance where I needed to add disk, I started postgresql and pgpool in each node (3 nodes total).<div>The first two came back OK after doing the pcp_recovery.</div><div>The third one (although status on pgsql is fine) never comes with the status "up"</div><div><br></div><div>[postgres@spcdmvm8021 ~]$ psql -h 192.168.21.60 -p 5000 -U pgpool postgres -c "show pool_nodes"<br>Password for user pgpool: <br> node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay | replication_state | replication_sync_state | last_status_change <br>---------+-------------+------+--------+-----------+---------+------------+-------------------+-------------------+-------------------+------------------------+---------------------<br> 0 | spcdmvm8019 | 5432 | up | 0.333333 | primary | 76254 | true | 0 | | | 2020-08-18 00:34:14<br> 1 | spcdmvm8020 | 5432 | up | 0.333333 | standby | 52491 | false | 0 | streaming | async | 2020-08-18 00:34:14<br> 2 | spcdmvm8021 | 5432 | down | 0.333333 | standby | 0 | false | 0 | streaming | async | 2020-08-17 23:21:39<br>(3 rows)<br><br>[postgres@spcdmvm8021 ~]$ pcp_recovery_node -h 192.168.21.60 -p 9898 -U pgpool -n 2<br>Password: <br>pcp_recovery_node -- Command Successful<br>[postgres@spcdmvm8021 ~]$ psql -h 192.168.21.60 -p 5000 -U pgpool postgres -c "show pool_nodes"<br>Password for user pgpool: <br> node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay | replication_state | replication_sync_state | last_status_change <br>---------+-------------+------+--------+-----------+---------+------------+-------------------+-------------------+-------------------+------------------------+---------------------<br> 0 | spcdmvm8019 | 5432 | up | 0.333333 | primary | 76556 | false | 0 | | | 2020-08-18 00:34:14<br> 1 | spcdmvm8020 | 5432 | up | 0.333333 | standby | 52634 | true | 0 | streaming | async | 2020-08-18 00:34:14<br> 2 | spcdmvm8021 | 5432 | down | 0.333333 | standby | 0 | false | 0 | streaming | async | 2020-08-17 23:21:39<br>(3 rows)</div><div><br></div><div>Not sure why this happened. </div><div>I changed the log details on the faulty one to see if I could see any error, but didn't notice anything</div><div><br></div><div>I attached the log of the server at fault and the 3 configs.</div><div><br></div><div>Thanks for any help.</div><div><div><br></div>-- <br><div dir="ltr">Rinaldo Akio Uehara</div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Rinaldo Akio Uehara</div>