1. Home
  2. Raspberry Pi Group
  3. rsync oddity
  4. Page 3

rsync oddity

It doesn't :-(

The target box won't install tcpdump. I've tried a couple of times, but it doesn't install, it suggests running apt update, which doesn't work (or not fully anyway).

Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libencode-locale-perl libexplain30 libfile-listing-perl libfont-afm-perl libgail-3-0 libhtml-form-perl libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libio-socket-ip-perl libio-socket-ssl-perl liblircclient0 liblwp-mediatypes-perl liblwp-protocol-https-perl liblzo2-2 libmailtools-perl libmpeg2-4 libnet-http-perl libnet-ssleay-perl libsocket-perl liburi-perl libwww-perl libwww-robotrules-perl libxvmc1 xawtv-plugins Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: tcpdump

0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 482 kB of archives. After this operation, 1,029 kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! tcpdump Install these packages without verification [y/N]? Err
formatting link
wheezy/main tcpdump armhf 4.9.0-1~deb7u1 404 Not Found Failed to fetch
formatting link
.9.0-1~deb7u1_armhf.deb 404 Not Found E: Unable to fetch some archives, maybe run apt-get update or try with

--fix-missing?

This is a machine running wheezy.

So, is this a fixable problem, or am I going to have to upgrade (which may take a while as I'm out of SD cards).

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian
Loading thread data ...

You can do that first anyway.

[...]

Ah.

That may well be your problem.

Reply to
Roger Bell_West

On Sun, 7 Jun 2020 18:32:27 +0100, Adrian declaimed the following:

wheezy is archaic... It is four releases out of date (wheezy, jessie, stretch, buster). Even jessie is no longer supported, and I suspect all the package archives for wheezy have been deleted (and jessie may be close to the same state).

You might be able to fetch a source archive/tarball and build from source.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

Yes, you should upgrade.

--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell

SD cards are already on order.

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian

Not so...

deb

formatting link
wheezy main contrib non-free rpi

works.

Reply to
Jim Jackson

Last update when, maybe 3 years ago?

Reply to
A. Dumas

certainly. But the respositories are still around, for those with the need.

Reply to
Jim Jackson

New SD card with Buster installed, and things set up.

Early this morning, the first rsync session ran, and failed in the usual way.

I opened up sessions on the source (192.168.1.18) and target (192.168.1.118) machines, and started tcpdump running on both. I then ran the rsync script on the source machine.

From the source machine :

No. Time Source Destination Protocol Length Info

43 8.398245 192.168.1.18 192.168.1.118 TCP 74 49878 ? 22 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=2778656323 TSecr=0 WS=128 44 8.399106 192.168.1.118 192.168.1.18 TCP 74 22 ? 49878 [SYN, ACK] Seq=0 Ack=1 Win=65160 Len=0 MSS=1460 SACK_PERM=1 TSval=371510247 TSecr=2778656323 WS=64 45 8.399173 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=2778656324 TSecr=371510247 46 8.402167 192.168.1.18 192.168.1.118 SSHv2 108 Client: Protocol (SSH-2.0-OpenSSH_7.4p1 Raspbian-10+deb9u7) 47 8.403659 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1 Ack=43 Win=65152 Len=0 TSval=371510251 TSecr=2778656327 48 8.543644 192.168.1.118 192.168.1.18 SSHv2 109 Server: Protocol (SSH-2.0-OpenSSH_7.9p1 Raspbian-10+deb10u2) 49 8.543673 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=43 Ack=44 Win=29312 Len=0 TSval=2778656468 TSecr=371510391 50 8.560096 192.168.1.118 192.168.1.18 SSHv2 1146 Server: Key Exchange Init 51 8.560132 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=43 Ack=1124 Win=32128 Len=0 TSval=2778656485 TSecr=371510407 52 8.560386 192.168.1.18 192.168.1.118 SSHv2 1498 Client: Key Exchange Init 53 8.561376 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1124 Ack=1475 Win=64064 Len=0 TSval=371510409 TSecr=2778656485 54 8.590538 192.168.1.18 192.168.1.118 SSHv2 114 Client: Diffie-Hellman Key Exchange Init 55 8.591343 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1124 Ack=1523 Win=64064 Len=0 TSval=371510439 TSecr=2778656515 56 8.676005 192.168.1.118 192.168.1.18 SSHv2 518 Server: Diffie-Hellman Key Exchange Reply, New Keys, Encrypted packet (len=172) 57 8.720500 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1523 Ack=1576 Win=35072 Len=0 TSval=2778656645 TSecr=371510524 58 8.755476 192.168.1.18 192.168.1.118 SSHv2 82 Client: New Keys 59 8.756247 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1576 Ack=1539 Win=64128 Len=0 TSval=371510604 TSecr=2778656680 60 8.756274 192.168.1.18 192.168.1.118 SSHv2 110 Client: Encrypted packet (len=44) 61 8.756969 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1576 Ack=1583 Win=64128 Len=0 TSval=371510605 TSecr=2778656681 62 8.757556 192.168.1.118 192.168.1.18 SSHv2 110 Server: Encrypted packet (len=44) 63 8.757566 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1583 Ack=1620 Win=35072 Len=0 TSval=2778656682 TSecr=371510605 64 8.757620 192.168.1.18 192.168.1.118 SSHv2 126 Client: Encrypted packet (len=60) 65 8.775365 192.168.1.118 192.168.1.18 SSHv2 118 Server: Encrypted packet (len=52) 66 8.775451 192.168.1.18 192.168.1.118 SSHv2 438 Client: Encrypted packet (len=372) 67 8.807598 192.168.1.118 192.168.1.18 SSHv2 398 Server: Encrypted packet (len=332) 68 8.834753 192.168.1.18 192.168.1.118 SSHv2 718 Client: Encrypted packet (len=652) 69 8.883209 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2004 Ack=2667 Win=64128 Len=0 TSval=371510731 TSecr=2778656759 70 8.884909 192.168.1.118 192.168.1.18 SSHv2 94 Server: Encrypted packet (len=28) 71 8.885140 192.168.1.18 192.168.1.118 SSHv2 178 Client: Encrypted packet (len=112) 72 8.885956 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2032 Ack=2779 Win=64064 Len=0 TSval=371510734 TSecr=2778656810 73 11.524351 192.168.1.118 192.168.1.18 SSHv2 706 Server: Encrypted packet (len=640) 74 11.570505 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=2779 Ack=2672 Win=40832 Len=0 TSval=2778659495 TSecr=371513372 75 11.571469 192.168.1.118 192.168.1.18 SSHv2 250 Server: Encrypted packet (len=184)

1058 48.762330 192.168.1.118 192.168.1.18 TCP 66 22 ?

49878 [ACK] Seq=21116 Ack=1668835 Win=333952 Len=0 TSval=371550610 TSecr=2778696684 1059 48.762399 192.168.1.18 192.168.1.118 SSHv2 13098 Client: Encrypted packet (len=13032) 1060 48.762430 192.168.1.18 192.168.1.118 SSHv2 930 Client: Encrypted packet (len=864) 1061 48.764914 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21116 Ack=1682731 Win=333952 Len=0 TSval=371550613 TSecr=2778696687 1062 49.225837 192.168.1.118 192.168.1.18 SSHv2 230 Server: Encrypted packet (len=164) 1063 49.225911 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1682731 Ack=21280 Win=149376 Len=0 TSval=2778697151 TSecr=371551074 1064 49.340819 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1065 49.340871 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1066 49.343526 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21280 Ack=1697211 Win=333952 Len=0 TSval=371551191 TSecr=2778697266 1067 49.343562 192.168.1.18 192.168.1.118 SSHv2 11978 Client: Encrypted packet (len=11912) 1068 49.345727 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21280 Ack=1709123 Win=333952 Len=0 TSval=371551194 TSecr=2778697269 1069 49.811906 192.168.1.118 192.168.1.18 SSHv2 214 Server: Encrypted packet (len=148) 1070 49.811955 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1709123 Ack=21428 Win=152320 Len=0 TSval=2778697737 TSecr=371551660 1071 49.936778 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1072 49.936830 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1073 49.939436 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21428 Ack=1723603 Win=333952 Len=0 TSval=371551787 TSecr=2778697862 1074 49.939474 192.168.1.18 192.168.1.118 SSHv2 13098 Client: Encrypted packet (len=13032) 1075 49.939488 192.168.1.18 192.168.1.118 SSHv2 298 Client: Encrypted packet (len=232) 1076 49.941737 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21428 Ack=1736867 Win=333952 Len=0 TSval=371551790 TSecr=2778697864 1077 50.493080 192.168.1.118 192.168.1.18 SSHv2 262 Server: Encrypted packet (len=196) 1078 50.493146 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1736867 Ack=21624 Win=155264 Len=0 TSval=2778698418 TSecr=371552341 1079 50.631121 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1080 50.631183 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1081 50.633815 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21624 Ack=1751347 Win=333952 Len=0 TSval=371552482 TSecr=2778698556 1082 50.633850 192.168.1.18 192.168.1.118 SSHv2 11282 Client: Encrypted packet (len=11216) 1083 50.636052 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21624 Ack=1762563 Win=333952 Len=0 TSval=371552484 TSecr=2778698559 1084 50.643400 192.168.1.118 192.168.1.18 SSHv2 102 Server: Encrypted packet (len=36) 1085 50.643435 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1762563 Ack=21660 Win=155264 Len=0 TSval=2778698568 TSecr=371552491 1086 51.105434 192.168.1.118 192.168.1.18 SSHv2 222 Server: Encrypted packet (len=156) 1087 51.105483 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1762563 Ack=21816 Win=158080 Len=0 TSval=2778699030 TSecr=371552953 1088 51.251912 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1089 51.251985 192.168.1.18 192.168.1.118 SSHv2 7306 Client: Encrypted packet (len=7240) 1090 51.254561 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21816 Ack=1777043 Win=333952 Len=0 TSval=371553102 TSecr=2778699177 1091 51.254647 192.168.1.18 192.168.1.118 SSHv2 13098 Client: Encrypted packet (len=13032) 1092 51.254679 192.168.1.18 192.168.1.118 SSHv2 13098 Client: Encrypted packet (len=13032)

From the target machine :

No. Time Source Destination Protocol Length Info

15 24.212488 192.168.1.18 192.168.1.118 TCP 74 49878 ? 22 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=2778656323 TSecr=0 WS=128 16 24.212715 192.168.1.118 192.168.1.18 TCP 74 22 ? 49878 [SYN, ACK] Seq=0 Ack=1 Win=65160 Len=0 MSS=1460 SACK_PERM=1 TSval=371510247 TSecr=2778656323 WS=64 17 24.213350 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=2778656324 TSecr=371510247 18 24.216573 192.168.1.18 192.168.1.118 SSHv2 108 Client: Protocol (SSH-2.0-OpenSSH_7.4p1 Raspbian-10+deb9u7) 19 24.216792 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1 Ack=43 Win=65152 Len=0 TSval=371510251 TSecr=2778656327 20 24.357175 192.168.1.118 192.168.1.18 SSHv2 109 Server: Protocol (SSH-2.0-OpenSSH_7.9p1 Raspbian-10+deb10u2) 21 24.357911 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=43 Ack=44 Win=29312 Len=0 TSval=2778656468 TSecr=371510391 22 24.373383 192.168.1.118 192.168.1.18 SSHv2 1146 Server: Key Exchange Init 23 24.374385 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=43 Ack=1124 Win=32128 Len=0 TSval=2778656485 TSecr=371510407 24 24.374888 192.168.1.18 192.168.1.118 SSHv2 1498 Client: Key Exchange Init 25 24.374992 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1124 Ack=1475 Win=64064 Len=0 TSval=371510409 TSecr=2778656485 26 24.404787 192.168.1.18 192.168.1.118 SSHv2 114 Client: Diffie-Hellman Key Exchange Init 27 24.404913 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1124 Ack=1523 Win=64064 Len=0 TSval=371510439 TSecr=2778656515 28 24.489446 192.168.1.118 192.168.1.18 SSHv2 518 Server: Diffie-Hellman Key Exchange Reply, New Keys, Encrypted packet (len=172) 29 24.534774 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1523 Ack=1576 Win=35072 Len=0 TSval=2778656645 TSecr=371510524 30 24.569707 192.168.1.18 192.168.1.118 SSHv2 82 Client: New Keys 31 24.569842 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1576 Ack=1539 Win=64128 Len=0 TSval=371510604 TSecr=2778656680 32 24.570495 192.168.1.18 192.168.1.118 SSHv2 110 Client: Encrypted packet (len=44) 33 24.570605 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=1576 Ack=1583 Win=64128 Len=0 TSval=371510605 TSecr=2778656681 34 24.571174 192.168.1.118 192.168.1.18 SSHv2 110 Server: Encrypted packet (len=44) 35 24.571759 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1583 Ack=1620 Win=35072 Len=0 TSval=2778656682 TSecr=371510605 36 24.571848 192.168.1.18 192.168.1.118 SSHv2 126 Client: Encrypted packet (len=60) 37 24.588933 192.168.1.118 192.168.1.18 SSHv2 118 Server: Encrypted packet (len=52) 38 24.589777 192.168.1.18 192.168.1.118 SSHv2 438 Client: Encrypted packet (len=372) 39 24.621096 192.168.1.118 192.168.1.18 SSHv2 398 Server: Encrypted packet (len=332) 40 24.649108 192.168.1.18 192.168.1.118 SSHv2 718 Client: Encrypted packet (len=652) 41 24.696698 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2004 Ack=2667 Win=64128 Len=0 TSval=371510731 TSecr=2778656759 42 24.698496 192.168.1.118 192.168.1.18 SSHv2 94 Server: Encrypted packet (len=28) 43 24.699429 192.168.1.18 192.168.1.118 SSHv2 178 Client: Encrypted packet (len=112) 44 24.699599 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2032 Ack=2779 Win=64064 Len=0 TSval=371510734 TSecr=2778656810 45 27.337691 192.168.1.118 192.168.1.18 SSHv2 706 Server: Encrypted packet (len=640) 46 27.384800 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=2779 Ack=2672 Win=40832 Len=0 TSval=2778659495 TSecr=371513372 47 27.385000 192.168.1.118 192.168.1.18 SSHv2 250 Server: Encrypted packet (len=184) 48 27.385687 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=2779 Ack=2856 Win=43008 Len=0 TSval=2778659496 TSecr=371513419 49 27.386030 192.168.1.18 192.168.1.118 SSHv2 258 Client: Encrypted packet (len=192) 50 27.386125 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2856 Ack=2971 Win=64064 Len=0 TSval=371513420 TSecr=2778659497 51 27.389792 192.168.1.118 192.168.1.18 SSHv2 138 Server: Encrypted packet (len=72) 52 27.390666 192.168.1.18 192.168.1.118 SSHv2 110 Client: Encrypted packet (len=44) 53 27.436788 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=2928 Ack=3015 Win=64128 Len=0 TSval=371513471 TSecr=2778659501 54 27.492527 192.168.1.118 192.168.1.18 SSHv2 110 Server: Encrypted packet (len=44)

1981 66.446888 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448)

