Ryan Underwood wrote: > On Sat, Feb 18, 2006 at 09:01:07PM -0600, Ryan Underwood wrote: >> I've been observing this for several months now. The token loss almost >> always corresponds with a period of high fileserver load. For example, >> moving several ripped CDs to the fileserver while playing another one. >> Or when several machines launch their scheduled backup scripts at the >> same time. No, there is nothing running 'unlog'. I can keep the token >> around for weeks if I don't bother the fileserver too much. A simple >> 'aklog' gets the token again, but any AFS operation that was going on >> aborts due to the lack of tokens. I have a cornucopia of Linux 2.6 >> versions, but the fileserver and clients are all OpenAFS 1.4.0. > > So, what would be helpful to track this down? Since the client is in > charge of the tokens, it seems that the problem might be in the client > somewhere, except for the correlation of the token-loss events with a > loaded fileserver. I've never had to debug AFS before, and only have > so many hours in the day, so bear with me.
Ryan: Tokens can be lost because of either local issues such as the pag being cleared via an 'unlog' or a new pag being allocated. The tokens could be lost due to a bug in the client. Or the tokens could be lost because the server has reported to the client that the tokens cannot be used due to RXKADUNKNOWNKEY, RXKADBADTICKET, RXKADEXPIRED, etc. The first thing you need to determine is which it is. If the server is the trigger of the token loss, an event will be written to the cache manager trace log within the kernel (if the log is active.) You can control the use of the cm event logging with the 'fstrace' options 'lsset', 'setset' and 'dump'. Activate the event logging and when the problem occurs, dump the output to a file and search it for a tokens discarded message. If found, the message will indicate the error value that caused the tokens to be cleared. Depending on why the tokens are being cleared there are different next steps. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
