[19324] in Kerberos_V5_Development
Re: What is kinit waiting for?
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Dec 14 10:39:48 2015
To: Wang Weijun <weijun.wang@oracle.com>, krbdev@mit.edu
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <566EE2B5.9000108@mit.edu>
Date: Mon, 14 Dec 2015 10:39:33 -0500
MIME-Version: 1.0
In-Reply-To: <81B48B10-4FDF-4D56-AD3C-B2416C4BC732@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 12/14/2015 03:50 AM, Wang Weijun wrote:
> [12207] 1450082324.188447: Received answer (645 bytes) from dgram 127.0.0.1:9090
> [12207] 1450082384.195594: Response was not from master KDC
> As you can see, after "Received answer (645 bytes) from dgram 127.0.0.1:9090", the tool waited for another 1 minute and printed out "Response was not from master KDC". What does this mean? The krb5.conf is simply
> [realms]
> R = {
> kdc = 127.0.0.1:9090
> }
Most likely kinit is performing a SRV query to find out if the response
was from a master KDC, and it is timing out. There are two known
problems at play here:
http://krbdev.mit.edu/rt/Ticket/Display.html?id=7721
http://krbdev.mit.edu/rt/Ticket/Display.html?id=6782
You can suppress the SRV query by defining a master_kdc value in the
realm configuration (there is, unfortunately, no way to say "there are
no master KDCs" at present) or by setting dns_lookup_kdc = false in
[libdefaults].
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
