[OpenAFS-devel] "Lost contact with file server" problems
Derrick J Brashear
shadow@dementia.org
Fri, 26 Aug 2005 13:48:49 -0400 (EDT)
On Mon, 22 Aug 2005, Jeffrey Altman wrote:
>>> The other thing is: it is the _client_ which sends the first ABORT in
>>> response to a challenge....
This is the interesting bit.
>> I've also captured the 'self-healing' of the client state, although I'm
>> not able to make something of it myself. The full trace is at
>>
>> http://www.e18.physik.tu-muenchen.de/~rkuhn/openafs.cap
>>
>> It seems that 118 minutes after the failure the client makes a get-time
>> call which succeeds, and then everything is happy again.
>>
>> Ciao,
>> Roland
>
> I simply interpret that to mean that after 118 minutes the client
> finally dumps the token and starts to make unencrypted file server
> requests.
>
> What I am seeing here is that the rx libary is detecting that the
> token is expired. It sends an abort to the server which simply
> marks the client's connection in an error state. Each subsequent
> request from the client on that connection is responded to with the
> expired token abort code.
The client code, though, in rxkad_client, doesn't appear to be able to
generate one of these.