<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Feb 16, 2014 at 5:06 PM, Jeff Frost <span dir="ltr"><<a href="mailto:jeff@pgexperts.com" target="_blank">jeff@pgexperts.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Feb 16, 2014, at 5:00 PM, Tory M Blue <<a href="mailto:tmblue@gmail.com">tmblue@gmail.com</a>> wrote:<br>
<br>
><br>
><br>
><br>
> As can be seen the connection is reaped, slon/postgres continue on their way, it's not until the next data copy is required that it finds it's connection is no longer there. Why it can't recreate a conneciton as one would do if they stopped and started slon is kind of beyond me. Just not 100% sure where it's being killed.<br>
><br>
<br>
Because the initial sync must be done as a single transaction.<br>
<br>
<br>
><br>
> 2014-02-16 16:40:46 PST CONFIG remoteWorkerThread_1: 7183.069 seconds to copy table "tracking"."spotlightimp"<br>
> 2014-02-16 16:40:46 PST CONFIG remoteWorkerThread_1: copy table "tracking"."adimp"<br>
> 2014-02-16 16:40:46 PST CONFIG remoteWorkerThread_1: Begin COPY of table "tracking"."adimp"<br>
> 2014-02-16 16:40:46 PST ERROR remoteWorkerThread_1: "select "_cls".copyFields(19);"<br>
> 2014-02-16 16:40:46 PST WARN remoteWorkerThread_1: data copy for set 2 failed 1 times - sleep 15 seconds<br>
> NOTICE: Slony-I: Logswitch to sl_log_2 initiated<br>
> CONTEXT: SQL statement "SELECT "_cls".logswitch_start()"<br>
> PL/pgSQL function _cls.cleanupevent(interval) line 96 at PERFORM<br>
> 2014-02-16 16:40:49 PST INFO cleanupThread: 6541.365 seconds for cleanupEvent()<br>
><br>
><br>
> Am I doing this wrong? figured that since I've seen connections at 15 minutes of processing complete fine, I thought that 30 minutes is more then enough. So send the first hey are you still there at 15 minutes then continue with them every 5 minutes, for a count of 30.<br>
><br>
> But the above seems to have been reaped in the 20 minute area..<br>
><br>
> net.ipv4.tcp_keepalive_time = 600<br>
> net.ipv4.tcp_keepalive_probes = 30<br>
> net.ipv4.tcp_keepalive_intvl = 300<br>
<br>
<br>
Set it so that it's sending keepalives every 30 seconds.<br>
<br>
Something like this:<br>
<br>
net.ipv4.tcp_keepalive_time = 30<br>
net.ipv4.tcp_keepalive_probes = 10<br>
net.ipv4.tcp_keepalive_intvl = 30<br>
<br>
What version of slony are you using? You may need to specifically enabled keepalive.<br>
<br>
<br></blockquote><div><br></div><div>Slony 2.1.3</div><div><br></div><div>I've actually got it working, some tuning (Sorry Jen, did it in the kernel) and found that my vpn tunnel was set to a 30 minute timeout, so bumped that to 120 minutes) and so far things seem to be working), took me a long time to get this far, but I appreciate the assistance.</div>
<div><br></div><div>I'll look at the settings inside slony vs the kernel, just in case I wanted to sync to the moon :)))</div><div><br></div><div>Thanks again</div><div><br></div><div>Tory </div></div><br></div></div>