unexpected EOF in read_timeout

Eric Whiting ewhiting at amis.com
Thu Sep 13 02:00:57 EST 2001


Michelle/Tim,

I ocassionally get this message under 2.4.7pre1 -- I just call it a
network error and ignore it, but perhaps there is still a rsync protocol
problem. TCP is pretty good about retry/resend under bad network
conditions. Network hiccups shouldn't really be hitting us this often or
severe, right?

Is the receiving side giving up or hanging up too soon?

One good thing about this error -- at least it isn't hanging forever
like 2.4.6 would often do.

my errors look like this:
rsync: connection to server unexpectedly closed (69872 bytes read so
far)
rsync error: error in rsync protocol data stream (code 12) at io.c(255)

eric



willem wrote:
> 
> tim.conway at philips.com wrote:
> 
> > Michelle:  I get the same sort of results. Solaris 7, rsync 2.4.6, with the nohang patches, or with 2.4.7pre1.  If you trace the execution, you'll probably find i/o errors.  I can't find out what they are, and would expect the kernel to take care of any
> > disk or network errors, leaving me wondering what rsync is choking on.  We've got all the latest patches to Solaris, so i'm pretty sure it's not a case of rsync overstressing the tcp implementation, especially as i bwlimit  the transfer to 1000kbps.
> > I've got 2328543  objects (files, directories, symlinks) in 116473553K, on NAS at each end, reached by NFS.  I have to break my jobs up into smaller chunks, which makes it hard to have it delete things.
> > Anybody else have any ideas?
> >
> > Tim Conway
> > tim.conway at philips.com
> > 303.682.4917
> > Philips Semiconductor - Longmont TC
> > 1880 Industrial Circle, Suite D
> > Longmont, CO 80501
> > Available via SameTime Connect within Philips
> > Available as n9hmg on AIM
> > perl -e 'print pack(nnnnnnnnnnnn, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" '
> > "There are some who call me.... Tim?"
> >
> > Michelle Brownsworth <mdb at primelogic.com>@lists.samba.org on 09/10/2001 06:34:16 PM
> >
> > Sent by:  rsync-admin at lists.samba.org
> >
> > To:     rsync at lists.samba.org
> > cc:      (bcc: Tim Conway/LMT/SC/PHILIPS)
> > Subject:  RE: unexpected EOF in read_timeout
> > Classification:
> >
> > Sadly, I don't seem to be having any better luck with 2.4.7pre1:
> >
> > su-2.05# ./rsync_nova.sh
> > receiving file list ... done
> > wrote 16 bytes  read 6620 bytes  13272.00 bytes/sec
> > total size is 1309032  speedup is 197.26
> > receiving file list ... done
> > wrote 16 bytes  read 4458 bytes  2982.67 bytes/sec
> > total size is 6037628  speedup is 1349.49
> > receiving file list ... done
> > wrote 16 bytes  read 450 bytes  932.00 bytes/sec
> > total size is 34693  speedup is 74.45
> > receiving file list ... done
> > mysql/kendall/car.MYD
> > Connection to nova closed by remote host.
> > rsync: connection to server unexpectedly closed (26372 bytes read so far)
> > rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229)
> > rsync error: received SIGUSR1 or SIGINT (code 20) at main.c(693)
> >
> > .\\ichelle
> > ---------------------
> > Michelle Brownsworth
> > System Administrator
> > PrimeLogic Communications
> > http://www.primelogic.com
> 
> sorry to get your hops up but I've no Ideas
> but I'm wondering how you limit your band width use uther solaris
> I wan't to do that for an ftp connection. can you help me with that?

-- 
__________________________________________________________________
Eric T. Whiting					AMI Semiconductors




More information about the rsync mailing list