public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Continued rsync failures
Date: Fri, 7 May 2021 14:09:46 -0400	[thread overview]
Message-ID: <a10cf2c2-e1ce-fe0e-2f72-6fd488a00a3d@cornell.edu> (raw)
In-Reply-To: <745b958a-4edc-b6ca-e61f-d143ccd3f8c0@pdc.ca>

On 5/7/2021 12:43 PM, Brent Epp wrote:
> Hello,
> 
> I've reported this in the past, but I cannot reliably use rsync. This is a 
> *local* synchronization between two Windows directories.  It seems that after a 
> number of executions (a few dozen, maybe?), it just stops working and reports 
> errors:
> 
>     rsync: connection unexpectedly closed (185 bytes received so far) [generator]
>     rsync error: error in rsync protocol data stream (code 12) at io.c(228) 
> [generator=3.2.4dev]
>     rsync: connection unexpectedly closed (0 bytes received so far) [sender]
>     rsync error: error in rsync protocol data stream (code 12) at io.c(228) 
> [sender=3.2.4dev]
> 
> I have upgraded to the latest version of cygwin as of this morning and the 
> problem persists.  I have no software on the BLODA list and I have tried with 
> all security software disabled.
> 
> The only thing I can do is wait for a period of time (never timed it, but 10-20 
> minutes or so), which is immensely frustrating, as I am heavily dependent on it 
> for work.
> 
> How can get I this working once and for all?

Please run the failing rsync command under strace, like this:

   strace -o strace.out rsync....

Then post the output file strace.out somewhere where others can look at it.

Ken

  reply	other threads:[~2021-05-07 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 16:43 Brent Epp
2021-05-07 18:09 ` Ken Brown [this message]
2021-05-08 15:03   ` Brent Epp
2021-05-08 19:36     ` Ken Brown
2021-05-09 13:13       ` Mark Hansen
2021-05-07 19:03 ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a10cf2c2-e1ce-fe0e-2f72-6fd488a00a3d@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).