>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am
28.08.2019 um 15:56 in
Nachricht <F0468E4D7DD097415B5FC5C1(a)[192.168.1.144]>:
‑‑On Wednesday, August 28, 2019 11:02 AM +0200 Ulrich Windl
<Ulrich.Windl(a)rz.xn--uniregensburg-dm6g.de> wrote:
> Hi!
>
> After systemd tearing down one of our LDAP servers I noticed the
> following message when the server was restarted: slapd[10525]: UNKNOWN
> attributeDescription "AUDITCONTEXT" inserted.
>
> The next line logged was:
> slapd[10525]: olcServerID: value #1: SID=0x002 (listener=ldap://...:389)
>
> (the server is that of SLES12 SP4, 2.4.41 from opensuse‑buildservice)
>
> The server is one of three MM servers that all have the same
> configuration and the same version.
>
> The schema knows in olcAttributeTypes (olcSchemaConfig):
> ( 1.3.6.1.4.1.4203.666.11.5.1.30 NAME 'auditContext' DESC 'DN of
> auditContainer' SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE‑VALUE
> NO‑USER‑MODIFICATION USAGE dSAOperation )
>
> What I'l like to know: Is there any thing I could fix in the
> configuration to make the message go away, or is it some software issue
> in slapd?
I've seen this when an attribute is introduced into the cn=config database
that's not part of the built‑in slapd schema. It can be harmless in that
case.
I grepped for the attribute in external schema files, but didn't find it. As I
found it when querying slapd, I conclude that the definition shown above must
be build into slapd.
‑‑Quanah
‑‑
Quanah Gibson‑Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<
http://www.symas.com>