<div dir="ltr"><div dir="ltr"><div dir="ltr">I am using pgpool 4.0.4</div><div dir="ltr">3 vitrual machines:</div><div dir="ltr">temp 172.28.30.5 - with pgpool, no PostgreSQL</div><div dir="ltr">temp2 172.28.30.6 - primary PostgreSQL</div><div dir="ltr">temp3 172.28.30.7 - standby PostgreSQL</div><div dir="ltr"><br></div><div dir="ltr"><div>Query select pg_is_in_recovery(); returns "f" on temp2 and "t" on temp3.<br></div><div><br></div><div><div>[root@temp ~]# journalctl --unit pgpool.service</div><div>-- Logs begin at Wed 2019-04-03 16:47:13 MSK, end at Wed 2019-04-03 17:50:42 MSK. --</div><div>Apr 03 16:55:32 temp systemd[1]: Started Pgpool-II.</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:32: pid 4696: LOG: reading status file: 0 th backend is set to down status</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:32: pid 4696: LOG: Setting up socket for <a href="http://0.0.0.0:9999">0.0.0.0:9999</a></div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:32: pid 4696: LOG: Setting up socket for :::9999</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:33: pid 4696: LOG: find_primary_node_repeatedly: waiting for finding a primary node</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:33: pid 4696: ERROR: unable to read data from DB node 1</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:33: pid 4696: DETAIL: EOF encountered with backend</div><div>Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:33: pid 4696: LOG: find_primary_node: make_persistent_db_connection_noerror failed on</div><div>Apr 03 16:55:34 temp pgpool[4696]: 2019-04-03 16:55:34: pid 4696: ERROR: unable to read data from DB node 1</div><div>Apr 03 16:55:34 temp pgpool[4696]: 2019-04-03 16:55:34: pid 4696: DETAIL: EOF encountered with backend</div><div>Apr 03 16:55:34 temp pgpool[4696]: 2019-04-03 16:55:34: pid 4696: LOG: find_primary_node: make_persistent_db_connection_noerror failed on</div><div>Apr 03 16:55:35 temp pgpool[4696]: 2019-04-03 16:55:35: pid 4696: ERROR: unable to read data from DB node 1</div><div>Apr 03 16:55:35 temp pgpool[4696]: 2019-04-03 16:55:35: pid 4696: DETAIL: EOF encountered with backend</div></div><div>...and so on...</div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ср, 3 апр. 2019 г. в 17:43, Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Hello to everyone. A couple of days I've spent trying to understand how<br>
> pgpool-II works.<br>
> <br>
> After some cruel experiments I've broken my pgpool cluster (1 primary and 1<br>
> standby nodes) :-)<br>
> <br>
> I've re-configured it and launched pgpool again. And now all nodes have<br>
> "standby" role no matter what i do. Is there any way of reset pgpool? Nodes<br>
> without pgpool operating correctly: one is primary, other is standby.<br>
<br>
It is likely that Pgpool-II failed to detect the primary. Which<br>
version of Pgpool-II are you using? Can you share Pgpool-II debug log<br>
right after starting up it? It detects the primary upon starting up.<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div>