Detecting reason for rsync errors
Nico -telmich- Schottelius
nico-rsync at schottelius.org
Mon Nov 19 10:01:24 GMT 2007
I'm doing a middle scale backup job using ccollect , which uses
rsyn, with about 50 servers, each about 1-10 GiB changes per day and have
some problems, that servers do not finish their backup completly:
[host1.backup] Read from remote host host1.backup: Connection reset by peer
[host1.backup] rsync: connection unexpectedly closed (41306592 bytes received so far) [receiver]
[host1.backup] rsync error: error in rsync protocol data stream (code 12) at io.c(458) [receiver=2.6.9]
[host1.backup] rsync: connection unexpectedly closed (21302116 bytes received so far) [generator]
[host1.backup] rsync error: unexplained error (code 255) at io.c(458) [generator=2.6.9]
[host1.backup] 2007-11-19-06:59:24: Finished backup (rsync return code: 255).
How can I debug best why the remote server, still running, seems to close the
Think about Free and Open Source Software (FOSS).
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/rsync/attachments/20071119/110e2812/attachment.bin
More information about the rsync