MIT Kerberos kadmind unable to start...

From: Sean Chittenden (sean@chittenden.org)
Date: 01/27/02 

Date: Sat, 26 Jan 2002 20:09:44 -0800
From: Sean Chittenden <sean@chittenden.org>
To: freebsd-security@freebsd.org

I just upgraded to 1.2.3 and thought it'd be a nice idea to kill and
restart the new kadmin and krb5kdc's, however, now I'm getting the
following error:

# /usr/local/sbin/kadmind
kadmind: Cannot set GSS-API authentication names.
kadmind in free(): warning: chunk is already free
kadmind in free(): warning: chunk is already free

Anyone else having similar problems? I've been able to reproduce this
on two different boxes and am now down both of my slave KDCs. <:~(
Anyone have any ideas? -sc 

-- 
Sean Chittenden
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: Solaris 10
    ... > unable to get kadmind to start. ... > Ignore this warning if this system is not a master KDC. ... > Anyone here successfully setup kerberos on Solaris 10? ...
    (comp.protocols.kerberos)
  • Re: MIT Kerberos kadmind unable to start... [RESOLVED]
    ... > restart the new kadmin and krb5kdc's, however, now I'm getting the ... > kadmind: ... > kadmind in free: warning: chunk is already free ...
    (FreeBSD-Security)
  • logging to stderr
    ... At startup, "kadmind" outputs: ... kadmind: cannot parse <STDERR> ... warning - logging entry syntax error ...
    (comp.protocols.kerberos)