Displaying 3 results from an estimated 3 matches for "ddp222".
Did you mean:
d2222
2016 Oct 13
5
rsync: connection unexpectedly closed
On Wed, 2016-10-12 at 08:36 +0200, Paul Slootman wrote:
> As always it's best to first upgrade to the current version (3.1.3)
> if at all possible, as there's always the chance that the cause of
> your problems has already been fixed.
Good call, but I believe I may have ruled this out. I didn't upgrade to
3.1.3, but both sides are running 3.1.1 protocol version 31 now. Same
2016 Oct 14
0
rsync: connection unexpectedly closed
I don't remember whether or not you said you were running rsync over ssh
but if you are you can also debug the ssh layer. You can even do it at
both ends....
On the server run a debugging sshd on an alternate port with:
/usr/sbin/sshd -dDp222
(note that this will only accept 1 connection, debug to the terminal,
then exit)
then on the client use rsync -e "ssh -vp222" to go verbose and use the
debugging port.
On 10/13/2016 08:05 PM, Kip Warner wrote:
> On Thu, 2016-10-13 at 16:58 -0700, Wayne Davison wrote:
>> No, that...
2016 Oct 16
1
rsync: connection unexpectedly closed
...08 -0400, Kevin Korb wrote:
> I don't remember whether or not you said you were running rsync over
> ssh but if you are you can also debug the ssh layer. You can even do
> it at both ends....
>
> On the server run a debugging sshd on an alternate port with:
> /usr/sbin/sshd -dDp222
> (note that this will only accept 1 connection, debug to the terminal,
> then exit) then on the client use rsync -e "ssh -vp222" to go verbose
> and use the debugging port.
Hey Kevin,
I managed to get a chance to try your suggestion. I noticed something
very interesting. On th...