<div class="gmail_quote">On Wed, Jan 13, 2010 at 7:23 AM, Ed Coates <span dir="ltr"><<a href="mailto:ed@coatesfam.us">ed@coatesfam.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
rsync: connection unexpectedly closed (338935497 bytes received so far) [sender]<br>[...] Any clues on why it might be losing connection?</blockquote></div><div><br></div>In a local connection the sender is the client side, so this is indicating that the receiving side went away. Because you got no terminating message, it is probable that the receiver was the process that died first, and its message did not make it through the generator before things closed down. You might try the latest "nightly" tar file rsync release of 3.1.0dev, which should do better at getting the errors to you when an abnormal shutdown is happening. Or, to diagnose what you're running now, you can turn off some of the verbosity and attach an strace to each of the receiving rsyncs after the transfer starts up. That should reveal why the process died.<div>
<br>..wayne..<br>
</div>