> 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@adt-web01 pgpool-II-3.0.3]# pcp_node_info 10 adt-web01 9898 postgres
> postgres 0
> adt-db01 5432 1 0.500000
> [root@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
Index: recovery.c
===================================================================
RCS file: /cvsroot/pgpool/pgpool-II/recovery.c,v
retrieving revision 1.20
diff -c -r1.20 recovery.c
*** recovery.c 7 Mar 2011 07:00:14 -0000 1.20
--- recovery.c 25 Apr 2011 22:54:41 -0000
***************
*** 71,78 ****
conn = connect_backend_libpq(backend);
if (conn == NULL)
{
! PQfinish(conn);
! pool_error("start_recover: could not connect master node.");
return 1;
}
--- 71,77 ----
conn = connect_backend_libpq(backend);
if (conn == NULL)
{
! pool_error("start_recovery: could not connect master node (%d)", node_id);
return 1;
}
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general