"Ticket expired" when KDC gets sluggish
Brian J. Murrell
brian at interlinx.bc.ca
Sat Apr 3 09:28:14 EDT 2010
Every 12 hours at noon and midnight, my KDC is backed up. That end up
driving the load on that machine up and it can become quite slow to
respond.
What is interesting (for some value of "interesting" about that is that
ever since my upgrade from Ubuntu Hardy (kerberos version 1.6-beta1) to
Ubuntu Lucid (kerberos version 1.8-alpha1) on that machine, when this
backup does start and the machine does become sluggish, I start to see
the following messages:
00:00:04 krb5kdc TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 2001:1234:123:0:123:1234:1234:1234: PROCESS_TGS: authtime 0, <unknown client> for <unknown server>, Ticket expired
00:00:05 krb5kdc TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 2001:1234:123:0:123:1234:1234:1234: PROCESS_TGS: authtime 0, <unknown client> for <unknown server>, Ticket expired
[ 4 repeats deleted ]
00:00:53 krb5kdc TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 2001:1234:123:0:123:1234:1234:1234: PROCESS_TGS: authtime 0, <unknown client> for <unknown server>, Ticket expired
[ 5 repeats deleted ]
I wonder if perhaps there is some configurable timeout value I can crank
up to give the sluggish KDC more time to do it's business.
Or perhaps I am misunderstanding the nature of the problem?
Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mailman.mit.edu/pipermail/kerberos/attachments/20100403/435dabfd/attachment.bin
More information about the Kerberos
mailing list