Hi Libor!
Thanks for your hint!
In fact using rsync via ssh as workaround *does work for me*, too.
This indeed adds an extra performance penalty for the SSH tunneling, but
in my final setup SSH will be required anyways.
In fact this issue seems to occur mainly with slow rsync servers like
N
Hello,
i was dealing with same thing , I coudln't find a sollution using rsyncd.
Using rsync+ssh did the trick ...
Problem was (probably) with slow NAS, taking ages to compute (initial?)
checksums of target file.
When using --progress or --verbose, it was just sitting there without output,
but s
I can't believe it -- but I DO fiddle around with _wireshark_ to get my
_backup_ done. Strange age of the 21th century.
Ok - here is what I was able to observe: At first everything seems to be
fine. After handshake the rsyncd is continuously sending every 1.7s
packets to the client which the c
-boun...@lists.samba.org] On
Behalf Of Justin T Pryzby
Sent: Friday, October 12, 2012 3:58 PM
To: rsync@lists.samba.org
Subject: Re: Problem rsyncing 450GB file to my NAS: 'connection unexpectedly
closed'
You can tcpdump it to see which side is closing the connection. My
understanding is that &quo
You can tcpdump it to see which side is closing the connection. My
understanding is that "the network" isn't timing out, but one end of
the rsync, due to the other end doing slow things at various points in
the connection. In the immediate case, one side is probably timing
out while the other sid
Damn! Just in the moment I clicked send it aborted again.
This is the tail of my rsyncd.log:
2012/10/12 19:36:06 [7325] chunk[261276] offset=34245967872 len=131072
sum1=db0593fa
2012/10/12 19:36:06 [7325] [receiver] _exit_cleanup(code=30, file=io.c,
line=137): entered
2012/10/12 19:36:06 [7325]
Wow: Thanks for your fast responses, Justin and Karl!
Yet the NAS is still located in my home network. So the network
connection shouldn't be the problem.
The pointer to the --inplace argument was really helpful. This is what I
really wanted in this particular use case.
I also tried to enab
On 10/12/2012 01:06:03 PM, Justin T Pryzby wrote:
> It sounds like a daemon may be timing out; is there a timeout
> specified in rsyncd.conf? Is there a remote logfile with any useful
> content?
I've gotten a 12 error code when a lame firewall broke the connection.
Karl
Free Software: "You d
Not sure, but some ideas:
-P means to retain partial files, and doesn't have anything to do with
/tmp; I wonder if you mean --inplace (not sure)?
It sounds like a daemon may be timing out; is there a timeout
specified in rsyncd.conf? Is there a remote logfile with any useful
content?
Justin
On
