<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 29, 2012 at 12:57 AM, Glyn Astill <span dir="ltr"><<a href="mailto:glynastill@yahoo.co.uk" target="_blank">glynastill@yahoo.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Tory<br>
<br>
> From: Tory M Blue <<a href="mailto:tmblue@gmail.com">tmblue@gmail.com</a>><br>
<br>
>To: slony1-general <<a href="mailto:slony1-general@lists.slony.info">slony1-general@lists.slony.info</a>><br>
>Sent: Wednesday, 28 November 2012, 18:35<br>
>Subject: [Slony1-general] data copy for set 1 failed 3 times - sleep 60 seconds<br>
><br>
><br>
>Greetings<br>
><br>
>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,<br>
><br>
>I'm getting these errors and can't get the initial replication to finish<br>
><br>
>4273435:2012-11-27 16:45:17 PST WARN remoteWorkerThread_1: data copy for set 1 failed 3 times - sleep 60 seconds<br>
><br>
<br>
Is that the only line you get in your logs? If so use a higher setting for log_level (like log_level=4).<br>
<br>
Also is there anything in the postgresql log to indicate the problem?<br></blockquote><div><br>I get the following<br><br>2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: 3858.988 seconds to copy table "cls"."listings"<br>
2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: copy table "cls"."customers"<br>2012-11-29 08:34:38 PST CONFIG remoteWorkerThread_1: Begin COPY of table "cls"."customers"<br>2012-11-29 08:34:38 PST ERROR remoteWorkerThread_1: "select "_admissioncls".copyFields(8);" <br>
2012-11-29 08:34:38 PST WARN remoteWorkerThread_1: data copy for set 1 failed 1 times - sleep 15 seconds<br>2012-11-29 08:34:39 PST DEBUG2 localListenThread: Received event 10,5000000195 SYNC<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
>The above error causes a rollback and a complete subscribe node/set restart<br>
><br>
>This is postgres 9.1.4 and slony 2.1.1<br>
><br>
>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?<br>
><br>
<br>
Could be, what platform is it on? Is there anything in syslog or messages?<br></blockquote><div><br>CentOS6.2 <br>Nothing that I see in dmesg or messages. <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
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<br>
</blockquote><div><br>I'll keep poking around, don't see anything from oom, thankfully!<br><br>Tory <br></div></div><br></div>