[Pgpool-general] failback setup problem

Tatsuo Ishii ishii at sraoss.co.jp
Mon Apr 25 23:06:47 UTC 2011


> I'm using pg-pool-II 3.0.3 with streaming replication.
> I coded the failback scenario/script for the slave server and the script
> itself works fine.
> 
> I now configured the failback script in pgpool.conf and during testing an
> error message comes up:
> 2011-04-09 06:42:18 LOG:   pid 16863: starting recovering node 1
> 2011-04-09 06:42:18 ERROR: pid 16863: start_recover: could not connect
> master node.
> 
> [root at adt-web01 pgpool-II-3.0.3]# pcp_node_info 10 adt-web01 9898 postgres
> postgres 0
> adt-db01 5432 1 0.500000
> [root at adt-web01 pgpool-II-3.0.3]# pcp_node_info 10 adt-web01 9898 postgres
> postgres 1
> adt-db02 5432 3 0.500000
> 
> pcp commands and pgpooladmin report that the master is up and running and
> I'm able to connect to the master directly and through pgpool.
> So what's wrong? So far everything else works fine.

Assuming you have set recovery_user and recovery_passwd correctly, I'm
not sure what's going on. IMO, the error message is very rare. It's so
rare and there's a bug in the error path, which had not been found for
long time. Can please try attached patch? The patch add a little bit
usefull info to the error message above.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: recovery.patch
Type: text/x-patch
Size: 664 bytes
Desc: not available
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20110426/8f0378f8/attachment.bin>


More information about the Pgpool-general mailing list