On 08/18/2018 01:53 AM, Chris Hecker wrote: > I just got this again today, this time instead of EBUSY, the libkadm5 > client got "Cannot resolve network address for admin server in requested > realm (43787576)". Same "The referenced context has expired" stuff in > kadmind.log. I'm confused about the kadmind.log lines...I can see the > client having a problem due to timeouts or paging or whatever, but why > would the kadmind print that stuff in this case?
>> Aug 16 16:17:12 domain.com kadmind[31118](Error): check_rpcsec_auth: >> failed inquire_context, stat=786432 >> Aug 16 16:17:12 domain.com kadmind[31118](Notice): Authentication >> attempt failed: x.x.x.x, GSS-API error strings are: >> Aug 16 16:17:12 domain.com kadmind[31118](Notice): The referenced >> context has expired These errors look like they might be associated with the previous connection expiring, rather than the new connection failing. I don't have much insight into why you're getting EBUSY or KRB5_REALM_CANT_RESOLVE when connecting to kadmind on the the local host. ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
