From: Wayne Davison <wayne@opencoder.net>
To: Neil Aggarwal <neil@propfinancing.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: rsync gives me error 12
Date: Fri, 25 Mar 2022 15:41:52 -0700 [thread overview]
Message-ID: <CAHSx_SssMd8HZMxXFKZ9PL93CPUeL9jn_8i4FD9NjgdkFHLJJg@mail.gmail.com> (raw)
In-Reply-To: <34a35c898731e4f83f700156bcd57945@mail.gmail.com>
On Fri, Mar 25, 2022 at 10:37 AM Neil Aggarwal wrote:
> I still get an error:
> rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226)
> [Receiver=3.1.3]
> 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]
As the rsync issues & debugging page mentions, you should try forcing
errors to stderr to see if it makes the remote rsync report its error
to you:
--msgs2stderr -M--msgs2stderr
It also mentions an rsync-debug script that you can put on the remote
host and use to get the strace output of what is happening and get a
core dump (if it is dumping core).
https://rsync.samba.org/issues.html
Also, try running the following test command and make sure you see the
word "hi" and nothing else:
echo hi | ssh root@marketing.propfinancing.com cat
..wayne..
next prev parent reply other threads:[~2022-03-25 22:42 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
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 [this message]
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=CAHSx_SssMd8HZMxXFKZ9PL93CPUeL9jn_8i4FD9NjgdkFHLJJg@mail.gmail.com \
--to=wayne@opencoder.net \
--cc=cygwin@cygwin.com \
--cc=neil@propfinancing.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).