rsync - Sep 2003 - rsync 2.5.6 still hangs

Hi,
we have two Linux systems (2.4.21 and 2.2.19) with rsync 2.5.6
The 2.4.21 system does backups via cron by rsync to the 2.2.19
system. 

Via cron rsync always exits with (it is called with --timeout=60)
----------
rsync error: timeout in data send/receive (code 30) at io.c(103)
----------

Or with -vvvv
----------
make_file(6,tex/alt/12.3/share/texmf/tex/latex/base/omxcmex.fd)
io timeout after 60 seconds - exiting
_exit_cleanup(code=30, file=io.c, line=103): entered
rsync error: timeout in data send/receive (code 30) at io.c(103)
_exit_cleanup(code=30, file=io.c, line=103): about to call exit(30)
----------

The file varies.

Interestingly this does not happen when rsync is called
interactively. %-{

Any idea how to avoid this?

Thanks in advance
        Martin
-- 
               Martin Schr?der, MS@ArtCom-GmbH.DE
     ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany
          Voice +49 421 20419-44 / Fax +49 421 20419-10

On Tue, Sep 23, 2003 at 11:18:13AM +0200, Martin Schr?der
wrote:
> Hi,
> we have two Linux systems (2.4.21 and 2.2.19) with rsync 2.5.6
> The 2.4.21 system does backups via cron by rsync to the 2.2.19
> system. 
> 
> Via cron rsync always exits with (it is called with --timeout=60)
> ----------
> rsync error: timeout in data send/receive (code 30) at io.c(103)
> ----------
> 
> Or with -vvvv
> ----------
> make_file(6,tex/alt/12.3/share/texmf/tex/latex/base/omxcmex.fd)
> io timeout after 60 seconds - exiting
> _exit_cleanup(code=30, file=io.c, line=103): entered
> rsync error: timeout in data send/receive (code 30) at io.c(103)
> _exit_cleanup(code=30, file=io.c, line=103): about to call exit(30)
> ----------
> 
> The file varies.
> 
> Interestingly this does not happen when rsync is called
> interactively. %-{
> 
> Any idea how to avoid this?
When there is a difference in behaviour between interactive
and cron it will be caused by a difference in the
environment.  Often PATH, sometimes "LD_*", sometimes
something else.

Also, use of more v than -vv can itself cause problems.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

rsync: writefd_unbuffered failed to write 1 bytes: phase "unknown":
Connection timed out
rsync error: error in rsync protocol data stream (code 12) at io.c(515)

Any idea regarding this error?  We sync a number of machines, and one
consistently has this error every night.  If I exclude the file that the error
occurs on, it will go past and fail on another file.  One large file it failed
on over and over.

The connection is over a vpn, but we always can get through and are using
bwlimit to throttle down to 15k.  Disk space is good on both sides, running as
root (uid 0 on the server side), versions 2.5.6 protocol 26 on both sides. 
Rsync will hang, pings still go through and we can still ssh into the sending
server.  Both servers are running Linux.

Thanks for any suggestions!

Ed