[pgpool-general: 6492] Re: Reset old data in pgpool

Dmitry Medvedev dm.dm.medvedev at gmail.com
Wed Apr 3 23:51:42 JST 2019


I am using pgpool 4.0.4
3 vitrual machines:
temp 172.28.30.5 - with pgpool, no PostgreSQL
temp2 172.28.30.6 - primary PostgreSQL
temp3 172.28.30.7 - standby PostgreSQL

Query select pg_is_in_recovery(); returns "f" on temp2 and "t" on temp3.

[root at temp ~]# journalctl --unit pgpool.service
-- Logs begin at Wed 2019-04-03 16:47:13 MSK, end at Wed 2019-04-03
17:50:42 MSK. --
Apr 03 16:55:32 temp systemd[1]: Started Pgpool-II.
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
Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:32: pid 4696: LOG:
Setting up socket for 0.0.0.0:9999
Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:32: pid 4696: LOG:
Setting up socket for :::9999
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
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
Apr 03 16:55:33 temp pgpool[4696]: 2019-04-03 16:55:33: pid 4696: DETAIL:
EOF encountered with backend
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
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
Apr 03 16:55:34 temp pgpool[4696]: 2019-04-03 16:55:34: pid 4696: DETAIL:
EOF encountered with backend
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
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
Apr 03 16:55:35 temp pgpool[4696]: 2019-04-03 16:55:35: pid 4696: DETAIL:
EOF encountered with backend
...and so on...

ср, 3 апр. 2019 г. в 17:43, Tatsuo Ishii <ishii at sraoss.co.jp>:

> > Hello to everyone. A couple of days I've spent trying to understand how
> > pgpool-II works.
> >
> > After some cruel experiments I've broken my pgpool cluster (1 primary
> and 1
> > standby nodes) :-)
> >
> > I've re-configured it and launched pgpool again. And now all nodes have
> > "standby" role no matter what i do. Is there any way of reset pgpool?
> Nodes
> > without pgpool operating correctly: one is primary, other is standby.
>
> It is likely that Pgpool-II failed to detect the primary. Which
> version of Pgpool-II are you using? Can you share Pgpool-II debug log
> right after starting up it? It detects the primary upon starting up.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190403/2eb67513/attachment.html>


More information about the pgpool-general mailing list