Your message dated Mon, 4 Jan 2016 10:52:45 +0100
with message-id <[email protected]>
and subject line Re: Bug#622855: rsync: connection unexpectedly closed
has caused the Debian Bug report #622855,
regarding rsync: connection unexpectedly closed
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.)
--
622855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622855
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsync
Version: 3.0.7-2
Severity: normal
The connection closes unexpectedly. The computer on which rsync is called
brakes the hole network connection.
A restart is neccessary.
Following information is given:
Write failed: Broken pipe
rsync: connection unexpectedly closed (2183331 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[receiver=3.0.7]
rsync: connection unexpectedly closed (1984989 bytes received so far)
[generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601)
[generator=3.0.7]
After this the connection is closed.
This behaviour happends after an upgrade to squeeze.
Because we are using the comupter as an backup system over our local networt,
the fix of
this behaviour is important for us.
Thanks in advance.
Norbert Schulz
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rsync depends on:
ii base-files 6.0squeeze1 Debian base system miscellaneous f
ii libacl1 2.2.49-4 Access control list shared library
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii libpopt0 1.16-1 lib for parsing cmdline parameters
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:5.5p1-6 secure shell (SSH) client, for sec
ii openssh-server 1:5.5p1-6 secure shell (SSH) server, for sec
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon 04 Jan 2016, Norbert Schulz wrote:
> The system is updated to wheezy with rsync 3.0.9-4. There are no problems
> with this version of rsync. Everything works fine.
Thanks for the feedback.
I'm now closing this bug report.
thanks,
Paul
> Am 30.12.2015 12:05, schrieb Paul Slootman:
> >I'm working through the old list of bug reports, so checking on the
> >status here...
> >
> >On Fri 15 Apr 2011, Norbert Schulz wrote:
> >
> >>Package: rsync
> >>Version: 3.0.7-2
> >>Severity: normal
> >>
> >>The connection closes unexpectedly. The computer on which rsync is
> >>called brakes the hole network connection.
> >>A restart is neccessary.
> >>
> >>Following information is given:
> >>Write failed: Broken pipe
> >>rsync: connection unexpectedly closed (2183331 bytes received so far)
> >>[receiver]
> >>rsync error: error in rsync protocol data stream (code 12) at io.c(601)
> >>[receiver=3.0.7]
> >>rsync: connection unexpectedly closed (1984989 bytes received so far)
> >>[generator]
> >>rsync error: error in rsync protocol data stream (code 12) at io.c(601)
> >>[generator=3.0.7]
> >>
> >>After this the connection is closed.
> >>
> >>This behaviour happends after an upgrade to squeeze.
> >
> >>Here are some more information that might be helpfull.
> >>
> >>rsync is called with the following options:
> >>
> >>rsync -avz --numeric-ids -e ssh --delete --delete-excluded \
> >> --exclude-from="$EXCLUDES" \
> >> $SERVER:/ $DATA_PATH/$SERVER/daily.0
> >
> >There were issues when using compression.
> >These seem to have been resolved with rsync 3.1.1.
> >
> >Can you confirm whether you still have these problems with 3.1.1, or if
> >disabling compression works?
> >
> >
> >Thanks,
> >Paul
--- End Message ---