1982 66.446954 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1983 66.446996 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1984 66.447036 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1985 66.447078 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1986 66.447429 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21624 Ack=1751347 Win=333952 Len=0 TSval=371552482 TSecr=2778698556 1987 66.448521 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1988 66.448677 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1989 66.449083 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1990 66.449200 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1991 66.449253 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1992 66.449293 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1993 66.449330 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 1994 66.449421 192.168.1.18 192.168.1.118 SSHv2 1146 Client: Encrypted packet (len=1080) 1995 66.449714 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21624 Ack=1762563 Win=333952 Len=0 TSval=371552484 TSecr=2778698559 1996 66.457005 192.168.1.118 192.168.1.18 SSHv2 102 Server: Encrypted packet (len=36) 1997 66.457715 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1762563 Ack=21660 Win=155264 Len=0 TSval=2778698568 TSecr=371552491 1998 66.918954 192.168.1.118 192.168.1.18 SSHv2 222 Server: Encrypted packet (len=156) 1999 66.919883 192.168.1.18 192.168.1.118 TCP 66 49878 ? 22 [ACK] Seq=1762563 Ack=21816 Win=158080 Len=0 TSval=2778699030 TSecr=371552953 2000 67.066461 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2001 67.066948 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2002 67.067082 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2003 67.067185 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2004 67.067279 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2005 67.067504 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2006 67.067565 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2007 67.067668 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2008 67.067718 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2009 67.067819 192.168.1.18 192.168.1.118 SSHv2 1514 Client: Encrypted packet (len=1448) 2010 67.068146 192.168.1.118 192.168.1.18 TCP 66 22 ? 49878 [ACK] Seq=21816 Ack=1777043 Win=333952 Len=0 TSval=371553102 TSecr=2778699177 564216 7427.756675 192.168.1.118 192.168.1.18 TCP 66 [TCP Keep-Alive] 22 ? 49878 [ACK] Seq=21815 Ack=1777043 Win=333952 Len=0 TSval=378913834 TSecr=2778699177 564217 7427.757541 192.168.1.18 192.168.1.118 TCP 60 49878 ? 22 [RST] Seq=1777043 Win=0 Len=0

