Discussion:
What causes "Connection reset by peer" errors?
Klaus Fehlker
2005-07-11 13:02:07 UTC
Permalink
Hi,

sorry to bother you with this again but i am still stuck. Can somebody say
if this is the right mailing list or is it rather a problem of Apache, or
even our network? As the subject says i have no idea what causes this
"connection reset by peer" error.

Any hint that brings me further is very much welcome!

Thanks,
Klaus
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use Apache
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on client-side. I
use
it from within the LAN as well as from remote sites with a poor network
connection.
Unfortunately, large commits from the remote site sometimes break with the
message "Connection reset by peer". The Apache logs tell that the server
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really know how
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal (165.72.165.25 =
server). In frame 236629 the client sents a DELETE *somethingcryptical*
but
the commit only consists of adds. Does that have to do with the error?
Many thinks for any help,
Klaus
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.jar
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115] (104)Connection
reset by peer: Could not get next bucket brigade [500, #0]
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=dhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
No. Time Source Destination
Protocol
Info
236618 15:50:01.880031 165.72.165.25 2.33.109.115 TCP
http > 4072 [ACK] Seq=1 Ack=507374 Win=30660 Len=0
Frame 236618 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 507374, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507374 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xba62 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236585
The RTT to ACK the segment was: 0.086843000 seconds
No. Time Source Destination
Protocol
Info
236619 15:50:01.880230 165.72.165.25 2.33.109.115 TCP
http > 4072 [ACK] Seq=1 Ack=507886 Win=30660 Len=0
Frame 236619 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 507886, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507886 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xb862 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236587
The RTT to ACK the segment was: 0.084847000 seconds
No. Time Source Destination
Protocol
Info
236620 15:50:01.880274 2.33.109.115 165.72.165.25 HTTP
Continuation
Frame 236620 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http (80),
Seq: 515566, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 515566 (relative sequence number)
Next sequence number: 516078 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0xd63c)
Hypertext Transfer Protocol
Data (512 bytes)
0000 2a 02 7a 78 52 2c 68 6c 12 01 e3 16 35 5e 6d 55 *.zxR,hl....5^mU
0010 8b 39 af b5 c9 e5 ae 76 08 ff 21 bd 01 e3 90 7d .9.....v..!....}
0020 d3 12 8e 11 36 45 0e d4 05 07 ac 43 44 c8 7d 38 ....6E.....CD.}8
0030 60 0d 47 cd 89 99 52 af 2a 53 e5 6c 5f 96 9b 63 `.G...R.*S.l_..c
0040 80 9c fd 99 b3 0b db 02 fe 3a 41 69 53 4a b9 f7 .........:AiSJ..
0050 a6 56 aa 55 1e 35 4e ad b6 8a 00 89 d7 7c bc ea .V.U.5N......|..
0060 38 6b b6 fd 7a 1a 3f 29 6d a8 31 75 61 b3 c5 63 8k..z.?)m.1ua..c
0070 7b 2b 1e a5 a9 ce 33 f1 58 7e f7 a8 d6 84 45 ea {+....3.X~....E.
0080 78 55 c9 42 b1 2e a9 09 dc 79 ac 4b ad b7 cc ed xU.B.....y.K....
0090 f2 9a 1a c4 da 5e 75 22 b0 54 3f 50 1b 70 b7 2a .....^u".T?P.p.*
00a0 b1 7f 77 5d 7c 23 a6 e9 5c 6b 50 1e db 13 22 56 ..w]|#..\kP..."V
00b0 03 b2 38 54 d5 54 9f 74 80 ba 93 9f 73 6e 36 79 ..8T.T.t....sn6y
00c0 02 36 14 50 35 4c d6 5a fe 23 3a bf 3e d4 dd 6c .6.P5L.Z.#:.>..l
00d0 97 da cc 85 c9 50 43 03 38 e6 55 75 a2 8f 47 6d .....PC.8.Uu..Gm
00e0 51 f5 56 88 17 1b 6c 3a 1b 3d 84 8b ce 0d c6 e6 Q.V...l:.=......
00f0 01 b5 90 6a 64 80 5b 53 9e 4f eb 38 da a5 22 dc ...jd.[S.O.8..".
0100 9d ee 1d 07 9b 3c 2a aa b6 b1 22 04 23 71 ec 4f .....<*...".#q.O
0110 b6 b0 df 91 f4 42 62 87 83 0a 45 f8 e2 50 aa 53 .....Bb...E..P.S
0120 93 c8 e5 58 6e 91 bf da 04 8f 6c a5 12 13 4e e7 ...Xn.....l...N.
0130 56 4b 9c 57 79 87 c4 29 d3 08 b1 02 ca ea 38 69 VK.Wy..)......8i
0140 c7 f7 4c 46 4b 5d ac 1a c6 0a 63 ad 77 f2 d1 d6 ..LFK]....c.w...
0150 9b d5 b9 76 13 db 2c 18 4f 61 ad b3 3e 27 74 e1 ...v..,.Oa..>'t.
0160 b5 13 99 ae 57 fd 48 9d ef 11 23 d4 05 29 de cc ....W.H...#..)..
0170 4a 1a ec 52 17 59 aa 10 b3 16 63 a6 ac eb 21 1c J..R.Y....c...!.
0180 fb b1 ba c4 a3 2e 56 97 5a e9 8d 85 bd 35 c0 ab ......V.Z....5..
0190 2e 57 19 bc f0 15 ec 0e 20 b1 ee 8d ec eb 2a 42 .W...... .....*B
01a0 15 a1 c6 9e d2 ed b0 a9 35 ab ab d4 d5 0c e0 1a ........5.......
01b0 08 6f 30 82 a4 2e ba c3 ab 76 89 e5 0c ef 3a b8 .o0......v....:.
01c0 97 60 c4 46 25 d8 60 12 ed 31 dd 06 73 1c a2 dd .`.F%.`..1..s...
01d0 a0 7e ca 00 6f 14 54 77 c8 c5 89 2e b2 9d 2e 0f .~..o.Tw........
01e0 0a 27 45 ad 37 b3 35 ba 25 c9 1a f1 38 7e 37 9e .'E.7.5.%...8~7.
01f0 bd 75 2c ec f8 39 b6 c7 af ec 0d 48 5e c3 a5 6e .u,..9.....H^..n
No. Time Source Destination
Protocol
Info
236621 15:50:01.880400 2.33.109.115 165.72.165.25 HTTP
Continuation
Frame 236621 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http (80),
Seq: 516078, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 516078 (relative sequence number)
Next sequence number: 516590 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0x3d1d)
Hypertext Transfer Protocol
Data (512 bytes)
0000 77 ab 66 79 89 57 64 c8 93 3c ea 56 75 07 14 b8 w.fy.Wd..<.Vu...
0010 8a 2b 0e 31 76 75 59 be 37 58 ac 63 0a dc a5 ee .+.1vuY.7X.c....
0020 66 0a dc 23 48 87 03 35 10 a2 f1 3d 8b 10 64 02 f..#H..5...=..d.
0030 63 63 8b 7c cf 17 63 8e 70 a9 07 04 dd f6 7d 5f cc.|..c.p.....}_
0040 ef ea 0a cb ce e1 e9 ff 9f 95 26 8c 7d c8 ad 1e ..........&.}...
0050 54 7b 2d 4f 15 8f d1 83 91 c6 3a ff 8e ee 5f 26 T{-O......:..._&
0060 b2 07 81 e9 ad 6a 9f 9b 56 ab b6 a4 6e 1e 0f ae .....j..V...n...
0070 6a 8a 44 43 f5 f9 8b 9a 22 3b 4a 1b aa 83 56 45 j.DC....";J...VE
0080 45 b5 73 1b 70 53 68 fb da 4d 41 3e be 95 f4 12 E.s.pSh..MA>....
0090 54 aa 45 ba 78 9f 4c 3d a2 f6 bb d5 2f d4 a3 82 T.E.x.L=..../...
00a0 46 75 4b 39 2e 8f 98 16 87 c9 f0 1c 27 73 06 5a FuK9........'s.Z
00b0 9d a8 44 20 61 8e 66 f4 3a 0f 50 bf 54 4f 70 b8 ..D a.f.:.P.TOp.
00c0 fd 64 1c 92 23 ed f2 aa a7 f8 e9 02 f5 2b 73 e8 .d..#........+s.
00d0 be f7 47 24 2c c0 cf 30 e0 67 19 c8 33 0c e4 d7 ..G$,..0.g..3...
00e0 7c 76 cd a0 cf 07 2f ec 94 69 52 ef 30 85 d5 aa |v..../..iR.0...
0110 9c ee 52 7f f0 a8 97 4d e7 37 90 98 fe 2a f4 de ..R....M.7...*..
0120 80 ac 70 34 ac d5 eb b1 bb 96 42 d8 77 df 84 fa ..p4......B.w...
0130 d7 39 6f bc 2d 28 b7 37 e5 fa 44 58 f0 ae 47 bd .9o.-(.7..DX..G.
0140 c7 8d 06 af d5 6b 42 30 57 c8 7d ec 0b 7b 4b 82 .....kB0W.}..{K.
0150 64 d1 8a bd 2e 1a 5f 2a d6 bb b4 df 64 3d d4 73 d....._*....d=.s
0160 90 cc f0 0f d4 87 6c 3a ff 18 a3 c1 2a 47 6b 5a ......l:....*GkZ
0170 7d cc 85 5c bb ad 6a df fa b3 e5 c2 62 af dc ce }..\..j.....b...
0180 ee b1 c6 96 f2 9d 5b af fa 54 fd 85 d7 fd 4c d0 ......[..T....L.
0190 b0 60 a4 b0 b1 b1 0e 5a 0a f5 ea d0 8f 53 5f 70 .`.....Z.....S_p
01a0 ab e1 4a f5 25 d7 b3 e0 36 8d 02 56 7b d5 d7 fc ..J.%...6..V{...
01b0 f2 c7 95 ea 9b 4e c7 6a bb 7a bf 57 4e 51 7f 83 .....N.j.z.WNQ..
01c0 38 a8 6f f9 85 d1 ea 6a 93 35 45 32 d4 3f 60 a6 8.o....j.5E2.?`.
01d0 eb 8d 54 4e ee 25 47 a0 03 7e 7b e7 9d c2 96 ee ..TN.%G..~{.....
01e0 de 30 9f 93 74 e2 bf 67 66 ba d4 77 5d fc 0a 42 .0..t..gf..w]..B
01f0 4f 2c 95 9b b5 70 6b d2 12 9b 85 0f b7 89 a6 35 O,...pk........5
No. Time Source Destination
Protocol
Info
236622 15:50:01.880737 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST, ACK] Seq=1 Ack=516078 Win=0 Len=0
Frame 236622 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516078 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x1023 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236620
The RTT to ACK the segment was: 0.000463000 seconds
No. Time Source Destination
Protocol
Info
236623 15:50:01.880860 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST, ACK] Seq=1 Ack=516590 Win=0 Len=0
Frame 236623 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516590 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x0e23 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236621
The RTT to ACK the segment was: 0.000460000 seconds
No. Time Source Destination
Protocol
Info
236624 15:50:01.980765 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST] Seq=1 Ack=516078 Win=0 Len=0
Frame 236624 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x1033 (correct)
No. Time Source Destination
Protocol
Info
236625 15:50:01.980943 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST] Seq=1 Ack=516590 Win=0 Len=0
Frame 236625 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x0e33 (correct)
No. Time Source Destination
Protocol
Info
236626 15:50:02.095888 2.33.109.115 165.72.165.25 TCP
4073 > http [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460
Frame 236626 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 0, Ack: 0, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 64240
Checksum: 0xdb11 (correct)
Options: (8 bytes)
No. Time Source Destination
Protocol
Info
236627 15:50:02.141335 165.72.165.25 2.33.109.115 TCP
http > 4073 [SYN, ACK] Seq=0 Ack=1 Win=1460 Len=0 MSS=1460
Frame 236627 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 1460
Checksum: 0x852c (correct)
Options: (8 bytes)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236626
The RTT to ACK the segment was: 0.045447000 seconds
No. Time Source Destination
Protocol
Info
236628 15:50:02.141448 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=1 Ack=1 Win=64240 [CHECKSUM INCORRECT] Len=0
Frame 236628 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64240
Checksum: 0xba10 (incorrect, should be 0xbcb3)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236627
The RTT to ACK the segment was: 0.000113000 seconds
No. Time Source Destination
Protocol
Info
236629 15:50:02.141761 2.33.109.115 165.72.165.25 HTTP
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1
Frame 236629 (301 bytes on wire, 301 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 247
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 248 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbb07 (incorrect, should be 0x8fc9)
Hypertext Transfer Protocol
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1\r\n
Request Method: DELETE
Host: czcholsint004.prg-dc.dhl.com\r\n
User-Agent: SVN/1.2.0 (r14790) neon/0.24.7\r\n
Connection: TE\r\n
TE: trailers\r\n
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx\r\n
\r\n
No. Time Source Destination
Protocol
Info
236630 15:50:02.188235 165.72.165.25 2.33.109.115 TCP
http > 4073 [ACK] Seq=1 Ack=248 Win=6432 Len=0
Frame 236630 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 1, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 6432
Checksum: 0x9d8d (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236629
The RTT to ACK the segment was: 0.046474000 seconds
No. Time Source Destination
Protocol
Info
236631 15:50:02.513670 165.72.165.25 2.33.109.115 HTTP
HTTP/1.1 204 No Content
Frame 236631 (239 bytes on wire, 239 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 1, Ack: 248, Len: 185
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Next sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 6432
Checksum: 0x3983 (correct)
Hypertext Transfer Protocol
HTTP/1.1 204 No Content\r\n
Response Code: 204
Date: Tue, 28 Jun 2005 13:44:30 GMT\r\n
Server: Apache/2.0.53 (Unix) mod_ssl/2.0.53 OpenSSL/0.9.7a DAV/2
SVN/1.1.4\r\n
Content-Length: 0\r\n
Content-Type: text/plain\r\n
\r\n
No. Time Source Destination
Protocol
Info
236632 15:50:02.626447 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=248 Ack=186 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236632 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 186, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 186 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbc)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236631
The RTT to ACK the segment was: 0.112777000 seconds
No. Time Source Destination
Protocol
Info
236633 15:50:17.522817 165.72.165.25 2.33.109.115 TCP
http > 4073 [FIN, ACK] Seq=186 Ack=248 Win=6432 Len=0
Frame 236633 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 186, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 6432
Checksum: 0x9cd3 (correct)
No. Time Source Destination
Protocol
Info
236634 15:50:17.522876 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236634 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbb)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236633
The RTT to ACK the segment was: 0.000059000 seconds
No. Time Source Destination
Protocol
Info
236635 15:51:34.060372 2.33.109.115 165.72.165.25 TCP
4073 > http [FIN, ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT]
Len=0
Frame 236635 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbba)
No. Time Source Destination
Protocol
Info
236636 15:51:34.105175 165.72.165.25 2.33.109.115 TCP
http > 4073 [RST] Seq=187 Ack=1085398113 Win=0 Len=0
Frame 236636 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 187, Ack: 1085398113, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 187 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x99e5 (correct)
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse f�r Mail, Message, More +++
k***@collab.net
2005-07-11 15:27:33 UTC
Permalink
Post by Klaus Fehlker
sorry to bother you with this again but i am still stuck. Can somebody say
if this is the right mailing list or is it rather a problem of Apache, or
even our network? As the subject says i have no idea what causes this
"connection reset by peer" error.
Any hint that brings me further is very much welcome!
This is just a wild guess, possibly totally wrong, but have you tried
playing with the 'http-timeout' parameter in your
~/.subversion/servers configuration file?

-Karl
Post by Klaus Fehlker
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use Apache
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on client-side. I
use
it from within the LAN as well as from remote sites with a poor network
connection.
Unfortunately, large commits from the remote site sometimes break with the
message "Connection reset by peer". The Apache logs tell that the server
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really know how
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal (165.72.165.25 =
server). In frame 236629 the client sents a DELETE *somethingcryptical*
but
the commit only consists of adds. Does that have to do with the error?
Many thinks for any help,
Klaus
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.jar
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115] (104)Connection
reset by peer: Could not get next bucket brigade [500, #0]
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=dhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
No. Time Source Destination
Protocol
Info
236618 15:50:01.880031 165.72.165.25 2.33.109.115 TCP
http > 4072 [ACK] Seq=1 Ack=507374 Win=30660 Len=0
Frame 236618 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 507374, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507374 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xba62 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236585
The RTT to ACK the segment was: 0.086843000 seconds
No. Time Source Destination
Protocol
Info
236619 15:50:01.880230 165.72.165.25 2.33.109.115 TCP
http > 4072 [ACK] Seq=1 Ack=507886 Win=30660 Len=0
Frame 236619 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 507886, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507886 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xb862 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236587
The RTT to ACK the segment was: 0.084847000 seconds
No. Time Source Destination
Protocol
Info
236620 15:50:01.880274 2.33.109.115 165.72.165.25 HTTP
Continuation
Frame 236620 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http (80),
Seq: 515566, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 515566 (relative sequence number)
Next sequence number: 516078 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0xd63c)
Hypertext Transfer Protocol
Data (512 bytes)
0000 2a 02 7a 78 52 2c 68 6c 12 01 e3 16 35 5e 6d 55 *.zxR,hl....5^mU
0010 8b 39 af b5 c9 e5 ae 76 08 ff 21 bd 01 e3 90 7d .9.....v..!....}
0020 d3 12 8e 11 36 45 0e d4 05 07 ac 43 44 c8 7d 38 ....6E.....CD.}8
0030 60 0d 47 cd 89 99 52 af 2a 53 e5 6c 5f 96 9b 63 `.G...R.*S.l_..c
0040 80 9c fd 99 b3 0b db 02 fe 3a 41 69 53 4a b9 f7 .........:AiSJ..
0050 a6 56 aa 55 1e 35 4e ad b6 8a 00 89 d7 7c bc ea .V.U.5N......|..
0060 38 6b b6 fd 7a 1a 3f 29 6d a8 31 75 61 b3 c5 63 8k..z.?)m.1ua..c
0070 7b 2b 1e a5 a9 ce 33 f1 58 7e f7 a8 d6 84 45 ea {+....3.X~....E.
0080 78 55 c9 42 b1 2e a9 09 dc 79 ac 4b ad b7 cc ed xU.B.....y.K....
0090 f2 9a 1a c4 da 5e 75 22 b0 54 3f 50 1b 70 b7 2a .....^u".T?P.p.*
00a0 b1 7f 77 5d 7c 23 a6 e9 5c 6b 50 1e db 13 22 56 ..w]|#..\kP..."V
00b0 03 b2 38 54 d5 54 9f 74 80 ba 93 9f 73 6e 36 79 ..8T.T.t....sn6y
00c0 02 36 14 50 35 4c d6 5a fe 23 3a bf 3e d4 dd 6c .6.P5L.Z.#:.>..l
00d0 97 da cc 85 c9 50 43 03 38 e6 55 75 a2 8f 47 6d .....PC.8.Uu..Gm
00e0 51 f5 56 88 17 1b 6c 3a 1b 3d 84 8b ce 0d c6 e6 Q.V...l:.=......
00f0 01 b5 90 6a 64 80 5b 53 9e 4f eb 38 da a5 22 dc ...jd.[S.O.8..".
0100 9d ee 1d 07 9b 3c 2a aa b6 b1 22 04 23 71 ec 4f .....<*...".#q.O
0110 b6 b0 df 91 f4 42 62 87 83 0a 45 f8 e2 50 aa 53 .....Bb...E..P.S
0120 93 c8 e5 58 6e 91 bf da 04 8f 6c a5 12 13 4e e7 ...Xn.....l...N.
0130 56 4b 9c 57 79 87 c4 29 d3 08 b1 02 ca ea 38 69 VK.Wy..)......8i
0140 c7 f7 4c 46 4b 5d ac 1a c6 0a 63 ad 77 f2 d1 d6 ..LFK]....c.w...
0150 9b d5 b9 76 13 db 2c 18 4f 61 ad b3 3e 27 74 e1 ...v..,.Oa..>'t.
0160 b5 13 99 ae 57 fd 48 9d ef 11 23 d4 05 29 de cc ....W.H...#..)..
0170 4a 1a ec 52 17 59 aa 10 b3 16 63 a6 ac eb 21 1c J..R.Y....c...!.
0180 fb b1 ba c4 a3 2e 56 97 5a e9 8d 85 bd 35 c0 ab ......V.Z....5..
0190 2e 57 19 bc f0 15 ec 0e 20 b1 ee 8d ec eb 2a 42 .W...... .....*B
01a0 15 a1 c6 9e d2 ed b0 a9 35 ab ab d4 d5 0c e0 1a ........5.......
01b0 08 6f 30 82 a4 2e ba c3 ab 76 89 e5 0c ef 3a b8 .o0......v....:.
01c0 97 60 c4 46 25 d8 60 12 ed 31 dd 06 73 1c a2 dd .`.F%.`..1..s...
01d0 a0 7e ca 00 6f 14 54 77 c8 c5 89 2e b2 9d 2e 0f .~..o.Tw........
01e0 0a 27 45 ad 37 b3 35 ba 25 c9 1a f1 38 7e 37 9e .'E.7.5.%...8~7.
01f0 bd 75 2c ec f8 39 b6 c7 af ec 0d 48 5e c3 a5 6e .u,..9.....H^..n
No. Time Source Destination
Protocol
Info
236621 15:50:01.880400 2.33.109.115 165.72.165.25 HTTP
Continuation
Frame 236621 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http (80),
Seq: 516078, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 516078 (relative sequence number)
Next sequence number: 516590 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0x3d1d)
Hypertext Transfer Protocol
Data (512 bytes)
0000 77 ab 66 79 89 57 64 c8 93 3c ea 56 75 07 14 b8 w.fy.Wd..<.Vu...
0010 8a 2b 0e 31 76 75 59 be 37 58 ac 63 0a dc a5 ee .+.1vuY.7X.c....
0020 66 0a dc 23 48 87 03 35 10 a2 f1 3d 8b 10 64 02 f..#H..5...=..d.
0030 63 63 8b 7c cf 17 63 8e 70 a9 07 04 dd f6 7d 5f cc.|..c.p.....}_
0040 ef ea 0a cb ce e1 e9 ff 9f 95 26 8c 7d c8 ad 1e ..........&.}...
0050 54 7b 2d 4f 15 8f d1 83 91 c6 3a ff 8e ee 5f 26 T{-O......:..._&
0060 b2 07 81 e9 ad 6a 9f 9b 56 ab b6 a4 6e 1e 0f ae .....j..V...n...
0070 6a 8a 44 43 f5 f9 8b 9a 22 3b 4a 1b aa 83 56 45 j.DC....";J...VE
0080 45 b5 73 1b 70 53 68 fb da 4d 41 3e be 95 f4 12 E.s.pSh..MA>....
0090 54 aa 45 ba 78 9f 4c 3d a2 f6 bb d5 2f d4 a3 82 T.E.x.L=..../...
00a0 46 75 4b 39 2e 8f 98 16 87 c9 f0 1c 27 73 06 5a FuK9........'s.Z
00b0 9d a8 44 20 61 8e 66 f4 3a 0f 50 bf 54 4f 70 b8 ..D a.f.:.P.TOp.
00c0 fd 64 1c 92 23 ed f2 aa a7 f8 e9 02 f5 2b 73 e8 .d..#........+s.
00d0 be f7 47 24 2c c0 cf 30 e0 67 19 c8 33 0c e4 d7 ..G$,..0.g..3...
00e0 7c 76 cd a0 cf 07 2f ec 94 69 52 ef 30 85 d5 aa |v..../..iR.0...
0110 9c ee 52 7f f0 a8 97 4d e7 37 90 98 fe 2a f4 de ..R....M.7...*..
0120 80 ac 70 34 ac d5 eb b1 bb 96 42 d8 77 df 84 fa ..p4......B.w...
0130 d7 39 6f bc 2d 28 b7 37 e5 fa 44 58 f0 ae 47 bd .9o.-(.7..DX..G.
0140 c7 8d 06 af d5 6b 42 30 57 c8 7d ec 0b 7b 4b 82 .....kB0W.}..{K.
0150 64 d1 8a bd 2e 1a 5f 2a d6 bb b4 df 64 3d d4 73 d....._*....d=.s
0160 90 cc f0 0f d4 87 6c 3a ff 18 a3 c1 2a 47 6b 5a ......l:....*GkZ
0170 7d cc 85 5c bb ad 6a df fa b3 e5 c2 62 af dc ce }..\..j.....b...
0180 ee b1 c6 96 f2 9d 5b af fa 54 fd 85 d7 fd 4c d0 ......[..T....L.
0190 b0 60 a4 b0 b1 b1 0e 5a 0a f5 ea d0 8f 53 5f 70 .`.....Z.....S_p
01a0 ab e1 4a f5 25 d7 b3 e0 36 8d 02 56 7b d5 d7 fc ..J.%...6..V{...
01b0 f2 c7 95 ea 9b 4e c7 6a bb 7a bf 57 4e 51 7f 83 .....N.j.z.WNQ..
01c0 38 a8 6f f9 85 d1 ea 6a 93 35 45 32 d4 3f 60 a6 8.o....j.5E2.?`.
01d0 eb 8d 54 4e ee 25 47 a0 03 7e 7b e7 9d c2 96 ee ..TN.%G..~{.....
01e0 de 30 9f 93 74 e2 bf 67 66 ba d4 77 5d fc 0a 42 .0..t..gf..w]..B
01f0 4f 2c 95 9b b5 70 6b d2 12 9b 85 0f b7 89 a6 35 O,...pk........5
No. Time Source Destination
Protocol
Info
236622 15:50:01.880737 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST, ACK] Seq=1 Ack=516078 Win=0 Len=0
Frame 236622 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516078 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x1023 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236620
The RTT to ACK the segment was: 0.000463000 seconds
No. Time Source Destination
Protocol
Info
236623 15:50:01.880860 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST, ACK] Seq=1 Ack=516590 Win=0 Len=0
Frame 236623 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516590 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x0e23 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236621
The RTT to ACK the segment was: 0.000460000 seconds
No. Time Source Destination
Protocol
Info
236624 15:50:01.980765 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST] Seq=1 Ack=516078 Win=0 Len=0
Frame 236624 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x1033 (correct)
No. Time Source Destination
Protocol
Info
236625 15:50:01.980943 165.72.165.25 2.33.109.115 TCP
http > 4072 [RST] Seq=1 Ack=516590 Win=0 Len=0
Frame 236625 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072 (4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x0e33 (correct)
No. Time Source Destination
Protocol
Info
236626 15:50:02.095888 2.33.109.115 165.72.165.25 TCP
4073 > http [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460
Frame 236626 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 0, Ack: 0, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 64240
Checksum: 0xdb11 (correct)
Options: (8 bytes)
No. Time Source Destination
Protocol
Info
236627 15:50:02.141335 165.72.165.25 2.33.109.115 TCP
http > 4073 [SYN, ACK] Seq=0 Ack=1 Win=1460 Len=0 MSS=1460
Frame 236627 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 1460
Checksum: 0x852c (correct)
Options: (8 bytes)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236626
The RTT to ACK the segment was: 0.045447000 seconds
No. Time Source Destination
Protocol
Info
236628 15:50:02.141448 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=1 Ack=1 Win=64240 [CHECKSUM INCORRECT] Len=0
Frame 236628 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64240
Checksum: 0xba10 (incorrect, should be 0xbcb3)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236627
The RTT to ACK the segment was: 0.000113000 seconds
No. Time Source Destination
Protocol
Info
236629 15:50:02.141761 2.33.109.115 165.72.165.25 HTTP
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1
Frame 236629 (301 bytes on wire, 301 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 1, Ack: 1, Len: 247
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 248 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbb07 (incorrect, should be 0x8fc9)
Hypertext Transfer Protocol
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1\r\n
Request Method: DELETE
Host: czcholsint004.prg-dc.dhl.com\r\n
User-Agent: SVN/1.2.0 (r14790) neon/0.24.7\r\n
Connection: TE\r\n
TE: trailers\r\n
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx\r\n
\r\n
No. Time Source Destination
Protocol
Info
236630 15:50:02.188235 165.72.165.25 2.33.109.115 TCP
http > 4073 [ACK] Seq=1 Ack=248 Win=6432 Len=0
Frame 236630 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 1, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 6432
Checksum: 0x9d8d (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236629
The RTT to ACK the segment was: 0.046474000 seconds
No. Time Source Destination
Protocol
Info
236631 15:50:02.513670 165.72.165.25 2.33.109.115 HTTP
HTTP/1.1 204 No Content
Frame 236631 (239 bytes on wire, 239 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 1, Ack: 248, Len: 185
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Next sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 6432
Checksum: 0x3983 (correct)
Hypertext Transfer Protocol
HTTP/1.1 204 No Content\r\n
Response Code: 204
Date: Tue, 28 Jun 2005 13:44:30 GMT\r\n
Server: Apache/2.0.53 (Unix) mod_ssl/2.0.53 OpenSSL/0.9.7a DAV/2
SVN/1.1.4\r\n
Content-Length: 0\r\n
Content-Type: text/plain\r\n
\r\n
No. Time Source Destination
Protocol
Info
236632 15:50:02.626447 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=248 Ack=186 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236632 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 186, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 186 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbc)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236631
The RTT to ACK the segment was: 0.112777000 seconds
No. Time Source Destination
Protocol
Info
236633 15:50:17.522817 165.72.165.25 2.33.109.115 TCP
http > 4073 [FIN, ACK] Seq=186 Ack=248 Win=6432 Len=0
Frame 236633 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 186, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 6432
Checksum: 0x9cd3 (correct)
No. Time Source Destination
Protocol
Info
236634 15:50:17.522876 2.33.109.115 165.72.165.25 TCP
4073 > http [ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236634 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbb)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236633
The RTT to ACK the segment was: 0.000059000 seconds
No. Time Source Destination
Protocol
Info
236635 15:51:34.060372 2.33.109.115 165.72.165.25 TCP
4073 > http [FIN, ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT]
Len=0
Frame 236635 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http (80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbba)
No. Time Source Destination
Protocol
Info
236636 15:51:34.105175 165.72.165.25 2.33.109.115 TCP
http > 4073 [RST] Seq=187 Ack=1085398113 Win=0 Len=0
Frame 236636 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073 (4073),
Seq: 187, Ack: 1085398113, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 187 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x99e5 (correct)
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse f|r Mail, Message, More +++
---------------------------------------------------------------------
Klaus Fehlker
2005-07-12 12:46:02 UTC
Permalink
--- Ursprüngliche Nachricht ---
Betreff: Re: What causes "Connection reset by peer" errors?
Datum: 11 Jul 2005 10:27:33 -0500
Post by Klaus Fehlker
sorry to bother you with this again but i am still stuck. Can somebody
say
Post by Klaus Fehlker
if this is the right mailing list or is it rather a problem of Apache,
or
Post by Klaus Fehlker
even our network? As the subject says i have no idea what causes this
"connection reset by peer" error.
Any hint that brings me further is very much welcome!
This is just a wild guess, possibly totally wrong, but have you tried
playing with the 'http-timeout' parameter in your
~/.subversion/servers configuration file?
Hm, haven't tried it, yet, but could a bad client configuration make the
server send Resets?
What is SVN's usual behavior when the server sends a reset? Do you know what
can cause a server sending a reset?

Klaus
Post by Klaus Fehlker
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use
Apache
Post by Klaus Fehlker
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on client-side.
I
Post by Klaus Fehlker
use
it from within the LAN as well as from remote sites with a poor
network
Post by Klaus Fehlker
connection.
Unfortunately, large commits from the remote site sometimes break with
the
Post by Klaus Fehlker
message "Connection reset by peer". The Apache logs tell that the
server
Post by Klaus Fehlker
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really know
how
Post by Klaus Fehlker
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal
(165.72.165.25 =
Post by Klaus Fehlker
server). In frame 236629 the client sents a DELETE
*somethingcryptical*
Post by Klaus Fehlker
but
the commit only consists of adds. Does that have to do with the error?
Many thinks for any help,
Klaus
[Tue Jun 28 17:05:17 2005] [info] [client 2.33.109.115] Access
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.jar
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115]
(104)Connection
Post by Klaus Fehlker
reset by peer: Could not get next bucket brigade [500, #0]
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=dhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
[Tue Jun 28 17:05:20 2005] [info] [client 2.33.109.115] Access
No. Time Source Destination
Protocol
Info
236618 15:50:01.880031 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [ACK] Seq=1 Ack=507374 Win=30660 Len=0
Frame 236618 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 507374, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507374 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xba62 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236585
The RTT to ACK the segment was: 0.086843000 seconds
No. Time Source Destination
Protocol
Info
236619 15:50:01.880230 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [ACK] Seq=1 Ack=507886 Win=30660 Len=0
Frame 236619 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 507886, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507886 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xb862 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236587
The RTT to ACK the segment was: 0.084847000 seconds
No. Time Source Destination
Protocol
Info
236620 15:50:01.880274 2.33.109.115 165.72.165.25
HTTP
Post by Klaus Fehlker
Continuation
Frame 236620 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 515566, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 515566 (relative sequence number)
Next sequence number: 516078 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0xd63c)
Hypertext Transfer Protocol
Data (512 bytes)
0000 2a 02 7a 78 52 2c 68 6c 12 01 e3 16 35 5e 6d 55
*.zxR,hl....5^mU
Post by Klaus Fehlker
0010 8b 39 af b5 c9 e5 ae 76 08 ff 21 bd 01 e3 90 7d
.9.....v..!....}
Post by Klaus Fehlker
0020 d3 12 8e 11 36 45 0e d4 05 07 ac 43 44 c8 7d 38
....6E.....CD.}8
Post by Klaus Fehlker
0030 60 0d 47 cd 89 99 52 af 2a 53 e5 6c 5f 96 9b 63
`.G...R.*S.l_..c
Post by Klaus Fehlker
0040 80 9c fd 99 b3 0b db 02 fe 3a 41 69 53 4a b9 f7
.........:AiSJ..
Post by Klaus Fehlker
0050 a6 56 aa 55 1e 35 4e ad b6 8a 00 89 d7 7c bc ea
.V.U.5N......|..
Post by Klaus Fehlker
0060 38 6b b6 fd 7a 1a 3f 29 6d a8 31 75 61 b3 c5 63
8k..z.?)m.1ua..c
Post by Klaus Fehlker
0070 7b 2b 1e a5 a9 ce 33 f1 58 7e f7 a8 d6 84 45 ea
{+....3.X~....E.
Post by Klaus Fehlker
0080 78 55 c9 42 b1 2e a9 09 dc 79 ac 4b ad b7 cc ed
xU.B.....y.K....
Post by Klaus Fehlker
0090 f2 9a 1a c4 da 5e 75 22 b0 54 3f 50 1b 70 b7 2a
.....^u".T?P.p.*
Post by Klaus Fehlker
00a0 b1 7f 77 5d 7c 23 a6 e9 5c 6b 50 1e db 13 22 56
..w]|#..\kP..."V
Post by Klaus Fehlker
00b0 03 b2 38 54 d5 54 9f 74 80 ba 93 9f 73 6e 36 79
..8T.T.t....sn6y
Post by Klaus Fehlker
00c0 02 36 14 50 35 4c d6 5a fe 23 3a bf 3e d4 dd 6c
.6.P5L.Z.#:.>..l
Post by Klaus Fehlker
00d0 97 da cc 85 c9 50 43 03 38 e6 55 75 a2 8f 47 6d
.....PC.8.Uu..Gm
Post by Klaus Fehlker
00e0 51 f5 56 88 17 1b 6c 3a 1b 3d 84 8b ce 0d c6 e6
Q.V...l:.=......
Post by Klaus Fehlker
00f0 01 b5 90 6a 64 80 5b 53 9e 4f eb 38 da a5 22 dc
...jd.[S.O.8..".
Post by Klaus Fehlker
0100 9d ee 1d 07 9b 3c 2a aa b6 b1 22 04 23 71 ec 4f
.....<*...".#q.O
Post by Klaus Fehlker
0110 b6 b0 df 91 f4 42 62 87 83 0a 45 f8 e2 50 aa 53
.....Bb...E..P.S
Post by Klaus Fehlker
0120 93 c8 e5 58 6e 91 bf da 04 8f 6c a5 12 13 4e e7
...Xn.....l...N.
Post by Klaus Fehlker
0130 56 4b 9c 57 79 87 c4 29 d3 08 b1 02 ca ea 38 69
VK.Wy..)......8i
Post by Klaus Fehlker
0140 c7 f7 4c 46 4b 5d ac 1a c6 0a 63 ad 77 f2 d1 d6
..LFK]....c.w...
Post by Klaus Fehlker
0150 9b d5 b9 76 13 db 2c 18 4f 61 ad b3 3e 27 74 e1
...v..,.Oa..>'t.
Post by Klaus Fehlker
0160 b5 13 99 ae 57 fd 48 9d ef 11 23 d4 05 29 de cc
....W.H...#..)..
Post by Klaus Fehlker
0170 4a 1a ec 52 17 59 aa 10 b3 16 63 a6 ac eb 21 1c
J..R.Y....c...!.
Post by Klaus Fehlker
0180 fb b1 ba c4 a3 2e 56 97 5a e9 8d 85 bd 35 c0 ab
......V.Z....5..
Post by Klaus Fehlker
0190 2e 57 19 bc f0 15 ec 0e 20 b1 ee 8d ec eb 2a 42 .W......
.....*B
Post by Klaus Fehlker
01a0 15 a1 c6 9e d2 ed b0 a9 35 ab ab d4 d5 0c e0 1a
........5.......
Post by Klaus Fehlker
01b0 08 6f 30 82 a4 2e ba c3 ab 76 89 e5 0c ef 3a b8
.o0......v....:.
Post by Klaus Fehlker
01c0 97 60 c4 46 25 d8 60 12 ed 31 dd 06 73 1c a2 dd
.`.F%.`..1..s...
Post by Klaus Fehlker
01d0 a0 7e ca 00 6f 14 54 77 c8 c5 89 2e b2 9d 2e 0f
.~..o.Tw........
Post by Klaus Fehlker
01e0 0a 27 45 ad 37 b3 35 ba 25 c9 1a f1 38 7e 37 9e
.'E.7.5.%...8~7.
Post by Klaus Fehlker
01f0 bd 75 2c ec f8 39 b6 c7 af ec 0d 48 5e c3 a5 6e
.u,..9.....H^..n
Post by Klaus Fehlker
No. Time Source Destination
Protocol
Info
236621 15:50:01.880400 2.33.109.115 165.72.165.25
HTTP
Post by Klaus Fehlker
Continuation
Frame 236621 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 516078, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 516078 (relative sequence number)
Next sequence number: 516590 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0x3d1d)
Hypertext Transfer Protocol
Data (512 bytes)
0000 77 ab 66 79 89 57 64 c8 93 3c ea 56 75 07 14 b8
w.fy.Wd..<.Vu...
Post by Klaus Fehlker
0010 8a 2b 0e 31 76 75 59 be 37 58 ac 63 0a dc a5 ee
.+.1vuY.7X.c....
Post by Klaus Fehlker
0020 66 0a dc 23 48 87 03 35 10 a2 f1 3d 8b 10 64 02
f..#H..5...=..d.
Post by Klaus Fehlker
0030 63 63 8b 7c cf 17 63 8e 70 a9 07 04 dd f6 7d 5f
cc.|..c.p.....}_
Post by Klaus Fehlker
0040 ef ea 0a cb ce e1 e9 ff 9f 95 26 8c 7d c8 ad 1e
..........&.}...
Post by Klaus Fehlker
0050 54 7b 2d 4f 15 8f d1 83 91 c6 3a ff 8e ee 5f 26
T{-O......:..._&
Post by Klaus Fehlker
0060 b2 07 81 e9 ad 6a 9f 9b 56 ab b6 a4 6e 1e 0f ae
.....j..V...n...
Post by Klaus Fehlker
0070 6a 8a 44 43 f5 f9 8b 9a 22 3b 4a 1b aa 83 56 45
j.DC....";J...VE
Post by Klaus Fehlker
0080 45 b5 73 1b 70 53 68 fb da 4d 41 3e be 95 f4 12
E.s.pSh..MA>....
Post by Klaus Fehlker
0090 54 aa 45 ba 78 9f 4c 3d a2 f6 bb d5 2f d4 a3 82
T.E.x.L=..../...
Post by Klaus Fehlker
00a0 46 75 4b 39 2e 8f 98 16 87 c9 f0 1c 27 73 06 5a
FuK9........'s.Z
Post by Klaus Fehlker
00b0 9d a8 44 20 61 8e 66 f4 3a 0f 50 bf 54 4f 70 b8 ..D
a.f.:.P.TOp.
Post by Klaus Fehlker
00c0 fd 64 1c 92 23 ed f2 aa a7 f8 e9 02 f5 2b 73 e8
.d..#........+s.
Post by Klaus Fehlker
00d0 be f7 47 24 2c c0 cf 30 e0 67 19 c8 33 0c e4 d7
..G$,..0.g..3...
Post by Klaus Fehlker
00e0 7c 76 cd a0 cf 07 2f ec 94 69 52 ef 30 85 d5 aa
|v..../..iR.0...
_wM\.
Post by Klaus Fehlker
0100 e2 6c 40 5b cd 53 26 a8 d5 2b 55 bf 4f ca 2f ba
0110 9c ee 52 7f f0 a8 97 4d e7 37 90 98 fe 2a f4 de
..R....M.7...*..
Post by Klaus Fehlker
0120 80 ac 70 34 ac d5 eb b1 bb 96 42 d8 77 df 84 fa
..p4......B.w...
Post by Klaus Fehlker
0130 d7 39 6f bc 2d 28 b7 37 e5 fa 44 58 f0 ae 47 bd
.9o.-(.7..DX..G.
Post by Klaus Fehlker
0140 c7 8d 06 af d5 6b 42 30 57 c8 7d ec 0b 7b 4b 82
.....kB0W.}..{K.
Post by Klaus Fehlker
0150 64 d1 8a bd 2e 1a 5f 2a d6 bb b4 df 64 3d d4 73
d....._*....d=.s
Post by Klaus Fehlker
0160 90 cc f0 0f d4 87 6c 3a ff 18 a3 c1 2a 47 6b 5a
......l:....*GkZ
Post by Klaus Fehlker
0170 7d cc 85 5c bb ad 6a df fa b3 e5 c2 62 af dc ce
}..\..j.....b...
Post by Klaus Fehlker
0180 ee b1 c6 96 f2 9d 5b af fa 54 fd 85 d7 fd 4c d0
......[..T....L.
Post by Klaus Fehlker
0190 b0 60 a4 b0 b1 b1 0e 5a 0a f5 ea d0 8f 53 5f 70
.`.....Z.....S_p
Post by Klaus Fehlker
01a0 ab e1 4a f5 25 d7 b3 e0 36 8d 02 56 7b d5 d7 fc
..J.%...6..V{...
Post by Klaus Fehlker
01b0 f2 c7 95 ea 9b 4e c7 6a bb 7a bf 57 4e 51 7f 83
.....N.j.z.WNQ..
Post by Klaus Fehlker
01c0 38 a8 6f f9 85 d1 ea 6a 93 35 45 32 d4 3f 60 a6
8.o....j.5E2.?`.
Post by Klaus Fehlker
01d0 eb 8d 54 4e ee 25 47 a0 03 7e 7b e7 9d c2 96 ee
..TN.%G..~{.....
Post by Klaus Fehlker
01e0 de 30 9f 93 74 e2 bf 67 66 ba d4 77 5d fc 0a 42
.0..t..gf..w]..B
Post by Klaus Fehlker
01f0 4f 2c 95 9b b5 70 6b d2 12 9b 85 0f b7 89 a6 35
O,...pk........5
Post by Klaus Fehlker
No. Time Source Destination
Protocol
Info
236622 15:50:01.880737 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [RST, ACK] Seq=1 Ack=516078 Win=0 Len=0
Frame 236622 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516078 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x1023 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236620
The RTT to ACK the segment was: 0.000463000 seconds
No. Time Source Destination
Protocol
Info
236623 15:50:01.880860 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [RST, ACK] Seq=1 Ack=516590 Win=0 Len=0
Frame 236623 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516590 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x0e23 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236621
The RTT to ACK the segment was: 0.000460000 seconds
No. Time Source Destination
Protocol
Info
236624 15:50:01.980765 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [RST] Seq=1 Ack=516078 Win=0 Len=0
Frame 236624 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x1033 (correct)
No. Time Source Destination
Protocol
Info
236625 15:50:01.980943 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4072 [RST] Seq=1 Ack=516590 Win=0 Len=0
Frame 236625 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Post by Klaus Fehlker
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x0e33 (correct)
No. Time Source Destination
Protocol
Info
236626 15:50:02.095888 2.33.109.115 165.72.165.25
TCP
Post by Klaus Fehlker
4073 > http [SYN] Seq=0 Ack=0 Win=64240 Len=0 MSS=1460
Frame 236626 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 0, Ack: 0, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 64240
Checksum: 0xdb11 (correct)
Options: (8 bytes)
No. Time Source Destination
Protocol
Info
236627 15:50:02.141335 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4073 [SYN, ACK] Seq=0 Ack=1 Win=1460 Len=0 MSS=1460
Frame 236627 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Post by Klaus Fehlker
Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 1460
Checksum: 0x852c (correct)
Options: (8 bytes)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236626
The RTT to ACK the segment was: 0.045447000 seconds
No. Time Source Destination
Protocol
Info
236628 15:50:02.141448 2.33.109.115 165.72.165.25
TCP
Post by Klaus Fehlker
4073 > http [ACK] Seq=1 Ack=1 Win=64240 [CHECKSUM INCORRECT] Len=0
Frame 236628 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 1, Ack: 1, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64240
Checksum: 0xba10 (incorrect, should be 0xbcb3)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236627
The RTT to ACK the segment was: 0.000113000 seconds
No. Time Source Destination
Protocol
Info
236629 15:50:02.141761 2.33.109.115 165.72.165.25
HTTP
Post by Klaus Fehlker
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1
Frame 236629 (301 bytes on wire, 301 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 1, Ack: 1, Len: 247
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 248 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbb07 (incorrect, should be 0x8fc9)
Hypertext Transfer Protocol
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93dbdc
HTTP/1.1\r\n
Request Method: DELETE
Host: czcholsint004.prg-dc.dhl.com\r\n
User-Agent: SVN/1.2.0 (r14790) neon/0.24.7\r\n
Connection: TE\r\n
TE: trailers\r\n
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx\r\n
\r\n
No. Time Source Destination
Protocol
Info
236630 15:50:02.188235 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4073 [ACK] Seq=1 Ack=248 Win=6432 Len=0
Frame 236630 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Post by Klaus Fehlker
Seq: 1, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 6432
Checksum: 0x9d8d (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236629
The RTT to ACK the segment was: 0.046474000 seconds
No. Time Source Destination
Protocol
Info
236631 15:50:02.513670 165.72.165.25 2.33.109.115
HTTP
Post by Klaus Fehlker
HTTP/1.1 204 No Content
Frame 236631 (239 bytes on wire, 239 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Post by Klaus Fehlker
Seq: 1, Ack: 248, Len: 185
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Next sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 6432
Checksum: 0x3983 (correct)
Hypertext Transfer Protocol
HTTP/1.1 204 No Content\r\n
Response Code: 204
Date: Tue, 28 Jun 2005 13:44:30 GMT\r\n
Server: Apache/2.0.53 (Unix) mod_ssl/2.0.53 OpenSSL/0.9.7a DAV/2
SVN/1.1.4\r\n
Content-Length: 0\r\n
Content-Type: text/plain\r\n
\r\n
No. Time Source Destination
Protocol
Info
236632 15:50:02.626447 2.33.109.115 165.72.165.25
TCP
Post by Klaus Fehlker
4073 > http [ACK] Seq=248 Ack=186 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236632 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 248, Ack: 186, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 186 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbc)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236631
The RTT to ACK the segment was: 0.112777000 seconds
No. Time Source Destination
Protocol
Info
236633 15:50:17.522817 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4073 [FIN, ACK] Seq=186 Ack=248 Win=6432 Len=0
Frame 236633 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Post by Klaus Fehlker
Seq: 186, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 6432
Checksum: 0x9cd3 (correct)
No. Time Source Destination
Protocol
Info
236634 15:50:17.522876 2.33.109.115 165.72.165.25
TCP
Post by Klaus Fehlker
4073 > http [ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT] Len=0
Frame 236634 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbb)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236633
The RTT to ACK the segment was: 0.000059000 seconds
No. Time Source Destination
Protocol
Info
236635 15:51:34.060372 2.33.109.115 165.72.165.25
TCP
Post by Klaus Fehlker
4073 > http [FIN, ACK] Seq=248 Ack=187 Win=64055 [CHECKSUM INCORRECT]
Len=0
Frame 236635 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: http
(80),
Post by Klaus Fehlker
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbba)
No. Time Source Destination
Protocol
Info
236636 15:51:34.105175 165.72.165.25 2.33.109.115
TCP
Post by Klaus Fehlker
http > 4073 [RST] Seq=187 Ack=1085398113 Win=0 Len=0
Frame 236636 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Post by Klaus Fehlker
Seq: 187, Ack: 1085398113, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 187 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x99e5 (correct)
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse f|r Mail, Message, More +++
---------------------------------------------------------------------
--
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Matthew Sanderson
2005-07-13 05:30:07 UTC
Permalink
Hi Klaus,

Some semi-random things I noticed that are curious in the dump you sent:

1. Why does your dump claim there are packets with bad checksums? This
looks like an issue with the TCP/IP stack on either client or server or
both, or maybe incorrect decoding/verification of the checksums by
ethereal, or the network connectivity is *really* bad and that isn't being
corrected at the transport layer (or some other layer) for some reason. I
think this should be investigated.

Could it be that when you access the repository remotely, you do so using
some gateway or firewall or something which you don't use in other
circumstances, and that gateway or whatever is corrupting the packets so
that their checksums don't match?

If you use PPP or a VPN or something when connecting from your 'remote
sites', I would expect that thing to do its own error correction, so the
eventual decapsulated TCP/IP over Ethernet traffic on your LAN that you
captured and emailed should have correct checksums. And it doesn't.

How remote is 'remote'? What's your network topology?

If the checksums are bad too often, it would make sense for the receiving
end's TCP/IP stack to despair and reset the connection.

2. From looking at some Apache 2 source linked from Google's results page
for 'could not get next bucket brigade', it looks like that error is
printed when the DAV module cannot read the client's request data,
probably because the TCP connection was reset. So I think it's just a
symptom of the previous problem, not in itself a problem, so it should be
ignored.

HTH,

--matt

Matthew Sanderson
Senior Programmer (UNIX)
TCG Information Systems Pty Ltd
Sydney, Australia
***@formtrap.com
http://www.formtrap.com/
+61 (02) 8303 2407
Post by Klaus Fehlker
--- Urspr=FCngliche Nachricht ---
Betreff: Re: What causes "Connection reset by peer" errors?
Datum: 11 Jul 2005 10:27:33 -0500
sorry to bother you with this again but i am still stuck. Can somebod=
y
Post by Klaus Fehlker
say
if this is the right mailing list or is it rather a problem of Apache=
,
Post by Klaus Fehlker
or
even our network? As the subject says i have no idea what causes this
"connection reset by peer" error.
Any hint that brings me further is very much welcome!
This is just a wild guess, possibly totally wrong, but have you tried
playing with the 'http-timeout' parameter in your
~/.subversion/servers configuration file?
Hm, haven't tried it, yet, but could a bad client configuration make the
server send Resets?
What is SVN's usual behavior when the server sends a reset? Do you know w=
hat
Post by Klaus Fehlker
can cause a server sending a reset?
Klaus
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use
Apache
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on client-sid=
e.
Post by Klaus Fehlker
I
use
it from within the LAN as well as from remote sites with a poor
network
connection.
Unfortunately, large commits from the remote site sometimes break w=
ith
Post by Klaus Fehlker
the
message "Connection reset by peer". The Apache logs tell that the
server
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really kno=
w
Post by Klaus Fehlker
how
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal
(165.72.165.25 =3D
server). In frame 236629 the client sents a DELETE
*somethingcryptical*
but
the commit only consists of adds. Does that have to do with the err=
or?
Post by Klaus Fehlker
Many thinks for any help,
Klaus
[Tue Jun 28 17:05:17 2005] [info] [client 2.33.109.115] Access
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.=
jar
Post by Klaus Fehlker
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115]
(104)Connection
reset by peer: Could not get next bucket brigade [500, #0]
[Tue Jun 28 17:05:20 2005] [info] (32)Broken pipe: core_output_filt=
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=3Ddhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
[Tue Jun 28 17:05:20 2005] [info] [client 2.33.109.115] Access
No. Time Source Destination
Protocol
Info
236618 15:50:01.880031 165.72.165.25 2.33.109.115
TCP
http > 4072 [ACK] Seq=3D1 Ack=3D507374 Win=3D30660 Len=3D0
Frame 236618 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 507374, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507374 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xba62 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236585
The RTT to ACK the segment was: 0.086843000 seconds
No. Time Source Destination
Protocol
Info
236619 15:50:01.880230 165.72.165.25 2.33.109.115
TCP
http > 4072 [ACK] Seq=3D1 Ack=3D507886 Win=3D30660 Len=3D0
Frame 236619 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 507886, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 507886 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 30660
Checksum: 0xb862 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236587
The RTT to ACK the segment was: 0.084847000 seconds
No. Time Source Destination
Protocol
Info
236620 15:50:01.880274 2.33.109.115 165.72.165.25
HTTP
Continuation
Frame 236620 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 515566, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 515566 (relative sequence number)
Next sequence number: 516078 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0xd63c)
Hypertext Transfer Protocol
Data (512 bytes)
0000 2a 02 7a 78 52 2c 68 6c 12 01 e3 16 35 5e 6d 55
*.zxR,hl....5^mU
0010 8b 39 af b5 c9 e5 ae 76 08 ff 21 bd 01 e3 90 7d
.9.....v..!....}
0020 d3 12 8e 11 36 45 0e d4 05 07 ac 43 44 c8 7d 38
....6E.....CD.}8
0030 60 0d 47 cd 89 99 52 af 2a 53 e5 6c 5f 96 9b 63
`.G...R.*S.l_..c
0040 80 9c fd 99 b3 0b db 02 fe 3a 41 69 53 4a b9 f7
.........:AiSJ..
0050 a6 56 aa 55 1e 35 4e ad b6 8a 00 89 d7 7c bc ea
.V.U.5N......|..
0060 38 6b b6 fd 7a 1a 3f 29 6d a8 31 75 61 b3 c5 63
8k..z.?)m.1ua..c
0070 7b 2b 1e a5 a9 ce 33 f1 58 7e f7 a8 d6 84 45 ea
{+....3.X~....E.
0080 78 55 c9 42 b1 2e a9 09 dc 79 ac 4b ad b7 cc ed
xU.B.....y.K....
0090 f2 9a 1a c4 da 5e 75 22 b0 54 3f 50 1b 70 b7 2a
.....^u".T?P.p.*
00a0 b1 7f 77 5d 7c 23 a6 e9 5c 6b 50 1e db 13 22 56
..w]|#..\kP..."V
00b0 03 b2 38 54 d5 54 9f 74 80 ba 93 9f 73 6e 36 79
..8T.T.t....sn6y
00c0 02 36 14 50 35 4c d6 5a fe 23 3a bf 3e d4 dd 6c
.6.P5L.Z.#:.>..l
00d0 97 da cc 85 c9 50 43 03 38 e6 55 75 a2 8f 47 6d
.....PC.8.Uu..Gm
00e0 51 f5 56 88 17 1b 6c 3a 1b 3d 84 8b ce 0d c6 e6
Q.V...l:.=3D......
00f0 01 b5 90 6a 64 80 5b 53 9e 4f eb 38 da a5 22 dc
...jd.[S.O.8..".
0100 9d ee 1d 07 9b 3c 2a aa b6 b1 22 04 23 71 ec 4f
.....<*...".#q.O
0110 b6 b0 df 91 f4 42 62 87 83 0a 45 f8 e2 50 aa 53
.....Bb...E..P.S
0120 93 c8 e5 58 6e 91 bf da 04 8f 6c a5 12 13 4e e7
...Xn.....l...N.
0130 56 4b 9c 57 79 87 c4 29 d3 08 b1 02 ca ea 38 69
VK.Wy..)......8i
0140 c7 f7 4c 46 4b 5d ac 1a c6 0a 63 ad 77 f2 d1 d6
..LFK]....c.w...
0150 9b d5 b9 76 13 db 2c 18 4f 61 ad b3 3e 27 74 e1
...v..,.Oa..>'t.
0160 b5 13 99 ae 57 fd 48 9d ef 11 23 d4 05 29 de cc
....W.H...#..)..
0170 4a 1a ec 52 17 59 aa 10 b3 16 63 a6 ac eb 21 1c
J..R.Y....c...!.
0180 fb b1 ba c4 a3 2e 56 97 5a e9 8d 85 bd 35 c0 ab
......V.Z....5..
0190 2e 57 19 bc f0 15 ec 0e 20 b1 ee 8d ec eb 2a 42 .W......
.....*B
01a0 15 a1 c6 9e d2 ed b0 a9 35 ab ab d4 d5 0c e0 1a
........5.......
01b0 08 6f 30 82 a4 2e ba c3 ab 76 89 e5 0c ef 3a b8
.o0......v....:.
01c0 97 60 c4 46 25 d8 60 12 ed 31 dd 06 73 1c a2 dd
.`.F%.`..1..s...
01d0 a0 7e ca 00 6f 14 54 77 c8 c5 89 2e b2 9d 2e 0f
.~..o.Tw........
01e0 0a 27 45 ad 37 b3 35 ba 25 c9 1a f1 38 7e 37 9e
.'E.7.5.%...8~7.
01f0 bd 75 2c ec f8 39 b6 c7 af ec 0d 48 5e c3 a5 6e
.u,..9.....H^..n
No. Time Source Destination
Protocol
Info
236621 15:50:01.880400 2.33.109.115 165.72.165.25
HTTP
Continuation
Frame 236621 (566 bytes on wire, 566 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4072 (4072), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 516078, Ack: 1, Len: 512
Source port: 4072 (4072)
Destination port: http (80)
Sequence number: 516078 (relative sequence number)
Next sequence number: 516590 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbc10 (incorrect, should be 0x3d1d)
Hypertext Transfer Protocol
Data (512 bytes)
0000 77 ab 66 79 89 57 64 c8 93 3c ea 56 75 07 14 b8
w.fy.Wd..<.Vu...
0010 8a 2b 0e 31 76 75 59 be 37 58 ac 63 0a dc a5 ee
.+.1vuY.7X.c....
0020 66 0a dc 23 48 87 03 35 10 a2 f1 3d 8b 10 64 02
f..#H..5...=3D..d.
0030 63 63 8b 7c cf 17 63 8e 70 a9 07 04 dd f6 7d 5f
cc.|..c.p.....}_
0040 ef ea 0a cb ce e1 e9 ff 9f 95 26 8c 7d c8 ad 1e
..........&.}...
0050 54 7b 2d 4f 15 8f d1 83 91 c6 3a ff 8e ee 5f 26
T{-O......:..._&
0060 b2 07 81 e9 ad 6a 9f 9b 56 ab b6 a4 6e 1e 0f ae
.....j..V...n...
0070 6a 8a 44 43 f5 f9 8b 9a 22 3b 4a 1b aa 83 56 45
j.DC....";J...VE
0080 45 b5 73 1b 70 53 68 fb da 4d 41 3e be 95 f4 12
E.s.pSh..MA>....
0090 54 aa 45 ba 78 9f 4c 3d a2 f6 bb d5 2f d4 a3 82
T.E.x.L=3D..../...
00a0 46 75 4b 39 2e 8f 98 16 87 c9 f0 1c 27 73 06 5a
FuK9........'s.Z
00b0 9d a8 44 20 61 8e 66 f4 3a 0f 50 bf 54 4f 70 b8 ..D
a.f.:.P.TOp.
00c0 fd 64 1c 92 23 ed f2 aa a7 f8 e9 02 f5 2b 73 e8
.d..#........+s.
00d0 be f7 47 24 2c c0 cf 30 e0 67 19 c8 33 0c e4 d7
..G$,..0.g..3...
00e0 7c 76 cd a0 cf 07 2f ec 94 69 52 ef 30 85 d5 aa
|v..../..iR.0...
_wM\.
0100 e2 6c 40 5b cd 53 26 a8 d5 2b 55 bf 4f ca 2f ba
0110 9c ee 52 7f f0 a8 97 4d e7 37 90 98 fe 2a f4 de
..R....M.7...*..
0120 80 ac 70 34 ac d5 eb b1 bb 96 42 d8 77 df 84 fa
..p4......B.w...
0130 d7 39 6f bc 2d 28 b7 37 e5 fa 44 58 f0 ae 47 bd
.9o.-(.7..DX..G.
0140 c7 8d 06 af d5 6b 42 30 57 c8 7d ec 0b 7b 4b 82
.....kB0W.}..{K.
0150 64 d1 8a bd 2e 1a 5f 2a d6 bb b4 df 64 3d d4 73
d....._*....d=3D.s
0160 90 cc f0 0f d4 87 6c 3a ff 18 a3 c1 2a 47 6b 5a
......l:....*GkZ
0170 7d cc 85 5c bb ad 6a df fa b3 e5 c2 62 af dc ce
}..\..j.....b...
0180 ee b1 c6 96 f2 9d 5b af fa 54 fd 85 d7 fd 4c d0
......[..T....L.
0190 b0 60 a4 b0 b1 b1 0e 5a 0a f5 ea d0 8f 53 5f 70
.`.....Z.....S_p
01a0 ab e1 4a f5 25 d7 b3 e0 36 8d 02 56 7b d5 d7 fc
..J.%...6..V{...
01b0 f2 c7 95 ea 9b 4e c7 6a bb 7a bf 57 4e 51 7f 83
.....N.j.z.WNQ..
01c0 38 a8 6f f9 85 d1 ea 6a 93 35 45 32 d4 3f 60 a6
8.o....j.5E2.?`.
01d0 eb 8d 54 4e ee 25 47 a0 03 7e 7b e7 9d c2 96 ee
..TN.%G..~{.....
01e0 de 30 9f 93 74 e2 bf 67 66 ba d4 77 5d fc 0a 42
.0..t..gf..w]..B
01f0 4f 2c 95 9b b5 70 6b d2 12 9b 85 0f b7 89 a6 35
O,...pk........5
No. Time Source Destination
Protocol
Info
236622 15:50:01.880737 165.72.165.25 2.33.109.115
TCP
http > 4072 [RST, ACK] Seq=3D1 Ack=3D516078 Win=3D0 Len=3D0
Frame 236622 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516078 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x1023 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236620
The RTT to ACK the segment was: 0.000463000 seconds
No. Time Source Destination
Protocol
Info
236623 15:50:01.880860 165.72.165.25 2.33.109.115
TCP
http > 4072 [RST, ACK] Seq=3D1 Ack=3D516590 Win=3D0 Len=3D0
Frame 236623 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a6, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 516590 (relative ack number)
Header length: 20 bytes
Flags: 0x0014 (RST, ACK)
Window size: 0
Checksum: 0x0e23 (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236621
The RTT to ACK the segment was: 0.000460000 seconds
No. Time Source Destination
Protocol
Info
236624 15:50:01.980765 165.72.165.25 2.33.109.115
TCP
http > 4072 [RST] Seq=3D1 Ack=3D516078 Win=3D0 Len=3D0
Frame 236624 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 516078, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x1033 (correct)
No. Time Source Destination
Protocol
Info
236625 15:50:01.980943 165.72.165.25 2.33.109.115
TCP
http > 4072 [RST] Seq=3D1 Ack=3D516590 Win=3D0 Len=3D0
Frame 236625 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:60:fb:51:62:a5, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4072
(4072),
Seq: 1, Ack: 516590, Len: 0
Source port: http (80)
Destination port: 4072 (4072)
Sequence number: 1 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x0e33 (correct)
No. Time Source Destination
Protocol
Info
236626 15:50:02.095888 2.33.109.115 165.72.165.25
TCP
4073 > http [SYN] Seq=3D0 Ack=3D0 Win=3D64240 Len=3D0 MSS=3D1460
Frame 236626 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 0, Ack: 0, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 64240
Checksum: 0xdb11 (correct)
Options: (8 bytes)
No. Time Source Destination
Protocol
Info
236627 15:50:02.141335 165.72.165.25 2.33.109.115
TCP
http > 4073 [SYN, ACK] Seq=3D0 Ack=3D1 Win=3D1460 Len=3D0 MSS=3D146=
0
Post by Klaus Fehlker
Frame 236627 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 1460
Checksum: 0x852c (correct)
Options: (8 bytes)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236626
The RTT to ACK the segment was: 0.045447000 seconds
No. Time Source Destination
Protocol
Info
236628 15:50:02.141448 2.33.109.115 165.72.165.25
TCP
4073 > http [ACK] Seq=3D1 Ack=3D1 Win=3D64240 [CHECKSUM INCORRECT] =
Len=3D0
Post by Klaus Fehlker
Frame 236628 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 1, Ack: 1, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64240
Checksum: 0xba10 (incorrect, should be 0xbcb3)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236627
The RTT to ACK the segment was: 0.000113000 seconds
No. Time Source Destination
Protocol
Info
236629 15:50:02.141761 2.33.109.115 165.72.165.25
HTTP
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93d=
bdc
Post by Klaus Fehlker
HTTP/1.1
Frame 236629 (301 bytes on wire, 301 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 1, Ack: 1, Len: 247
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 248 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 64240
Checksum: 0xbb07 (incorrect, should be 0x8fc9)
Hypertext Transfer Protocol
DELETE
/nps-svn/NPS-Application/!svn/act/aad32169-0229-2c4e-8714-a2d51d93d=
bdc
Post by Klaus Fehlker
HTTP/1.1\r\n
Request Method: DELETE
Host: czcholsint004.prg-dc.dhl.com\r\n
User-Agent: SVN/1.2.0 (r14790) neon/0.24.7\r\n
Connection: TE\r\n
TE: trailers\r\n
Authorization: Basic xxxxxxxxxxxxxxxxxxxxx\r\n
\r\n
No. Time Source Destination
Protocol
Info
236630 15:50:02.188235 165.72.165.25 2.33.109.115
TCP
http > 4073 [ACK] Seq=3D1 Ack=3D248 Win=3D6432 Len=3D0
Frame 236630 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Seq: 1, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 6432
Checksum: 0x9d8d (correct)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236629
The RTT to ACK the segment was: 0.046474000 seconds
No. Time Source Destination
Protocol
Info
236631 15:50:02.513670 165.72.165.25 2.33.109.115
HTTP
HTTP/1.1 204 No Content
Frame 236631 (239 bytes on wire, 239 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Seq: 1, Ack: 248, Len: 185
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 1 (relative sequence number)
Next sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 6432
Checksum: 0x3983 (correct)
Hypertext Transfer Protocol
HTTP/1.1 204 No Content\r\n
Response Code: 204
Date: Tue, 28 Jun 2005 13:44:30 GMT\r\n
Server: Apache/2.0.53 (Unix) mod_ssl/2.0.53 OpenSSL/0.9.7a DAV/=
2
Post by Klaus Fehlker
SVN/1.1.4\r\n
Content-Length: 0\r\n
Content-Type: text/plain\r\n
\r\n
No. Time Source Destination
Protocol
Info
236632 15:50:02.626447 2.33.109.115 165.72.165.25
TCP
4073 > http [ACK] Seq=3D248 Ack=3D186 Win=3D64055 [CHECKSUM INCORRE=
CT] Len=3D0
Post by Klaus Fehlker
Frame 236632 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 248, Ack: 186, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 186 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbc)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236631
The RTT to ACK the segment was: 0.112777000 seconds
No. Time Source Destination
Protocol
Info
236633 15:50:17.522817 165.72.165.25 2.33.109.115
TCP
http > 4073 [FIN, ACK] Seq=3D186 Ack=3D248 Win=3D6432 Len=3D0
Frame 236633 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Seq: 186, Ack: 248, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 186 (relative sequence number)
Acknowledgement number: 248 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 6432
Checksum: 0x9cd3 (correct)
No. Time Source Destination
Protocol
Info
236634 15:50:17.522876 2.33.109.115 165.72.165.25
TCP
4073 > http [ACK] Seq=3D248 Ack=3D187 Win=3D64055 [CHECKSUM INCORRE=
CT] Len=3D0
Post by Klaus Fehlker
Frame 236634 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbbb)
SEQ/ACK analysis
This is an ACK to the segment in frame: 236633
The RTT to ACK the segment was: 0.000059000 seconds
No. Time Source Destination
Protocol
Info
236635 15:51:34.060372 2.33.109.115 165.72.165.25
TCP
4073 > http [FIN, ACK] Seq=3D248 Ack=3D187 Win=3D64055 [CHECKSUM IN=
CORRECT]
Post by Klaus Fehlker
Len=3D0
Frame 236635 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 00:08:02:e4:d8:4f, Dst: 00:00:0c:07:ac:01
165.72.165.25 (165.72.165.25)
Transmission Control Protocol, Src Port: 4073 (4073), Dst Port: htt=
p
Post by Klaus Fehlker
(80),
Seq: 248, Ack: 187, Len: 0
Source port: 4073 (4073)
Destination port: http (80)
Sequence number: 248 (relative sequence number)
Acknowledgement number: 187 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 64055
Checksum: 0xba10 (incorrect, should be 0xbbba)
No. Time Source Destination
Protocol
Info
236636 15:51:34.105175 165.72.165.25 2.33.109.115
TCP
http > 4073 [RST] Seq=3D187 Ack=3D1085398113 Win=3D0 Len=3D0
Frame 236636 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:12:80:97:3c:20, Dst: 00:08:02:e4:d8:4f
Internet Protocol, Src Addr: 165.72.165.25 (165.72.165.25), Dst Add=
2.33.109.115 (2.33.109.115)
Transmission Control Protocol, Src Port: http (80), Dst Port: 4073
(4073),
Seq: 187, Ack: 1085398113, Len: 0
Source port: http (80)
Destination port: 4073 (4073)
Sequence number: 187 (relative sequence number)
Header length: 20 bytes
Flags: 0x0004 (RST)
Window size: 0
Checksum: 0x99e5 (correct)
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse f|r Mail, Message, More +++
---------------------------------------------------------------------
--
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
---------------------------------------------------------------------
Klaus Fehlker
2005-07-13 14:33:59 UTC
Permalink
Hi Matthew,
Post by Matthew Sanderson
1. Why does your dump claim there are packets with bad checksums? This
looks like an issue with the TCP/IP stack on either client or server or
both, or maybe incorrect decoding/verification of the checksums by
ethereal, or the network connectivity is *really* bad and that isn't being
corrected at the transport layer (or some other layer) for some reason. I
think this should be investigated.
I dumped the traffic of a successful "local" commit and it shows "checksum
incorrect" for each packet sent by the client. I dumped it on the client, so
there is no interference with the network. Thus, i suppose it is some
Ethereal bug, would you agree?
Can it be that checksum computation is done on hardware and the software
beforehand just fills it with random bytes?
Post by Matthew Sanderson
Could it be that when you access the repository remotely, you do so using
some gateway or firewall or something which you don't use in other
circumstances, and that gateway or whatever is corrupting the packets so
that their checksums don't match?
We have a packetshaper in between dropping packets depending on the load.
But this should be transparent to Apache / SVN isn't it?
Post by Matthew Sanderson
If you use PPP or a VPN or something when connecting from your 'remote
sites', I would expect that thing to do its own error correction, so the
eventual decapsulated TCP/IP over Ethernet traffic on your LAN that you
captured and emailed should have correct checksums. And it doesn't.
We have no PPP or VPN but a couple of switches and other stuff. I am about
to find out details.
Post by Matthew Sanderson
If the checksums are bad too often, it would make sense for the receiving
end's TCP/IP stack to despair and reset the connection.
2. From looking at some Apache 2 source linked from Google's results page
for 'could not get next bucket brigade', it looks like that error is
printed when the DAV module cannot read the client's request data,
probably because the TCP connection was reset. So I think it's just a
symptom of the previous problem, not in itself a problem, so it should be
ignored.
So in the end it would be good to see what the server receives and not what
the client sends. I try to get that asap.
Unfortunately, the remote host is hard to access and i therefore cannot
easily reproduce the error :(
Post by Matthew Sanderson
HTH,
Thanks,
Klaus
Post by Matthew Sanderson
--matt
Matthew Sanderson
Senior Programmer (UNIX)
TCG Information Systems Pty Ltd
Sydney, Australia
http://www.formtrap.com/
+61 (02) 8303 2407
Post by Klaus Fehlker
--- Ursprüngliche Nachricht ---
Betreff: Re: What causes "Connection reset by peer" errors?
Datum: 11 Jul 2005 10:27:33 -0500
Post by Klaus Fehlker
sorry to bother you with this again but i am still stuck. Can
somebody
Post by Klaus Fehlker
say
Post by Klaus Fehlker
if this is the right mailing list or is it rather a problem of
Apache,
Post by Klaus Fehlker
or
Post by Klaus Fehlker
even our network? As the subject says i have no idea what causes
this
Post by Klaus Fehlker
Post by Klaus Fehlker
"connection reset by peer" error.
Any hint that brings me further is very much welcome!
This is just a wild guess, possibly totally wrong, but have you tried
playing with the 'http-timeout' parameter in your
~/.subversion/servers configuration file?
Hm, haven't tried it, yet, but could a bad client configuration make the
server send Resets?
What is SVN's usual behavior when the server sends a reset? Do you know
what
Post by Klaus Fehlker
can cause a server sending a reset?
Klaus
Post by Klaus Fehlker
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use
Apache
Post by Klaus Fehlker
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on
client-side.
Post by Klaus Fehlker
I
Post by Klaus Fehlker
use
it from within the LAN as well as from remote sites with a poor
network
Post by Klaus Fehlker
connection.
Unfortunately, large commits from the remote site sometimes break
with
Post by Klaus Fehlker
the
Post by Klaus Fehlker
message "Connection reset by peer". The Apache logs tell that the
server
Post by Klaus Fehlker
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really
know
Post by Klaus Fehlker
how
Post by Klaus Fehlker
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal
(165.72.165.25 =
Post by Klaus Fehlker
server). In frame 236629 the client sents a DELETE
*somethingcryptical*
Post by Klaus Fehlker
but
the commit only consists of adds. Does that have to do with the
error?
Post by Klaus Fehlker
Post by Klaus Fehlker
Many thinks for any help,
Klaus
[Tue Jun 28 17:05:17 2005] [info] [client 2.33.109.115] Access
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.jar
Post by Klaus Fehlker
Post by Klaus Fehlker
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115]
(104)Connection
Post by Klaus Fehlker
reset by peer: Could not get next bucket brigade [500, #0]
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=dhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
[Tue Jun 28 17:05:20 2005] [info] [client 2.33.109.115] Access
[..]
--
GMX DSL = Maximale Leistung zum minimalen Preis!
2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Matthew Sanderson
2005-07-15 02:58:20 UTC
Permalink
G'day Klaus, replying below the 'rude' way, sorry.

--matt
Post by Klaus Fehlker
I dumped the traffic of a successful "local" commit and it shows "checksum
incorrect" for each packet sent by the client. I dumped it on the client, so
there is no interference with the network. Thus, i suppose it is some
Ethereal bug, would you agree?
Can it be that checksum computation is done on hardware and the software
beforehand just fills it with random bytes?
Yeah, if your NIC does so-called hardware checksum offload then libpcap
will see the packet with uninitialised checksums, and according to the
Ethereal FAQ at:
http://www.ethereal.com/faq.html#q5.14
this will cause bogus error messages when there's nothing really wrong.
Apparently, libpcap doesn't realise that the NIC's doing checksum offload
so libpcap shouldn't validate the checksums. You could try disabling
checksum offload. Someone should hack on libpcap...

If your NIC isn't doing checksum offload then I suppose libpcap's checksum
validation is broken. Beware, just cos the NIC claims to support checksum
offload doesn't mean your OS's driver for it is using that feature - the
firmware may implement it buggily, or the OS doesn't support checksum
offload, or some similar problem.

But so this checksum problem also looks like a seperate issue, unrelated
to your original problem re intermittently failing commits. So on to the
next candidate, packet loss...
Post by Klaus Fehlker
We have a packetshaper in between dropping packets depending on the load.
But this should be transparent to Apache / SVN isn't it?
Yup, TCP will notice the missing packets, retransmit them and the apps
will just notice lower throughput, that's all - within reason. If you drop
a *lot* of packets then this might be the source of your problems. But
you'd have to drop a lot of packets, not just the odd one here and there.
Once the three-way handshake is complete, TCP doesn't give up on the
connection easily; things just get reeeaally sloooow.

Do you absolutely need to drop packets? That sounds scary. Could you try
disabling this traffic shaping and see if that fixes things? I think this
could well be the source of your problems.
Post by Klaus Fehlker
So in the end it would be good to see what the server receives and not what
the client sends. I try to get that asap.
I reckon get both, and compare them. Or even, simultaneously log packet
data at the client, at the server, and also at selected point(s)
approximately evenly spaced (in terms of hops) in between client and
server, then compare the captured data, and thus you can do a binary
search to find the bad gateway/router/whatever.

Since you say in next later post that you've proved that this problem
isn't exclusive to Subversion, shall we take this thread off-list?

I'm pretty sure that the problem is with your network, or maybe with the
TCP/IP stacks involved, but almost certainly not with SVN, Apache or
libneon etc directly.

HTH,

--matt

Matthew Sanderson
Senior Programmer (UNIX)
TCG Information Systems Pty Ltd
Sydney, Australia
***@formtrap.com
http://www.formtrap.com/
+61 (02) 8303 2407

Klaus Fehlker
2005-07-14 10:08:51 UTC
Permalink
Post by k***@collab.net
This is just a wild guess, possibly totally wrong, but have you tried
playing with the 'http-timeout' parameter in your
~/.subversion/servers configuration file?
I set it manually to a few hours but it crashes already withing 3-4 minutes.
Any more ideas?
- Nobody else accesses the server during the commit.
- Nothing else works on the client during the commit.
- I am using Apache 2.0.53 and SVN client/server 1.1.4 now.
- Apache's AccessLog reports an internal error (500).
- Apache's error log says:

[Thu Jul 14 12:43:32 2005] [info] [client 2.33.109.163] Access granted: -
PUT test:/ProgramFiles.zip-from-FRONEWD00004_1
[Thu Jul 14 12:45:46 2005] [error] [client 2.33.109.163] (104)Connection
reset by peer: Could not get next bucket brigade [500, #0]
[Thu Jul 14 12:45:46 2005] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Thu Jul 14 12:45:46 2005] [info] [client 2.33.109.163] Access granted: -
DELETE test:

Is there anything i can do?

Klaus
Post by k***@collab.net
-----Original Message-----
Sent: Mittwoch, 29. Juni 2005 18:13
Subject: What causes "Connection reset by peer" errors?
Hi,
I have problems using my repository from certain locations. I use
Apache
2.0.54 with Subversion 1.1.4 on server-side and 1.2.0 on client-side.
I
use
it from within the LAN as well as from remote sites with a poor
network
connection.
Unfortunately, large commits from the remote site sometimes break with
the
message "Connection reset by peer". The Apache logs tell that the
server
could not get the next buckade brigade - whatever that means?!
I suspect it to be some kind of network error but do not really know
how
to
make sure. There is no proxy in between.
Below i appended the network traffic dumped with Ethereal
(165.72.165.25 =
server). In frame 236629 the client sents a DELETE
*somethingcryptical*
but
the commit only consists of adds. Does that have to do with the error?
Many thinks for any help,
Klaus
[Tue Jun 28 17:05:17 2005] [info] [client 2.33.109.115] Access
'kFehlker' PUT
NPS-Application:/NPS0.1_trunk/infrastructure/tools/TMS-development-
environment/envdev/eclipse/plugins/org.eclipse.debug.ui_3.0.1/dtui.jar
[Tue Jun 28 17:05:20 2005] [error] [client 2.33.109.115]
(104)Connection
reset by peer: Could not get next bucket brigade [500, #0]
writing data to the network
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(337): [client
2.33.109.115] [20767] auth_ldap authenticate: using URL
ldap://ldap.dhl.com:389/o=dhl.com
[Tue Jun 28 17:05:20 2005] [debug] mod_auth_ldap.c(411): [client
2.33.109.115] [20767] auth_ldap authenticate: accepting kFehlker
[Tue Jun 28 17:05:20 2005] [info] [client 2.33.109.115] Access
--
GMX DSL = Maximale Leistung zum minimalen Preis!
2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl
Ben Collins-Sussman
2005-07-14 15:13:08 UTC
Permalink
Post by Klaus Fehlker
Is there anything i can do?
Perhaps try the latest version of apache and svn?
Continue reading on narkive:
Loading...