>> Michael Ströder <michael(a)stroeder.com> schrieb am
29.08.2019 um 16:34 in
On 8/29/19 8:32 AM, Ulrich Windl wrote:
>>>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am 28.08.2019 um
> 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:
>>> After systemd tearing down one of our LDAP servers I noticed the
>>> following message when the server was restarted: slapd: UNKNOWN
>>> attributeDescription "AUDITCONTEXT" inserted.
>>> The schema knows in olcAttributeTypes (olcSchemaConfig):
>>> ( 22.214.171.124.4.1.4203.6126.96.36.199.30 NAME 'auditContext' DESC 'DN of
>>> auditContainer' SYNTAX 188.8.131.52.4.1.14184.108.40.206.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
> I grepped for the attribute in external schema files, but didn't find it.
> found it when querying slapd, I conclude that the definition shown above
> be build into slapd.
Attribute type description 'auditContext' and all other schema
definitions for accesslog overlay are defined in C code of
slapo-accesslog. If you don't load slapo-accesslog then you normally
don't see the schema.
I don't know what inconsistent content your cn=config has though.
Still I don't quite understand it: It seems the attribute is also in the
config database (dn: cn=schema,cn=config), so why is it unknown when slapd
starts? It cannot be the reason that the schema is provided by an overlay. That
would apply when starting the first time only, maybe (when the schema database
isn't populated yet by the overlay).