rsync-2.5.5 hangs in client-server mode

[tim.conway at philips.com]

Well, Robert, at least you're to a consistent state from which maybe the 
more capable people on this list may be able to help you.  I'm ccing the 
list, as I don't see anything I can help with.  You might try it again 
with -vvv on the client side, to generate more detail.   As it looks like 
it's dying in connection setup, the output shouldn't be cluttered with a 
mass of transfer detail.

Tim Conway
conwayDOTtimATphilipsDOTcomREVERSETHENAMEORDER
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me.... Tim?"




Robert Brooks <rbrooks at hod.aarg.net>
09/18/2002 10:07 AM

 
        To:     Tim Conway/LMT/SC/PHILIPS at AMEC
        cc: 
        Subject:        rsync-2.5.5 hangs in client-server mode
        Classification: 




> Such behaviour has been seen.  In some iterations of rsync, running from
> cron, on some systems, it would detect STDIO as a socket and try to run 
as
> a daemon.  I don't know when that was, or what platforms, but your 
version
> is way downlevel.  There are a lot of reasons that the current version 
is
> 2.5.5, and reliablilty issues are among them.  See how it looks with 
BOTH
> ENDS running a current version of the utility.
>
> Good luck.

Thank you for your reply to my earlier note about
rsync-2.4.6-3 on Red Hat 7.1.

I took your advice and installed rsync-2.5.5 on
all three systems, taking care to be sure that
the older versions were actually replaced.

Unfortunately, the client-server setup still hangs,
but there were differences:

  1 - The error message is now two lines long:

        io timeout after 60 seconds - exiting
        rsync error: timeout in data send/receive (code 30) at
io.c(85)

  2 - There is now one line of output in the file
      where  stdout  is redirected:

        opening tcp connection to backbone.byron.home port 873

  3 - On the server side, there are now two lines
      entered in  rsyncd.log  (the log file):

        2002/09/18 09:12:25 [1365] rsync: connection unexpectedly
closed (22 bytes read so far)
        2002/09/18 09:12:25 [1365] rsync error: error in rsync
protocol data stream (code 12) at io.c(150)

Here is the output from the command  rsync --version:

  rsync  version 2.5.5  protocol version 26
  Copyright (C) 1996-2002 by Andrew Tridgell and others
  <http://rsync.samba.org/>
  Capabilities: 64-bit files, socketpairs, hard links, symlinks,
batchfiles,
                IPv6, 64-bit system inums, 64-bit internal inums

  rsync comes with ABSOLUTELY NO WARRANTY.  This is free software,
and you
  are welcome to redistribute it under certain conditions.  See the
GNU
  General Public Licence for details.

As before, after the timeout, I was able to run the script
from the root console without any problems.  The log
created on the client side was greatly enhanced, a very
nice improvement.