Hi Yevgeniy,
On 2015-08-22 14:00, Евгений Парфенов wrote:
> I have some problem with rsync.
> I'm trying to commit large files via git-annex-shell but get error:
>
>> rsync: Failed to exec ssh: No such file or directory (2)
>>
> So i try rsync manually and get:
>
>> *protocol version mismatch -- is your shell clean?*
>> (see the rsync man page for an explanation)
>> rsync error: protocol incompatibility (code 2) at
>> /home/lapo/package/rsync-3.0.9
>> -1/src/rsync-3.0.9/compat.c(174) [Receiver=3.0.9]
>>
>
> Output with "-vvvv":
>
>> cmd=<NULL> machine=gitlab.local user=root path=
>> cmd[0]=ssh cmd[1]=-l cmd[2]=root cmd[3]=gitlab.local cmd[4]=rsync
>> cmd[5]=--serve
>> r cmd[6]=-vvvve.Lsf cmd[7]=. cmd[8]=
>> opening connection using: ssh -l root gitlab.local rsync --server
>> -vvvve.Lsf .
>>
>> note: iconv_open("UTF-8", "UTF-8") succeeded.
>> *rsync: Failed to exec ssh: No such file or directory (2)*
>> rsync error: error in IPC code (code 14) at
>> /home/lapo/package/rsync-3.0.9-1/src
>> /rsync-3.0.9/pipe.c(84) [sender=3.0.9]
>> (Client) Protocol versions: remote=1852142427, negotiated=30
>> protocol version mismatch -- is your shell clean?
>> (see the rsync man page for an explanation)
>> [sender] _exit_cleanup(code=2,
>> file=/home/lapo/package/rsync-3.0.9-1/src/rsync-3
>> .0.9/compat.c, line=174): entered
>> rsync error: error in IPC code (code 14) at
>> /home/lapo/package/rsync-3.0.9-1/src
>> /rsync-3.0.9/compat.c(174) [sender=3.0.9]
>> [sender] _exit_cleanup(code=2,
>> file=/home/lapo/package/rsync-3.0.9-1/src/rsync-3
>> .0.9/compat.c, line=174): about to call exit(14)
>>
>
> Seems like rsync can't find ssh while "where" can:
>
>> c:\Git\cmd>where ssh.exe
>> C:\Git\usr\bin\ssh.exe
>>
>
> Git-2.5.0-64-bit.exe
> git-annex 5.20150812
> Windows 7 Pro SP1 6.1.7601
The interesting part is that we do not ship `rsync` with Git for
Windows... That has not changed between 1.x and 2.x...
Having said that, it looks like these error messages come from a Unix
machine (`/home/lapo` is not the usual form of home directories on
Windows). So I guess that your server side is not finding the `ssh`
executable to talk back to the client side's `ssh`.
Ciao,
Johannes