That error message can be caused by anything which causes the remote side
to go away, so it's not very helpful. The server's log file may have more
information. It is possible that you're running out of RAM as is
susggested in that FAQ-O-Matic thread; rsync uses up some memory for every
file in
Other things :
client disk not full :
/dev/hdb2 29412000 16321084 11596872 58% /backup
I also had RAM to client : 128MB => 256 MB on an intel celeron 600Mhz.
This error isn't due to a network error 'cause this happened again and again
each night ...
The rsync client is running vi
> On Thu, 6 Sep 2001 13:29:59 -0700, Michelle Brownsworth <[EMAIL PROTECTED]>
>said:
Michelle> Perhaps someone can shed some light on the problem I'm
Michelle> having using rsync 2.4.6. I'm getting the following error:
Michelle> Connection to nova closed by remote host. unexpe
h <[EMAIL PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM
> >
> > Sent by: [EMAIL PROTECTED]
> >
> > To: [EMAIL PROTECTED]
> > cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
> > Subject: RE: unexpected EOF in read_timeout
> > Classification:
&g
680,26721,25451,25970), ".\n" '
> "There are some who call me Tim?"
>
> Michelle Brownsworth <[EMAIL PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM
>
> Sent by: [EMAIL PROTECTED]
>
> To: [EMAIL PROTECTED]
> cc: (bcc: Tim Conw
PROTECTED]>@lists.samba.org on 09/10/2001 06:34:16 PM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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#
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
I had the same error this is what fixed it for me
/usr/bin/rsync -avc --stats --timeout=0 \ Hostname:/source/
/TargetOnLocalHost
Note the --timeout and you can also speed the process
up by dropping the c from the -avc.
Hope this helps
Dale
--- Wileczek_Mickaël <[EMAIL PROTECTED]>
wrote:
>
On Wed, May 30, 2001 at 02:05:33AM -0500, Phil Howard wrote:
> > I'm a novice at rsync, so I can't tell you all the details, but, in
> > general, the "unexpected EOF in read_timeout" (usually) means that
> > something not so good happened on the server side. On what server I was
> > connecting to
Thank you very much this is a very plausiable cause.
It is a very large filesystem. thanks again.
--- Alberto Accomazzi <[EMAIL PROTECTED]> wrote:
>
> The "unexpected EOF in read_timeout" can happen for a
> variety of reasons,
> but it typically shows up when you have deadlock (no
> bytes sent
1 09:22 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: unexpected EOF in read_timeout
The "unexpected EOF in read_timeout" can happen for a variety of reasons,
but it typically shows up when you have deadlock (no bytes sent across
the wire, which could happen as a result
The "unexpected EOF in read_timeout" can happen for a variety of reasons,
but it typically shows up when you have deadlock (no bytes sent across
the wire, which could happen as a result of ssh blocking for instance)
or a very large filesystem being syncronized (which could happen if the
receiv
Randy Kramer wrote:
> I'm a novice at rsync, so I can't tell you all the details, but, in
> general, the "unexpected EOF in read_timeout" (usually) means that
> something not so good happened on the server side. On what server I was
> connecting to, I believe that the preprocessing by the server
I agree. I am going to check the aix ulimit
params as it is a stock box and no mods have
been made yet.
thanks
Dale
--- Michael <[EMAIL PROTECTED]> wrote:
> > Dale Phillips wrote:
> >
> > > I am trying to rsync a rather large amount of
> > > data. (i.e. clone a box) - What causes the
> > >
I think you are correct at first blush
dropping the -c seems to help.
I am also going to check the aix "limits"
params.
Thanks
Dale
--- Randy Kramer <[EMAIL PROTECTED]> wrote:
> I'm a novice at rsync, so I can't tell you all the
> details, but, in
> general, the "unexpected EOF in read_timeout"
I'm a novice at rsync, so I can't tell you all the details, but, in
general, the "unexpected EOF in read_timeout" (usually) means that
something not so good happened on the server side. On what server I was
connecting to, I believe that the preprocessing by the server made some
watchdog on the se
> Dale Phillips wrote:
>
> > I am trying to rsync a rather large amount of
> > data. (i.e. clone a box) - What causes the
> >
> > unexpected EOF in read_timeout?
>
> I get these. Apparently it is ssh. Are you running this through
> ssh?
It has nothing to do with ssh. I use rsync with and wi
No. I am using aix 4.3 and rsh. I am wondering
if it is some sort of a network glitch.
Dale
--- Phil Howard <[EMAIL PROTECTED]> wrote:
> Dale Phillips wrote:
>
> > I am trying to rsync a rather large amount of
> > data. (i.e. clone a box) - What causes the
> >
> > unexpected EOF in read_tim
Dale Phillips wrote:
> I am trying to rsync a rather large amount of
> data. (i.e. clone a box) - What causes the
>
> unexpected EOF in read_timeout?
I get these. Apparently it is ssh. Are you running this through ssh?
--
-
|
> Check the log file of the rsync server. A number of error messages
> are not reported to the client (mostly for security reasons,
> although some of them may not actually be a security risk).
>
> - Dave Dykstra
>
These are public servers, I have no access to that information.
sigh..
[
On Mon, May 07, 2001 at 05:11:23PM -0800, Michael wrote:
> In reading through the archives, I've seen this topic come up several
> times, but no real solutions. I posted the question on the
> FAQ-O-MATIC, then realized I should have posted here first.
>
>When mirroring a large tree from
21 matches
Mail list logo