Note the big leap between packets 2010 and 564216 when there was no traffic between the two machines.

Apart from the last two packets on the target, the two sessions seem to run for about the same time on both machines.

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian

[...]

That?s stretch?s SSH on .18 - which _shouldn?t_ be a problem...

[...] .18 sends two 7240-byte packets:

.118 acknowledges their receipt (the Ack field advances by

14480=2*7240):

It sends two 13032-byte packets in quick succession. However, these two packets don?t shown up in the tcpdump from the other end:

The silence from this point is hard to explain. In the absence of an acknowledgement from .118, .18 should be retransmitting, and when it gives up (as the RST below suggests it has) that should provoke some kind traffic. And it?s certainly surprising not to see the final RST shown below.

My current guess is that something has gone wrong in .18?s kernel network stack, possibly related to the the packet size. Since I?m not up for debugging the Linux IP stack, the only way I have to test this theory would be to upgrade .18 to buster and see if gets better (essentially: if there?s a bug that was fixed between the stretch and buster kernels). I appreciate that this is ?perturb the problem and see if it goes away? but I don?t have a better suggestion at this point.

[...]

.118 receives 10 1448-byte packets, the same number of bytes as the two

7240-byte packets sent by .18 - i.e. they were fragmented (by something

- probably .18 itself, but after tcpdump got a look):

