Your message dated Sun, 15 Apr 2012 18:48:05 +0200
with message-id <[email protected]>
and subject line Re: Bug#525021: Version in Testing looks promising
has caused the Debian Bug report #525021,
regarding rsync connection closes, error in protocol data stream
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
525021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525021
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsync
Version: 3.0.3-2
Severity: important
Hello, I have a simple script that I use to backup my system to an external
usb drive. The script is short and simple, so I'll print it out below.
--------------------------------------
#! /bin/sh
set -e
DESTPARENT=/media/agent/bard64
echo "Test for root user"
if ! test `id -u` -eq 0 ;then
echo "You must be root for this script."
exit 1
fi
echo "Syncing /"
rsync -avHXS --one-file-system --delete / $DESTPARENT/root/
echo "Syncing /freespace"
rsync -avHXS --delete /freespace/ $DESTPARENT/freespace/
-------------------------------------
I run this script manually, from time to time, so it's never called
automatically, i.e. via cron or similar. Often, I get this error:
rsync: connection unexpectedly closed (3759 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(635)
[sender=3.0.3]
I've looked at the rsync FAQ page at http://www.samba.org/rsync/FAQ.html ,
but the "issues and debugging" page seems to indicate that this is likely a
problem with the remote part of the rsync. This leaves me somewhat helpless
in determining the cause of the problems, as rsync is being run locally. I
do understand that there are two processes running when rsync is being run
locally, and I suspect there may be a problem with the communication between
them. So, the problem has nothing to do with running different versions of
rsync between the source and destination.
In the past, I had been wondering if the failure was related to files being
changed during the transfer, but today it stopped in a place where no files
were being modified. I am going to include a snippet of where the transfer
died, and a snippet of where it was resumed on the next run of the script.
<snip>
usr/bin/git-svn
usr/bin/git-unpack-file
usr/bin/git-update-server-info
usr/bin/git-upload-pack
usr/bin/git-var
usr/bin/git-web--browse
usr/bin/gitk
rsync: connection unexpectedly closed (3759 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(635)
[sender=3.0.3]
... The subsequent run of the script starts here
tmp/
<snipped a few tmp files>
usr/bin/
usr/bin/git-annotate => usr/bin/git
usr/bin/git-apply => usr/bin/git
usr/bin/git-archive => usr/bin/git
usr/bin/git-blame => usr/bin/git
usr/bin/git-branch => usr/bin/git
<snip>
The files on the second run are hardlinks.
I had just installed security updates about an hour before I started the rsync
script, so I don't have any reason to believe that these files have been
modified since then.
I don't know if it's relevant, but the destination on the usb drive is an
ecrypted lvm partition. Currently, I don't have enough space anywhere else
to test the script anywhere else.
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rsync depends on:
ii base-files 5lenny2 Debian base system miscellaneous
f
ii libacl1 2.2.47-2 Access control list shared
library
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libpopt0 1.14-4 lib for parsing cmdline
parameters
ii lsb-base 3.2-20 Linux Standard Base 3.2 init
scrip
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:5.1p1-5 secure shell client, an
rlogin/rsh
ii openssh-server 1:5.1p1-5 secure shell server, an rshd
repla
-- no debconf information
--
Thanks:
Joseph Rawson
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
On Sun 15 Apr 2012, Dr. Lars Hanke wrote:
> >Can you confirm you don't have these problems anymore with the current
> >3.0.9-2?
>
> I didn't encounter the problem for years. The machine running the
> script moved to Squeeze about half a year ago and performed quite
> some backups flawlessly.
Great; I'll close this bug report now.
Thanks for your time.
Paul
--- End Message ---
