Hi Tory

> From: Tory M Blue <tmblue at gmail.com>

>To: slony1-general <slony1-general at lists.slony.info> 
>Sent: Wednesday, 28 November 2012, 18:35
>Subject: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds
> 
>
>Greetings
>
>I've just brought up a replication node across the state, we have gig circuits, but still going over the net over a vpn tunnel. So there is some delay,
>
>I'm getting these errors and can't get the initial replication to finish
>
>4273435:2012-11-27 16:45:17 PST WARN   remoteWorkerThread_1: data copy for set 1 failed 3 times - sleep 60 seconds
>

Is that the only line you get in your logs?  If so use a higher setting for log_level (like log_level=4).

Also is there anything in the postgresql log to indicate the problem?


>The above error causes a rollback and a complete subscribe node/set restart
>
>This is postgres 9.1.4 and slony 2.1.1
>
>I'm not sure if something is reaping the connection or something internal to slon. Is there configuration settings I should adjust or a watcher or something else daemon that I should be running?
>

Could be, what platform is it on?  Is there anything in syslog or messages?

Check the postgres log first, it could be something like another transaction blocking it, or like you say some other reason for the connection to be hoofed out like a flakey connection, ssl renegotiation, oom killer etc