Nitin Agarwal [EMAIL PROTECTED] wrote:
Dear Mr. Rusty,
We have not defined the timeout parameter in the configuration file. That means no
timeout (by
default). So, that cant be the solution.
Further, I checked on the net (in the mailing lists), many are complaining the same
error, but
none
]: unexpected EOF in read_timeout (was Re[2]: [Fwd: Re:
meaning of IO
Error: skipping the delete]])
Classification:
Nitin Agarwal [EMAIL PROTECTED] wrote:
Dear Mr. Rusty,
We have not defined the timeout parameter in the configuration file.
That means no timeout (by
default). So
,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
.\n '
There are some who call me Tim?
Dave Dykstra [EMAIL PROTECTED]
02/13/2002 12:20 PM
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc: [EMAIL PROTECTED]
Subject:Re: Re[2]: unexpected EOF in read_timeout (was Re[2
this :
read error: Connection reset by peer
unexpected EOF in read_timeout
I try rsync 2.4.5, 2.4.6 and 2.5.1 and always the same thing.
Both client and server are running linux redhat.
I don't know what to do now :(
Thanks
David
, February 01, 2002 9:38 AM
Subject: unexpected EOF in read_timeout
I've got this when i backup my server ( like 3GB and lots of small
files ).
i've read this :
http://rsync.samba.org/rsync/fom-serve/cache/73.html.
i launch rsync like this :
rsync -avrpogtzH --rsync-path=/usr/local/bin/rsync
: unexpected EOF in read_timeout
I've got this when i backup my server ( like 3GB and lots of small
files ).
i've read this :
http://rsync.samba.org/rsync/fom-serve/cache/73.html.
i launch rsync like this :
rsync -avrpogtzH --rsync-path=/usr/local/bin/rsync --timeout=0
IP_SERVER::cgi-bin
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. unexpected EOF
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# ./rsync_nova.sh
receiving file list ... done
wrote 16 bytes read 6620 bytes
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 Conway/LMT/SC/PHILIPS)
Subject: RE: unexpected EOF in read_timeout
Classification:
Sadly, I don't seem
! unexpected EOF in read_timeout ?
Example of a cron job email:
***
Date: Wed, 25 Jul 2001 01:00:01 +0200
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron root@it97 test -x /usr/lib/cron/run-crons
/usr/lib/cron/run-crons
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: PATH=/usr/bin:/usr
am trying to rsync 2Go file systems with lots of tiny
file thru a low link
Aproximatively 2 hours after the beginning, the rsync
process stops with the
error 'unexpected EOF in read_timeout'
leaving rsh(rsync) process on the distant machine.
I've seen such problem several times
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
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 of ssh blocking
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 across
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, I
Hello,
I am trying to rsync a rather large amount of
data. (i.e. clone a box) - What causes the
unexpected EOF in read_timeout?
thanks in advance
Dale
__
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http
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
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_timeout?
I
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
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
without ssh and
find that I get the unexpected EOF in read_timeout? from
public
sites that use the newer daemon. This is just
an rsync server the error
unexpected EOF in read_timeout
unexpected EOF in read_timeout
occurs and the session terminates. This error repeats over and
over resulting in the mirror process never completing. This is
also repeatable on several public servers
snip
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..
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 an rsync server the error
unexpected EOF in read_timeout
Hi all,
I'm new to the mailing list.I run into troubles trying to sync servers with
millions of files ... did anyone had any previous experience on this subject
?
In most cases, it ends with something like : "unexpected EOF in
read_timeout".
The servers I'm trying to sync have betwe
I am trying to pull a directory from a remote site. When I type in the
command rsync -avz foo:dir/subdir/ /home/subdir in the csh I get the
following error:
remshd: Login incorrect.
unexpected EOF in read_timeout
Is this due to some error in the systems configurations or do I need to
have ssh
/subdir in the csh I get the
following error:
remshd: Login incorrect.
unexpected EOF in read_timeout
Is this due to some error in the systems configurations or do I need to
have ssh to run this? When I use rsync locally, it works fine from one
machine to another. I am new to rsync
Is a password required? Your error message indicates that:
remshd: Login incorrect.
unexpected EOF in read_timeout
Login is incorrect, which implies that rsh isn't working as rsync expects
it to: without a password.
--
Sean Berry
that:
remshd: Login incorrect.
unexpected EOF in read_timeout
Login is incorrect, which implies that rsh isn't working as rsync expects
it to: without a password.
--
Sean BerryRentals.com IT
(650) 622 2641 work
for a password and a login. How do I run rsync from the
command line with a login and a password?
Thank you.
berry wrote:
Is a password required? Your error message indicates that:
remshd: Login incorrect.
unexpected EOF in read_timeout
Login is incorrect, which implies
2000-12-13-16:25:05 Nancy Pham:
When I rsh to the remote site, a login and a password is required. But when I run
rsync, I do not get prompted for a password and a login. How do I run rsync from the
command line with a login and a password?
Unless you can find you --- or build, perhaps using
30 matches
Mail list logo