Continued rsync failures

Continued rsync failures

[Brent Epp]

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?

Thanks
  - Brent

Re: Continued rsync failures

[Ken Brown]

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

Re: Continued rsync failures

[Marco Atzeri]

On 07.05.2021 18:43, 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?
> 
> Thanks
>   - Brent
> 

please provide the cygcheck.out (see https://cygwin.com/problems.html)

an example of your command and if you are using rsync through
different disks

Regards
Marco

Re: Continued rsync failures

[Brent Epp]

Sorry, my silly mail client doesn't reply to the list by default.

------------------------------

It might be worth noting that these rsync commands run using an 
on-demand script to manage sync jobs.  Generally, it will execute rsync 
once with `--dry-run` to gather a list of files for me to preview:

rsync -avi --progress --no-perms --no-owner --no-group --delete 
--dry-run -s --exclude-from='/cygdrive/d/my/exclusion/file' 
--exclude-from='/cygdrive/d/my/additional/exclusion/file' 
/cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'

trace file: http://cygtestdata.ddnsfree.com/strace.exec1.out

Then it can run rsync a consecutive time:

rsync -avi --progress --no-perms --no-owner --no-group --delete -s 
--exclude-from='/cygdrive/d/my/exclusion/file' 
--exclude-from='/cygdrive/d/my/additional/exclusion/file' 
/cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'

trace file: http://cygtestdata.ddnsfree.com/strace.exec2.out

Thanks
  - Brent

On 2021-05-07 13:09, Ken Brown via Cygwin wrote:
> 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
>

-- 
Brent Epp

E-Mail:    brent@pdc.ca
Web site:  www.pdc.ca/it
Call/Text: (204) 304-9057

Re: Continued rsync failures

[Ken Brown]

[Please don't top post on this list.]

On 5/8/2021 11:03 AM, Brent Epp wrote:
> Sorry, my silly mail client doesn't reply to the list by default.
> 
> ------------------------------
> 
> It might be worth noting that these rsync commands run using an on-demand script 
> to manage sync jobs.  Generally, it will execute rsync once with `--dry-run` to 
> gather a list of files for me to preview:
> 
> rsync -avi --progress --no-perms --no-owner --no-group --delete --dry-run -s 
> --exclude-from='/cygdrive/d/my/exclusion/file' 
> --exclude-from='/cygdrive/d/my/additional/exclusion/file' 
> /cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'
> 
> trace file: http://cygtestdata.ddnsfree.com/strace.exec1.out
> 
> Then it can run rsync a consecutive time:
> 
> rsync -avi --progress --no-perms --no-owner --no-group --delete -s 
> --exclude-from='/cygdrive/d/my/exclusion/file' 
> --exclude-from='/cygdrive/d/my/additional/exclusion/file' 
> /cygdrive/d/path/to/source'/. '/cygdrive/d/path/to/target'
> 
> trace file: http://cygtestdata.ddnsfree.com/strace.exec2.out

After the line "dll_crt0_0: finished dll_crt0_0 initialization" in the trace 
files, you can see several additional DLLs loaded, including several from NVIDIA 
and one from 0patch, and then the program crashes.  This looks to me like BLODA. 
  Can you uninstall or at least disable something from NVIDIA or 0patch to see 
if that fixes the problem?

Ken

Re: Continued rsync failures

[Mark Hansen]

On 5/8/2021 12:36 PM, Ken Brown via Cygwin wrote:
> 
> 
> After the line "dll_crt0_0: finished dll_crt0_0 initialization" in the trace
> files, you can see several additional DLLs loaded, including several from NVIDIA
> and one from 0patch, and then the program crashes.  This looks to me like BLODA.
>    Can you uninstall or at least disable something from NVIDIA or 0patch to see
> if that fixes the problem?
> 
> Ken
> 

Or perhaps make sure you have the latest NVIDIA drivers installed?