On Monday, May 22, 2006 12:37:19 PM -0400 Derrick J Brashear
<[EMAIL PROTECTED]> wrote:
Widereply pruned. Ick.
On Mon, 22 May 2006, Juha [UTF-8] Jäykkä 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.fi.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 >
lagrange.tfy.utu.fi.afs3-callback: rx abort (32)
Using -s 1500 -x would provide packet payloads. The last 32 bits of the
abort is an error code. I bet it would be -455 (RXGEN_OPCODE), I think
that's ffff fe38
Connection from host 130.232.104.188, 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 130.232.104.188 and that connection is mode
error.
And error 19270409 is RXKADEXPIRED, which at least does not refute your
theory that the problem went away when the tickets expired.
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
