As a first step, I'd try upgrading to the current OpenSSH (free,
rather than noncommercial), and rsync 2.4.6.
I don't think you have to do anything special to get debugging info.
Just give lots of -v's.
--
Martin
On 11 Dec 2000, Philippe McLean <[EMAIL PROTECTED]> wrote:
> Hi Martin,
>
> version of ssh:
>
> locally:
> ssh: SSH Secure Shell 2.2.0 (non-commercial version) on i686-pc-linux-gnu
>
> remote host:
>
> [root@host8 /root]# ssh -V
> ssh: SSH Version 2.0.13
> [root@host8 /root]#
>
> rsync:
>
> locally:
>
> [philippem@philippem ~/morpheus]$ rsync -v
> rsync version 2.4.1 Copyright Andrew Tridgell and Paul Mackerras
>
> remote:
>
> [root@host8 /root]# rsync -v
> rsync version 2.4.1 Copyright Andrew Tridgell and Paul Mackerras
>
> It doesn't happen all the time. It is intermittent, maybe 1 in 10
> times. One day I saw it very frequently, the next not at all. Here is
> an example of when it happened (I've copied the output from my network
> tool):
>
> [13:31:29] pulling crypt
> [13:31:29] `rsync --verbose --delete --archive --compress -e "ssh -x -l root"
>host8.syslab.freedom.net:/tmp/Morpheus/shadow/crypt/. /tmp/Morpheus/shadow/crypt'
>cwd=/turf/philippem/morpheus
>PATH=/turf2/philippem/builds/mayday_dev/tools/morpheus/bin:/usr/kerberos/bin:/usr/kerberos/bin:/usr/kerberos/bin:/usr/kerberos/bin:/usr/kerberos/bin:/bin:/usr/bin:/usr/bin/X11:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/turf/philippem/bin:/usr/X11R6/bin:/turf/philippem/bin:/usr/X11R6/bin:/turf/philippem/bin
> [13:31:30] receiving file list ... done
> [13:31:30] ./
> [13:31:30] 32403
> [13:31:30] ./
> [13:31:30] wrote 32 bytes read 183 bytes 143.33 bytes/sec
> [13:31:30] total size is 30 speedup is 0.14
> [13:31:30]
> [13:31:30] (WARNING): rsync capriciously returned nonzero exit status `5120'
> [13:31:30] Morpheus waits for you to choose a pill. Red or blue?
> (red/blue) : red
> [13:40:56] <gulp> Red pill swallowed. Excellent choice.
>
> Any ideas? I will build a debug rsync build and try reproducing.
>
>
> Martin Pool writes:
> > Hi Philippe. Thanks for your mail, and sorry for the delay in
> > replying. I'm still down in California on Linuxcare business.
> >
> > On 2 Dec 2000, Philippe McLean <[EMAIL PROTECTED]> wrote:
> >
> > > I encountered a strange behaviour when we started using rsync over
> > > ssh1. Occasionally, when copying from a remote server to a local
> > > machine, rsync would return an exit code of 20 (5120 returned by
> > > waitpid()). This always occurred when no files were transferred. I did
> > > not see this error over ssh2. The transfer seemed to be successful. I
> > > don't have the exact details handy but will do a more thorough
> > > investigatino when I have time.
> >
> > My first question would be about which version you're using. The
> > current one is 2.4.6, and recent 2.3 and 2.4 releases have had some
> > intermittent network bugs. I won't recapitulate them all here, but
> > looking through the archives will tell you more. Are both machines
> > running Linux?
> >
> > As a very simply and kludgy workaround you might want to run rsync
> > from a shell script that loops until it is succesful.
> >
> > If that does not fix up the problems I would like to work with you
> > more to find out what's going wrong. A good place to start is with
> > -vvv trace output, which will tell me more about where the problem
> > occurs.
> >
> > I greatly enjoyed visiting Montreal and Quebec, and meeting all the
> > ZKS people.
> >
> > Best regards,
>
--
Martin Pool, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
PGP signature
