OK, I have it again. User reports inability to log in. $ kas -a dsakfksda Administrator's (dsakfksda) Password: ka> exa useraccount examine: ticket contained unknown key version number getting information for useraccount.
So: $ udebug 128.214.88.114 7004 -long Host's addresses are: 128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1 Host's 128.214.88.114 time is Wed Apr 14 13:01:35 2010 Local time is Wed Apr 14 13:01:35 2010 (time differential 0 secs) Last yes vote for 128.214.58.174 was 14 secs ago (sync site); Last vote started 13 secs ago (at Wed Apr 14 13:01:22 2010) Local db version is 1271074432.4 I am not sync site Lowest host 128.214.58.174 was set 14 secs ago Sync host 128.214.58.174 was set 14 secs ago Sync site's db version is 1271074432.4 0 locked pages, 0 of them for write Server (128.214.58.174): (db 0.0) last vote rcvd 165054 secs ago (at Mon Apr 12 15:10:41 2010), last beacon sent 165054 secs ago (at Mon Apr 12 15:10:41 2010), last vote was no dbcurrent=0, up=1 beaconSince=1 $ udebug 128.214.58.174 7004 -long Host's addresses are: 128.214.58.174 Host's 128.214.58.174 time is Wed Apr 14 13:01:50 2010 Local time is Wed Apr 14 13:01:54 2010 (time differential 4 secs) Last yes vote for 128.214.58.174 was 12 secs ago (sync site); Last vote started 12 secs ago (at Wed Apr 14 13:01:42 2010) Local db version is 1271074432.4 I am sync site until 47 secs from now (at Wed Apr 14 13:02:41 2010) (2 servers) Recovery state 1f Sync site's db version is 1271074432.4 0 locked pages, 0 of them for write Last time a new db version was labelled was: 164878 secs ago (at Mon Apr 12 15:13:56 2010) Server (128.214.88.114 10.0.0.3 172.16.0.1 172.17.0.1 172.18.0.1): (db 1271074432.4) last vote rcvd -3 secs ago (at Wed Apr 14 13:01:57 2010), last beacon sent -3 secs ago (at Wed Apr 14 13:01:57 2010), last vote was yes dbcurrent=1, up=1 beaconSince=1 Nothing obvious - at least to my untrained eye. Using kas specifically against 128.214.58.174 (the sunx86_510 OpenAFS host) reproduces the error with this account. Using kas specifically against 128.214.88.114 (the sun4x_58 IBM AFS host) shows correct information, however. bos restart 128.214.58.174 kaserver made the problem go away. There is no indication of anything unusual in the AuthLog of 128.214.58.174. All pointers welcome. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish & / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE ATTACHMENTS _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