.118 acknowledges these packets, the same packet seen in the other log:

...and nothing thereafter. The two 13032-byte packets do not appear.

Two hours later .118 asks if the session still exists and gets a ?no?.

--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell

I think the OP said there wasn't any sort of switch or other packet-mangling device between the two machines - otherwise I'd be looking hard at that.

Reply to
Roger Bell_West

I think its hardware.

Because we are all software people doesn't mean it *is* software...

--
If I had all the money I've spent on drink... 
..I'd spend it on drink. 

Sir Henry (at Rawlinson's End)
Reply to
The Natural Philosopher

I didn't say such a thing.

Source Pi is plugged into a switch (used by 3 Pis in total). That switch is connected to another switch, which the target Pi (and one other) is plugged into. The second switch has two other branches of the network connected to it, both of which have a Pi plugged into them.

In total there are 8 Pis on the network, with OS versions varying from Wheezy to Buster. All of them do a "push" rsync to the target machine, seven across the network, and the target from its SD to the HDD. All work fine apart from this one machine. The source machine does a "pull" rsync from the targets HDD to the source's SSD. This also works OK.

So the only thing in this that I can see is unique is the source machine.

To reiterate, the original machine was working fine, but failed (looks like the power supply went, and took the Pi with it), so a new one was put in, with a new SD card, which is when the problems started. It could be a hardware problem, but it seems to be a very specific case where it fails, but then the same could be said to apply if it is a software error. And it doesn't always fail.

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian

Cable and switch port are presumably unique too, and easy to rule out.

--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell

Since there?s eight Pis knocking around on this network it should be straightforward to test that theory, i.e. by putting the SD card into a different Pi and seeing if the behavior changes.

--
https://www.greenend.org.uk/rjk/
Reply to
Richard Kettlewell

On Sat, 13 Jun 2020 21:13:04 +0100, Richard Kettlewell declaimed the following:

The second permutation is (if these are CABLED connections) to swap cables around. If not cabled -- test the problematic system using a wired connection.

--
	Wulfraed                 Dennis Lee Bieber         AF6VN 
	wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/
Reply to
Dennis Lee Bieber

I.e. Its a hardware issue Which is the third time I have said it. Get another pi and plug the card into that and see if THAT works #

--
  ?A leader is best When people barely know he exists. Of a good leader,  
who talks little,When his work is done, his aim fulfilled,They will say,  
?We did this ourselves.? 

? Lao Tzu, Tao Te Ching
Reply to
The Natural Philosopher

On the basis of trying the easy fixes first, I've swapped the lead and switch port.

However that was this morning, after the overnight rsync job ran, which worked this time around.

If that doesn't work, then next it will probably be swapping the Pi (but keeping the SD card). I've got a spare Pi 2, which ought to be up to the job.

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian

I've just found a faulty cable on the to the Raspberry Pi attached to the bedroom TV, used for web browsing and media playing. I've just upgraded it from a Pi 3B+ to a Pi 4B, and everything seemed to be ok.

However I ran a speed test against from another machine, accessing a USB3 HD on the Pi, and while it was managing 86MB/s down, it was only doing about 5MB/s up. After replacing the cable it did 86MB/s down and

92MB/s up.

As it was normally only used to consume data, and the return path wasn't completely broken, this hadn't been noticed up to now.

---druck

Reply to
druck

In message , Adrian writes

Another night, and another failure.

I've now swapped the source Pi for a spare. Unfortunately the source was a Pi3 and the spare is a Pi2. In most respects, this probably isn't a problem, but I have a BME280 (temperature/humidity/pressure) sensor attached, and they don't seem to play nicely with Pi2s (which is probably worthy of a whole new thread).

With it all connected up (and the router tweaked to reflect the new MAC address), I've rerun the rsync, and it works. However, as this is intermittent, that proves nothing in the short term.

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
Sorry for the rigmarole, If I want spam, I'll go to the shops 
Every time someone says "I don't believe in trolls", another one dies.
Reply to
Adrian

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.