Hi Everybody (again). We are testing online recovery process. We have started by using a simple sync method (no PITR) between our two databases. However, when performing an online recovery, we get this error: BackendError Pgpool log has these entries. Node 0 has status 3 (has been previously detached) and node 1 is selected as master node. However, when launching pcp_recovery_node on node 0 the BackendError appears. For this testing, we have used a faster approach using a common filesystem for both databases. User postgres is the same and our recovery scripts uses "cp -Rfp" instead rsync, but basically it's the same as using rsync. 2009-01-14 17:27:43 DEBUG: pid 13342: starting health checking 2009-01-14 17:27:43 DEBUG: pid 13342: health_check: 0 the DB node status: 3 2009-01-14 17:27:43 DEBUG: pid 13342: health_check: 1 the DB node status: 1 2009-01-14 17:28:02 DEBUG: pid 13375: I am PCP 13375 accept fd 5 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: received PCP packet type of service 'M' 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: salt sent to the client 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: received PCP packet type of service 'R' 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: authentication OK 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: received PCP packet type of service 'O' 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: start online recovery 2009-01-14 17:28:02 LOG: pid 13375: starting recovering node 0 2009-01-14 17:28:02 ERROR: pid 13375: start_recover: could not connect master node. 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: received PCP packet type of service 'X' 2009-01-14 17:28:02 DEBUG: pid 13375: pcp_child: client disconnecting. close connection
What does "could not connect master node" could mean? Thanks in advance.
_______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
