Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jul 2018 22:26:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 229939] security/krb5: "krb5kdc: cannot initialize realm <REALM>" on boot with local LDAP
Message-ID:  <bug-229939-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229939

            Bug ID: 229939
           Summary: security/krb5: "krb5kdc: cannot initialize realm
                    <REALM>" on boot with local LDAP
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: cy@FreeBSD.org
          Reporter: john@saltant.com
          Assignee: cy@FreeBSD.org
             Flags: maintainer-feedback?(cy@FreeBSD.org)

Synopsis
=3D=3D=3D=3D=3D=3D=3D=3D

When security/krb5 (-115, in my case) is built with the LDAP option, and th=
en
configured to use a local LDAP server, the krb5kdc daemon fails to start on
boot with "cannot initialize realm EXAMPLE.COM - see log file for details"
because slapd is not yet running.

Expected behavior
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On boot, slapd and kdc both start successfully in that order.

Observed behavior
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On boot, kdc tries to start first and fails, and later slapd starts
successfully. After boot, an attempt to start kdc succeeds.

Reproducible
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Always.

$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* 2>/dev/null | egrep "kdc|slapd"
/etc/rc.d/kdc
/usr/local/etc/rc.d/slapd

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229939-7788>