Assertion failed w/krb5-1.4.1 on FreeBSD-5.3
Dennis Davis
D.H.Davis at bath.ac.uk
Thu Apr 28 11:05:32 EDT 2005
On Wed, 27 Apr 2005, Jeff Aitken wrote:
>Date: Wed, 27 Apr 2005 17:51:10 -0400
>From: Jeff Aitken <jaitken at aitken.com>
>To: kerberos at mit.edu
>Subject: Assertion failed w/krb5-1.4.1 on FreeBSD-5.3
>
>I recently installed a new FreeBSD-5.3 system designed to
>function as a master KDC. I then built and installed krb5-1.4.1.
>Initially, I ran ./configure with:
>
> --enable-shared --enable-static --without-krb4
>
>After installation, I could not run krb5kdc due to a failed
>assertion. A bit of googling led me to add the following to
>./configure:
>
> --disable-thread-support
>
>After rebuilding and reinstalling, things seemed to work. I was
>able to run krb5kdc (and kadmind), and am able to log in remotely
>with ssh using kerberos for authenticaion. I am also able to use
>'ksu' to become root. However, when I exit the root shell, I get
>the following error message:
>
> Assertion failed: ((&_m->os)->initialized == K5_MUTEX_DEBUG_INITIALIZED),
> function krb5_fcc_destroy, file cc_file.c, line 1526.
>
>This doesn't appear to be critical at first glance, but I'm
>wondering what else might not work properly. Based on some
>additional googling, I tried rebuilding with:
>
> --disable-shared --enable-static --without-krb4 --disable-thread-support
>
>but got the same result. Any ideas?
No, but I'm seeing similar errors on OpenBSD3.5 & OpenBSD3.6 with
both krb5-1.4 and krb5-1.4.1. I haven't tried running the kdc, but
both kinit and klist give errors similar to the above. However both
commands seem to work OK.
I've compiled with:
--disable-shared --enable-static --disable-thread-support
The --disable-shared is there to avoid any possible clashes with the
installed Heimdal kerberosV libraries. I've had trouble with this
in the past.
I *don't* see these problems with krb5-1.4 and krb5-1.4.1 on an
(obsolete) OpenBSD3.3 system.
My gut feeling (ie I could well be completely wrong) is that the
--disable-thread-support argument to configure isn't being fully
obeyed and some thread support is being picked up. I haven't even
thought about how I'd look into this.
--
Dennis Davis, BUCS, University of Bath, Bath, BA2 7AY, UK
D.H.Davis at bath.ac.uk Phone: +44 1225 386101
More information about the Kerberos
mailing list