[OpenAFS] connection timeouts
Derrick J Brashear
Mon, 22 May 2006 12:37:19 -0400 (EDT)
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.andrew.cmu.edu id k4MGbMWN017947
Widereply pruned. Ick.
On Mon, 22 May 2006, Juha [UTF-8] J=E4ykk=E4 wrote:
> I'll send the fileserver logs upon request: it is over 100kB long, so I
> won't email it to the list (and won't publish an URL on the list either=
> I can, however, immediately say that the fileserver log never shows the
> IP of the client. Is this normal?
> Here is one more thing: tcpdump of a "fs checkservers":
> 12:36:59.013846 IP lagrange.tfy.utu.fi.afs3-callback > dirac.tfy.utu.f=
i.afs3-fileserver: rx data fs call op#1054934366 (44)
So is the client sad or is tcpdump?
There's no RPC "1054934366"
> 12:37:02.015633 IP dirac.tfy.utu.fi.afs3-fileserver >=20
> lagrange.tfy.utu.fi.afs3-callback: rx abort (32)
Using -s 1500 -x would provide packet payloads. The last 32 bits of the=20
abort is an error code. I bet it would be -455 (RXGEN_OPCODE), I think=20
that's ffff fe38
> Connection from host 220.127.116.11, port 7001, Cuid 83aaa7c0/4dff9bc,
> error 19270409 serial 6, natMTU 1444, flags pktCksum, security index 2=
> server conn rxkad: level clear, flags pktCksum
> Received 0 bytes in 0 packets
> Sent 0 bytes in 0 packets
> call 0: # 182, state precall, mode: error
Ok, lagrange.tfy.utu.fi is 18.104.22.168 and that connection is mode=20