mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages1 Wiki Activity Actions

commnet

Browse source
This commit is contained in:
Joey Hess 2015-05-26 10:56:51 -04:00
parent db17e9d329
commit a9583a3ee4
1 changed files with 22 additions and 0 deletions

22
doc/bugs/rsync:_protocol_version_mismatch/comment_5_7d819c3e4af2b8044a52fa6131f36187._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2015-05-26T14:52:11Z"
content="""
The stray recv-key is a good clue. git-annex-shell only allows one upload
of a given file to run at a time. So if you get a transfer stalled out,
it will reject another transfer attempt. This can sometimes happen when eg,
migrating between networks and restarting an upload when the old one is
still running on the server.
However, normally there is an error message "transfer already in progress".
It may be that your rsync is not forwarding that stderr through to display
it, for some reason.
It would probably help if you can run the same git-annex shell command line
on the server, verify that it fails with "transfer already in progress"
when an recvkey of that key is already running. Then you could try sshing
to the server noninteractively and having it run the same git-annex-shell
command, and see if the error makes it through that.
"""]]