[Wylug-help] Rsync is broken?

RichardA pingvin at simaric.net
Thu May 3 00:03:55 BST 2007


> RichardA wrote:
> I know this is clutching at straws at this point, but you could try 
> playing around with various Ethernet parameters. e.g. MTU size.

But I haven't changed anything like this since it worked.

>    tcpdump -i eth0 -w trace.pcap host REMOTEHOST
> 
> If you like, please e-mail me the (compressed) trace file, and I'll
> have a look. Up to you - the offer is there.

260MB, 107MB gzipped!

I don't pretend to understand it, but I can tell you that both ends
look alike, apart from the first and last couple of lines.
Here's the end of it. You'd have to unwrap the lines to see anything.

21:40:28.055780 IP cetri.local.40987 > dva.ssh: . 2677697647:2677699095
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055787 IP cetri.local.40987 > dva.ssh: . 2677699095:2677700543
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055795 IP cetri.local.40987 > dva.ssh: . 2677700543:2677701991
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055803 IP cetri.local.40987 > dva.ssh: . 2677701991:2677703439
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055811 IP cetri.local.40987 > dva.ssh: . 2677703439:2677704887
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055819 IP cetri.local.40987 > dva.ssh: . 2677704887:2677706335
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.055826 IP cetri.local.40987 > dva.ssh: . 2677706335:2677707783
(1448) ack 1646577 win 2172 <nop,nop,timestamp 7364419 166634572>
21:40:28.056409 IP dva.ssh > cetri.local.40987: . ack 2677654239 win
32767 <nop,nop,timestamp 166634580 7364404> 21:40:28.056899 IP
cetri.local.40987 > dva.ssh: . 2677707783:2677709231(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056916 IP
cetri.local.40987 > dva.ssh: . 2677709231:2677710679(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056924 IP
cetri.local.40987 > dva.ssh: . 2677710679:2677712127(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056932 IP
cetri.local.40987 > dva.ssh: . 2677712127:2677713575(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056940 IP
cetri.local.40987 > dva.ssh: . 2677713575:2677715023(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056948 IP
cetri.local.40987 > dva.ssh: . 2677715023:2677716471(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056957 IP
cetri.local.40987 > dva.ssh: . 2677716471:2677717919(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.056966 IP
cetri.local.40987 > dva.ssh: . 2677717919:2677719367(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634580> 21:40:28.057758 IP
dva.ssh > cetri.local.40987: . ack 2677657135 win 32767
<nop,nop,timestamp 166634583 7364404> 21:40:28.057793 IP
cetri.local.40987 > dva.ssh: . 2677719367:2677720815(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634583> 21:40:28.057801 IP
cetri.local.40987 > dva.ssh: . 2677720815:2677722263(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634583> 21:40:28.060325 IP
dva.ssh > cetri.local.40987: . ack 2677659999 win 32133
<nop,nop,timestamp 166634621 7364405> 21:40:28.060337 IP
cetri.local.40987 > dva.ssh: . 2677722263:2677723711(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364420 166634621> 21:40:28.061709 IP
dva.ssh > cetri.local.40987: . ack 2677662895 win 32133
<nop,nop,timestamp 166634624 7364419> 21:40:28.061724 IP
cetri.local.40987 > dva.ssh: P 2677723711:2677724279(568) ack 1646577
win 2172 <nop,nop,timestamp 7364421 166634624> 21:40:28.063089 IP
dva.ssh > cetri.local.40987: . ack 2677665791 win 32133
<nop,nop,timestamp 166634626 7364419> 21:40:28.063132 IP
cetri.local.40987 > dva.ssh: . 2677724279:2677725727(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364421 166634626> 21:40:28.063142 IP
cetri.local.40987 > dva.ssh: . 2677725727:2677727175(1448) ack 1646577
win 2172 <nop,nop,timestamp 7364421 166634626> 21:40:28.065722 IP
dva.ssh > cetri.local.40987: . ack 2677668687 win 32133
<nop,nop,timestamp 166634629 7364419> 21:40:28.068316 IP dva.ssh >
cetri.local.40987: . ack 2677671583 win 32133 <nop,nop,timestamp
166634631 7364419> 21:40:28.070871 IP dva.ssh > cetri.local.40987: .
ack 2677674479 win 32133 <nop,nop,timestamp 166634634 7364419>
21:40:28.073461 IP dva.ssh > cetri.local.40987: . ack 2677677375 win
32133 <nop,nop,timestamp 166634637 7364419> 21:40:28.120048 IP dva.ssh
> cetri.local.40987: . ack 2677681719 win 32767 <nop,nop,timestamp
> 166634642 7364419> 21:40:28.120179 IP dva.ssh > cetri.local.40987: P
> 1646577:1646625(48) ack 2677683167 win 32767 <nop,nop,timestamp
> 166634642 7364419> 21:40:28.120263 IP dva.ssh > cetri.local.40987: .
> ack 2677686063 win 32767 <nop,nop,timestamp 166634644 7364419>
> 21:40:28.120349 IP dva.ssh > cetri.local.40987: . ack 2677688959 win
> 32767 <nop,nop,timestamp 166634647 7364419> 21:40:28.120435 IP
> dva.ssh > cetri.local.40987: . ack 2677691855 win 32767
> <nop,nop,timestamp 166634649 7364419> 21:40:28.123671 IP dva.ssh >
> cetri.local.40987: FP 1646625:1646689(64) ack 2677727175 win 17193
> <nop,nop,timestamp 166634688 7364419> 21:40:28.123738 IP
> cetri.local.40987 > dva.ssh: P 2677727175:2677728423(1248) ack
> 1646690 win 2172 <nop,nop,timestamp 7364436 166634642>
> 21:40:28.123746 IP dva.ssh > cetri.local.40987: R 1646690:1646690(0)
> ack 2677727175 win 32767 <nop,nop,timestamp 166634688 7364419>
> 21:40:28.125353 IP dva.ssh > cetri.local.40987: R 696006881:696006881
> (0) win 0

> > How do I find which libraries are used by both rsync and scp?
> 
> You can use 'ldd'. That will tell you which shared libraries each
> uses, and you can then use your distro's package management tools to
> tell you which version of the libs are in use. e.g.
> 
>    dpkg -S /lib/libcrypto.so.0.x.x

I think it would be too much work to do this. I don't have the time,
knowledge or energy to work out which library might be failing. It's
very probably that the problem is with my setup or of my doing. If not,
someone else will have to find and analyse it. I know that's not how
Free software is meant to work, but reality intrudes.



More information about the Wylug-help mailing list