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
On Wed, May 30, 2001 at 10:50:37AM +1000, Greg Burley <[EMAIL PROTECTED]> wrote:
| have a look at errorcode.h in the distribution source of 2.4.6
| 20 is commented as status returned when sent SIGUSR1 or SIGINT -- the later
| being the most useful clue to your problem (you would probably know if
Ken,
have a look at errorcode.h in the distribution source of 2.4.6
20 is commented as status returned when sent SIGUSR1 or SIGINT -- the later
being the most useful clue to your problem (you would probably know if you
sent SIGUSR1 to your running rsync.
Greg
> -Original Message-
> Fro
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?
--
-
|
I have a few web servers running Redhat 6.2 which synchronize via two
scripts to an rsync server. They run every 5 and 15 minutes through a cron
job. For many months this worked great until a few days ago when it just
stopped working. If I run these scripts manually it works fine, which lead
You could try errcode.h:
/* error codes returned by rsync */
#define RERR_SYNTAX 1 /* syntax or usage error */
#define RERR_PROTOCOL 2 /* protocol incompatibility */
#define RERR_FILESELECT 3 /* errors selecting input/output files, dirs
*/
#define RERR_UNSUPPORTED 4
Hi,
Where can I find an explanation of rsync's exit codes? I've checked the
man pages and the web site but don't see anything. Specifically, I'm
looking for an explanation of exit status 20?
Thanks,
Ken
(pls reply to me directly, I'm not currently subscribe to the mailing
list. Thanks)
--
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://auctions.ya
Dave Dykstra wrote:
> On Fri, May 25, 2001 at 02:19:59PM -0500, Dave Dykstra wrote:
> ...
> > Use the -W option to disable the rsync algorithm. We really ought to make
> > that the default when both the source and destination are local.
>
> I went ahead and submitted a change to the rsync CVS t
>
> I don't have any experience with BSDI, but what's the full command line of
> the rsync command you're trying to run?
>
/usr/local/bin/rsync -vrlptgozx --partial --delete --force --rsync-path=/usr/l
ocal/bin/rsync --exclude='stats/' --exclude='archive/' --include='*/' --blocking
-io /usr/
On Sun, May 27, 2001 at 03:38:10PM -0400, Tuc wrote:
> Hi,
>
> We recently upgraded a machine from BSDI 4.0.1 to 4.2 . At the same
> time, we went from rsync 2.3.1 to 2.4.6 . This has proved problematic.
>
> I attempted to backdown the new 4.2 machine to 2.3.1 to match the
> receivi
On Fri, May 25, 2001 at 02:19:59PM -0500, Dave Dykstra wrote:
...
> Use the -W option to disable the rsync algorithm. We really ought to make
> that the default when both the source and destination are local.
I went ahead and submitted a change to the rsync CVS to automatically turn
on -W when t
On Fri, May 25, 2001 at 02:52:24PM -0700, Simison, Matthew wrote:
> I am getting this error,
>
> read error: Connection reset by peer
>
> Why is this happening?
>
> Solaris 7 to Solaris 7
> rsync v-2.4.1
>
> rsync -a -z --address ${IP} /data/test user@${hostIP}::root/data
>
> Matt
First, be
18 matches
Mail list logo
