I made a bash script doing this in parallel, checks how many rsyncs are
running and then starts another 'concurrent one'. My parallel sessions
are against different servers. I doubt if it would make any sense doing
multiple sessions between the same two hosts. My single rsync sessions
was alre
; Also note that it flattens the remote host's mount tree into a single
>> filesystem - so things like /proc look like they are in the same
>> filesystem as /. This can lead to backing up /proc's contents (many
>> pseudofiles), if you don't exclude it
; filesystem as /. This can lead to backing up /proc's contents (many
> pseudofiles), if you don't exclude it, even if you use rsync's -x
> option.
>
> On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync
> wrote:
>>
>> I still stuck with these errors
&g
I still stuck with these errors
packet_write_wait: Connection to 192.168.10.43 port 22: Broken pipe
rsync: connection unexpectedly closed (534132435 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(605)
[receiver=3.0.9]
rsync: connection unexp
ct(1, [0], [], NULL, {60, 0}) = 0
(Timeout)
>From man 2 select:
int select(int nfds, fd_set *readfds, fd_set *writefds, fd_set
*exceptfds, struct timeval *timeout);
So, it is waiting for file descriptor #1 to become available with a 60
second timeout which it is hitting.
Use lsof to find
I have been having broken pipe messages for a while. I think since a
network architecture change. But I am not sure because I have not been
monitoring the errors closely before. I added this
(https://rsync.samba.org/issues.html) rsync-debug.sh script with strace
of 100. But I have no idea how
