From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: rsync gives me error 12
Date: Fri, 25 Mar 2022 13:37:41 +0000 [thread overview]
Message-ID: <20220325133741.6eua7wghywuoibi3@lucy.dinwoodie.org> (raw)
In-Reply-To: <62e2854b675b0437db040419913e4c10@mail.gmail.com>
On Fri, Mar 25, 2022 at 08:25:16AM -0500, Neil Aggarwal wrote:
> > I suspect the `-e ssh` part is the problem here. That's supposed to
> > specify the remote shell, not the method for connecting. What are you
> > attempting to achieve with that?
>
> I am trying to do the sync over an SSH connection.
>
> When I remove it:
> rsync --debug=ALL root@marketing.propfinancing.com:/var/www/svnDumps
> /cygdrive/c/Tmp
>
> I still get the error:
> opening connection using: ssh -l root marketing.propfinancing.com
> rsync --server --sender -e.LsfxCIvu . /var/www/svnDumps (10 args)
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226)
> [sender=3.1.3]
> rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(228)
> [Receiver=3.2.4dev]
> [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call
> exit(12)
Works just fine for me. (Indeed, it works just fine even if I add `-e
ssh`, which surprised me -- clearly I have the wrong impression of what
that `-e` argument is for!)
Looking slightly closer at the logs, this reads to me like the remote
server is closing the connection, so I expect you'll need help from
whoever provides/supports that remote server to work out why it's doing
that.
next prev parent reply other threads:[~2022-03-25 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 5:22 Neil Aggarwal
2022-03-25 9:45 ` Adam Dinwoodie
2022-03-25 13:25 ` Neil Aggarwal
2022-03-25 13:37 ` Adam Dinwoodie [this message]
2022-03-25 13:41 ` Neil Aggarwal
2022-03-25 17:14 ` Neil Aggarwal
2022-03-28 13:27 ` Andrey Repin
2022-03-28 14:06 ` Neil Aggarwal
2022-03-28 14:31 ` Neil Aggarwal
2022-03-25 17:36 ` Neil Aggarwal
2022-03-25 22:41 ` Wayne Davison
2022-03-26 5:01 ` Neil Aggarwal
2022-03-26 17:18 ` Wayne Davison
2022-03-27 4:49 ` Neil Aggarwal
2022-03-27 5:08 ` gs-cygwin.com
2022-03-27 14:32 ` Neil Aggarwal
2022-03-26 11:48 ` Adam Dinwoodie
2022-03-26 15:52 ` Neil Aggarwal
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=20220325133741.6eua7wghywuoibi3@lucy.dinwoodie.org \
--to=adam@dinwoodie.org \
--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).