Your message dated Sun, 2 Mar 2008 14:08:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#158170: rsync: hangs or exits with strange errors when
pulling files
has caused the Debian Bug report #158170,
regarding rsync: hangs or exits with strange errors when pulling files
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.)
--
158170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=158170
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: rsync
Version: 2.5.5-0.2
Severity: important
When pulling files from a remote system running Debian, the rsync
process on the Debian side seems to send garbled data or just hang.
Example output from the side trying to pull data:
unexpected tag 62
rsync error: error in rsync protocol data stream (code 12) at ../../io.c(299)
rsync: connection unexpectedly closed (1035 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at ../../io.c(151)
unexpected tag 94
rsync error: error in rsync protocol data stream (code 12) at ../../io.c(299)
rsync: connection unexpectedly closed (1035 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at ../../io.c(151)
or the process will just hang until killed (and when that happens, the
rsync process running on the Debian system never exits and has to be
killed manually; I've waited up to five hours for it to realize that the
other end has gone away).
These errors happen almost every time I attempt to rsync a large tree of
files and happen after only a couple of files or just one file. They
are so severe as to completely prevent rsync from being used as a way to
pull backups to another system.
The other end of the connection (the requesting machine) is running
Solaris, so I at least can't rule out some sort of subtle network byte
order problem.
I strongly suspect this is an upstream bug.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lothlorien 2.4.19 #2 Thu Aug 8 22:52:09 PDT 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages rsync depends on:
ii libc6 2.2.5-9.woody.3 GNU C Library: Shared libraries an
ii libpopt0 1.6.4-2 lib for parsing cmdline parameters
--- End Message ---
--- Begin Message ---
On Thu 02 Aug 2007, Russ Allbery wrote:
>
> I'm pleased to report that with the latest version of rsync, I can no
> longer reproduce the problem that I was having. Previously, I could
> reliably hang rsync by syncing a deeply nested directory structure from
> the remote system to the local system using ssh or rsh as the transport.
> Both now work fine. It looks like whatever had been causing this was
> finally fixed.
>
> Feel free to close this bug.
Oops, left it lying.
Now closing this bug.
FYI, 3.0.0 was released today.
Paul Slootman
--- End Message ---
