- you are using W10 (while I am using W7 - rsync works at my place)
- Current System Time: Sat Mar 16 11:44:27 2019
- Windows 10 Home Ver 10.0 Build 17134
- you are using the 64-bits version of Cygwin (root = c:\cygwin64)
- Cygwin DLL version info: DLL version: 3.0.2
- rsync: version: 3.1.2-1
- librsync2: 1.0.0-1 (resulting in bin/cygrsync-2.dll)
(not installed at my place)
Your PATH definition is exceptionally long ...
- it contains e:\Cywin64\bin twice
- it contains a multitude of "bins", irrelevant to Cygwin
Finding the cause of your problem is an exercise in reducing your
environment to the absolute minimum, required to execute rsync.
I would suggest to (temporarily):
- uninstall librsync2 (it should not interfere w/ rsync, but it
is also not required)
- limit your PATH definition to e:\cygwin64
- i.e. export PATH=/usr/bin, if you are using bash
and run, rsync -vvv <some file> <some directory> again, and show
us the output.
Do not use the arguments that you used previously; create a new
file and a new directory to 'copy' to.
Remember, finding the cause of a problem, is first and foremost
about excluding any factor (you did not think of).
On 2019-03-16 13:45, Houder wrote:
> On Sat, 16 Mar 2019 03:49:27, jwang wrote:
>> rsync /tmp/test.log /cygdrive/c/temp/
>> rsync: pipe: Connection timed out (116)
>> rsync error: error in IPC code (code 14) at pipe.c(122) [sender=3.1.2]
> Your PATH definition is exceptionally long ...
> - it contains e:\Cywin64\bin twice
> - it contains a multitude of "bins", irrelevant to Cygwin
> Finding the cause of your problem is an exercise in reducing your
> environment to the absolute minimum, required to execute rsync.
> I would suggest to (temporarily):
> - uninstall librsync2 (it should not interfere w/ rsync, but it
> is also not required)
> - limit your PATH definition to e:\cygwin64
> - i.e. export PATH=/usr/bin, if you are using bash
Sorry, that should be:
(cygdrive, or whatever your prefix is)
as rsync is also dependent on .dll's from the Windows bin ...
> rsync -vvv /tmp/test2.log /tmp/tmp/
> rsync: pipe: Connection timed out (116)
> rsync error: error in IPC code (code 14) at pipe.c(122) [sender=3.1.2]
> [sender] _exit_cleanup(code=14, file=pipe.c, line=122): about to call
> rsync used to work perfectly and still do on my other Windows 10 boxes.
> Just one box has problem.
> About PATH - i think it is defined by cygwin /etc/profile and my other boxes
> also long PATH :)
But this is NOT about "what used to work", it is about what is NOT working NOW
on this specific machine ...
It is also not relevant (to a large extent) that rsync is working on the other
W10 boxes you own ...
The main issue (to us) here is: Is it Cygwin that is causing the problem? Said
differently, if it is not Cygwin, than we cannot help you.
In that case, you will have to rely on your own capabilities (and the support,
if any, given by Microsoft).
So, the reason I am asking to reduce your PATH definition is to exclude Cygwin
as the cause of your recent problem on this specific box.
Excluding, excluding ... that is the main theme here!
> Sorry, that should be:
> export PATH=/usr/bin:/cygdrive/c/Windows/System32
The proper way to isolate Cygwin from Windows to the extent possible
is to set "CYGWIN_NOWINPATH=yes" in the control panel in either the system
or user variables so it is in the environment when you start the first
Cygwin process (which should be a login shell). I recommend that as the
default setting. If it turns out you need a specific Windows path later
on, you can add it as needed from ORIGINAL_PATH (provided you use a
> (cygdrive, or whatever your prefix is)
Here, too: this should be set independently of whatever the cygdrive
prefix is, so "/proc/cygdrive/c…"
On 3/17/2019 4:15 AM, jwang wrote:
> update: rclone worked on my troubled Windows 10 box.
> not sure if rclone can do sync via ssh yet, nor if it can do sync
> incrementally yet as rsync can for both
> thank you all for your help
Well, if you want a Windows native rsync, you can look into
acrosync. (cwrsync, on the other hand, is just a repackaging
or cygwin and cygwin's rsync.)
But given the effort invested so far, it might be reasonable
to try to find why rsync broke on your one particular machine.
Perhaps some BLODA? (See the cygwin acronyms for a definition!)
Basically some interfering program or setting? Multiple
installations of cygwin? Lots of things can cause it, and the
folks on this list have truly been trying to be helpful -- but
(as said before) we don't have your box, so there is testing
and narrowing down of possibilities that you have to do ...
Whatever is breaking rsync could well affect other programs