I just recently encountered the same error.  It was caused by a cascaded
server that had its listen paths set up to pull from the wrong server.
You might want to check there...

-----Original Message-----
From: slony1-general-bounces at gborg.postgresql.org
[mailto:slony1-general-bounces at gborg.postgresql.org] On Behalf Of Erik
G. Burrows
Sent: Tuesday, November 28, 2006 6:23 PM
To: slony1-general at gborg.postgresql.org
Subject: [Slony1-general] Repeating error: copy set: data provider 2
only onsync -1 - sleep 5 seconds

I have four PostgreSQL databases, all 8.1, except for one that is 7.4
series.

I just altered my replication configuration to drop two tables from a
replication set on node 2, in order to create a new set, origin node 2,
that would be replicated to node 1, 3 and 4, like this:

set drop table (origin=2, id = 1052);
set drop table (origin=2, id = 1029);

create set (id=6, origin=2, comment='Customer config for spawn');

set add table (set id=6, origin=2, id=6001, fully qualified name =
'public.custinfo');
set add table (set id=6, origin=2, id=6002, fully qualified name =
'public.crediguard');

subscribe set ( id = 6, provider = 2, receiver = 1, forward = yes);
subscribe set ( id = 6, provider = 2, receiver = 3, forward = yes);
subscribe set ( id = 6, provider = 2, receiver = 4, forward = yes);

After executing these slonik commands, node 1 is replicating the new set
(id=6) fine, but nodes 3 and 4 are not, and both spitting out these logs
from slon:

2006-11-28 15:19:55 PST WARN   remoteWorkerThread_2: copy set: data
provider 2 only on sync -1 - sleep 5 seconds
2006-11-28 15:20:00 PST WARN   remoteWorkerThread_2: copy set: data
provider 2 only on sync -1 - sleep 5 seconds
2006-11-28 15:20:05 PST WARN   remoteWorkerThread_2: copy set: data
provider 2 only on sync -1 - sleep 5 seconds

Any ideas on how I can get these guys on speaking terms again?

Thanks,
  Erik G. Burrows

_______________________________________________
Slony1-general mailing list
Slony1-general at gborg.postgresql.org
http://gborg.postgresql.org/mailman/listinfo/slony1-general


Disclaimer: Any references to Pipeline performance contained herein are based on historic performance levels which Pipeline expects to maintain or exceed but nevertheless does not guarantee. Congested networks, price volatility, or other extraordinary events may impede future trading activities and degrade performance statistics.