Displaying 3 results from an estimated 3 matches for "251382".
Did you mean:
25132
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
......, 57452) = 57452
> 3104 select(4, [3], [], [3], {60, 0}) = 0 (Timeout)
> (repeats above line until client (sender) reports connection timed out)
>
> Sender reports the following until it times out...
>
> ...
> match at 32949141504 last_match=32949141504 j=251382 len=131072 n=0
> 32.95G 96% 83.55MB/s 0:00:12
>
>
>
--
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb Phone: (407) 252-6853
Systems Administrator Internet:
FutureQuest, Inc. Kevin at F...
2016 Oct 16
1
rsync: connection unexpectedly closed
...cleanup
debug1: PAM: cleanup
debug1: PAM: closing session
Sessions still open, not unmounting
debug1: PAM: deleting credentials
...and the client rsync dies...
match at 32949010432 last_match=32949010432 j=251381 len=131072 n=0
match at 32949141504 last_match=32949141504 j=251382 len=131072 n=0
32.95G 96% 74.13MB/s 0:00:14 packet_write_wait: Connection to <snip> port 22223: Broken pipe
rsync: [sender] write error: Broken pipe (32)
rsync error: unexplained error (code 255) at io.c(820) [sender=3.1.1]
[sender] _exit_cleanup(code=10, file...