Re: unexpected EOF in read_timeout
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 made some > watchdog on the server side decide that the process was dead -- it then > killed it, and then I got the error message. I never proved this > completely. I posted a while back with this problem and someone answered that the message existed in ssh and not in rsync. I never verified it. But I do know that it started happening when I upgraded to 2.4.6. But I also upgraded ssh around that time, so this was believable. > At the time, because I was new to using rsync, I was using the -c option > to force a full checksum comparison of the two files (because I thought > that the files were not updating because the dates and times matched). > I stopped using the -c option and just made sure the dates and times did > not match and that cured my problem with the "unexpected EOF ..." -- I > believe because the server (and client) spent less time calculating > checksums before starting to exchange data. Unfortunately, I'm not using -c and I do get these problems. The thing is, they occur randomly. I run some mirroing scripts and have coded the scripts to just repeat until a good status comes back, like: while ! rsync ; do echo "oops, let's try that again"; done -- - | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ | -
Re: unexpected EOF in read_timeout
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 > > > > > > 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 a > correlation, for one > set of files > 700mb that I mirror. I can only get them > from one of > about 6 sites. That particular site apparently uses and > old daemon. > > I suspect it is some kind of resource limitation on the > daemon end > that causes the problem when the directory cache get too > big. > > Michael > [EMAIL PROTECTED] > __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Re: unexpected EOF in read_timeout
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" (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 server side decide that the process was > dead -- it then > killed it, and then I got the error message. I never > proved this > completely. > > At the time, because I was new to using rsync, I was > using the -c option > to force a full checksum comparison of the two files > (because I thought > that the files were not updating because the dates and > times matched). > I stopped using the -c option and just made sure the > dates and times did > not match and that cured my problem with the "unexpected > EOF ..." -- I > believe because the server (and client) spent less time > calculating > checksums before starting to exchange data. > > (All this is to the best of my recollection.) > > Hope this helps! > Randy Kramer > > Dale Phillips wrote: > > > > 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 get these. Apparently it is ssh. Are you running > this > > > through ssh? > > > > > > -- > > > > > > - > > > | Phil Howard - KA9WGN | Dallas | > > > http://linuxhomepage.com/ | > > > | [EMAIL PROTECTED] | Texas, USA | > > > http://phil.ipal.org/ | > > > > > > - > > > > __ > > Do You Yahoo!? > > Get personalized email addresses from Yahoo! Mail - > only $35 > > a year! http://personal.mail.yahoo.com/ __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Re: 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 server side decide that the process was dead -- it then killed it, and then I got the error message. I never proved this completely. At the time, because I was new to using rsync, I was using the -c option to force a full checksum comparison of the two files (because I thought that the files were not updating because the dates and times matched). I stopped using the -c option and just made sure the dates and times did not match and that cured my problem with the "unexpected EOF ..." -- I believe because the server (and client) spent less time calculating checksums before starting to exchange data. (All this is to the best of my recollection.) Hope this helps! Randy Kramer Dale Phillips wrote: > > 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 get these. Apparently it is ssh. Are you running this > > through ssh? > > > > -- > > > - > > | Phil Howard - KA9WGN | Dallas | > > http://linuxhomepage.com/ | > > | [EMAIL PROTECTED] | Texas, USA | > > http://phil.ipal.org/ | > > > - > > __ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail - only $35 > a year! http://personal.mail.yahoo.com/
Re: unexpected EOF in read_timeout
> 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 without ssh and find that I get the unexpected EOF in read_timeout? from public sites that use the newer daemon. This is just a correlation, for one set of files > 700mb that I mirror. I can only get them from one of about 6 sites. That particular site apparently uses and old daemon. I suspect it is some kind of resource limitation on the daemon end that causes the problem when the directory cache get too big. Michael [EMAIL PROTECTED]
Re: unexpected EOF in read_timeout
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 get these. Apparently it is ssh. Are you running this > through ssh? > > -- > - > | Phil Howard - KA9WGN | Dallas | > http://linuxhomepage.com/ | > | [EMAIL PROTECTED] | Texas, USA | > http://phil.ipal.org/ | > - __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
Re: rsync exit codes
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 you | sent SIGUSR1 to your running rsync. Hmm. It has long annoyed me that rsync returns exit code 20 after successfully updating the target. (No, I don't send it any signals.) I only get zero if both sides are the same before the sync. I would have expected: - both sides the same - exit zero - both sides different and -n used - non-zero - both sides different, no -n, successful update - zero - both sides different, no -n, unsuccessful update - non-zero This doesn't seem to be the case. -- Cameron Simpson, DoD#743[EMAIL PROTECTED]http://www.zip.com.au/~cs/ The Microsoft manuals, of course, are just a load of self-serving propaganda written by tekkies under the supervision of public relations folks. - David Lloyd-Jones
RE: rsync exit codes
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- > From: Ken Versteeg [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 30 May 2001 4:18 AM > To: [EMAIL PROTECTED] > Subject: rsync exit codes > > > 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) > > -- > > > Ken Versteeg > Berbee > 5520 Research Park Dr. Madison, WI 53711 > [EMAIL PROTECTED] > (608)298.1246 pager:376.6573 cell:212.2556 > Berbee...putting the E in business. >
Re: unexpected EOF in read_timeout
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? -- - | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ | -
rsync stopped synchronizing
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 leads me to believe its a cron problem. But, cron logs report that these scripts execute fine with no errors. Even the rsync server log reports the systems establish a connection just fine. Except for a "cant find /etc/pwd.db - no such file" which has been in the logs for months as well (i just took over this responsibility). I am pretty new to rsync, but i have looked through more logs than I can count with no luck. By the way, lock files do not exist either. I need help to troubleshoot this problem desperately. Thanks, Frank _ Get your FREE download of MSN Explorer at http://explorer.msn.com
RE: rsync exit codes
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 /* requested action not supported */ #define RERR_SOCKETIO 10 /* error in socket IO */ #define RERR_FILEIO 11 /* error in file IO */ #define RERR_STREAMIO 12 /* error in rsync protocol data stream */ #define RERR_MESSAGEIO 13 /* errors with program diagnostics */ #define RERR_IPC14 /* error in IPC code */ #define RERR_SIGNAL 20 /* status returned when sent SIGUSR1, SIGINT */ #define RERR_WAITCHILD 21 /* some error returned by waitpid() */ #define RERR_MALLOC 22 /* error allocating core memory buffers */ #define RERR_TIMEOUT30 /* timeout in data send/receive */ But I do agree it would be nice if the man page documented them. John. -Original Message- From: Ken Versteeg [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 29, 2001 02:18 PM To: [EMAIL PROTECTED] Subject: rsync exit codes 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) -- Ken Versteeg Berbee 5520 Research Park Dr. Madison, WI 53711 [EMAIL PROTECTED] (608)298.1246 pager:376.6573 cell:212.2556 Berbee...putting the E in business.
rsync exit codes
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) -- Ken Versteeg Berbee 5520 Research Park Dr. Madison, WI 53711 [EMAIL PROTECTED] (608)298.1246 pager:376.6573 cell:212.2556 Berbee...putting the E in business.
unexpected EOF in read_timeout
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.yahoo.com/
Re: problems encountered in 2.4.6
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 to automatically turn > on -W when the source and destination are both on the local machine. So how do I revert that on the command line? I've been trying with -W doing my disk to disk backups, and I've had to go back to not using -W. Will -c do that? The reason is the load on the machine gets so high, nothing else can run. This is not CPU load, but rather, buffering/swapping load. CPU load just slows other things down. But buffering/swapping load brings other things to a grinding halt. I suspect Linux's tendency to want to keep everything that anything writes in RAM, even if that means swapping out all other processes, is impacted by this. So I'll need a way to not have the effect of -W to use rsync for disk to disk backups. The fact that rsync loads so much into VM probably makes the problem a bit worse in this case. I saw 1 process at 35M and 2 processes at 70M (total 175M used by rsync, in addition to all the buffered writes). I'm wondering if rsync is even a good choice for disk to disk backup duty. Is there some option I missed that disables pre-loading all the file names into memory? I also tried the --bwlimit option and it had no effect, not even on the usual download syncronizing over a dialup that I do. I could not get it to pace the rate below the dialup speed no matter what I would specify. -- - | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ | -
Re: 2.4.6 Hang on BSDI 4.2/4.0.1
> > 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/home/directory/subdirectory/ [EMAIL PROTECTED]:/usr/home/directory/subdirectory/ > > If you're transferring over SSH, > which version of SSH? > Nope. Tuc/TTSG Internet Services, Inc.
Re: 2.4.6 Hang on BSDI 4.2/4.0.1
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 > receiving 4.0.1's system running 2.3.1 . > > Same problems. > > I upgraded both systems to 2.4.6. It seems to take ALOT LONGER to > run, but seems to run and then freeze. > > On the receiving system, the "ktrace" of the primary pid is : > > 10435 rsyncRET select 0 > 10435 rsyncCALL select(0x2,0,0x804675c,0,0x8046734) > > On the receiving system, the ktrace of the secondary pid is : > > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d8c,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d8c,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d8c,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > 10592 rsyncRET select 0 > 10592 rsyncCALL gettimeofday(0x8047d84,0) > 10592 rsyncRET gettimeofday 0 > 10592 rsyncCALL select(0,0,0,0,0x8047d7c) > > and keeps going and going... > > I ran 2.4.6 with the "--blocking-io" and still no better. > > Any ideas/thoughts? > > Thanks, Tuc/TTSG Internet Services, Inc. I don't have any experience with BSDI, but what's the full command line of the rsync command you're trying to run? If you're transferring over SSH, which version of SSH? - Dave Dykstra
Re: problems encountered in 2.4.6
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 the source and destination are both on the local machine. - Dave Dykstra
Re: reset error
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 sure to upgrade to rsync 2.4.6 as 2.4.1 had some severe
problems. I'm not sure any of them would have affected rsync daemon mode
(that is, using "::") but it definitely affected at least ssh.
Next, as far as I can tell from the rsync man page the --address option
will make no difference unless you're starting up an rsync --daemon. I
wasn't even aware the option existed until now.
Finally, chances are you've got a problem with you rsyncd.conf file on
the target machine, but I can't tell because you didn't post it. Many errors
on daemons do not get passed back to the client, look at the daemon log file
(either syslog or use the 'log file' option). I note that you need to be
extra careful regarding security when writing to a daemon, and that you need
to use the "read only = false" option.
- Dave Dykstra
