>> Howard Chu <hyc(a)symas.com> schrieb am 04.09.2019 um
03:40 in Nachricht
Ulrich Windl wrote:
>>>> Michael Ströder <michael(a)stroeder.com> schrieb am 29.08.2019 um
>> On 8/29/19 8:32 AM, Ulrich Windl wrote:
>>>>>> Quanah Gibson-Mount <quanah(a)symas.com> schrieb am
28.08.2019 um 15:56
>>> 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:
>>>>> attributeDescription "AUDITCONTEXT" inserted.
>>>>> The schema knows in olcAttributeTypes (olcSchemaConfig):
>>>>> ( 184.108.40.206.4.1.4203.6220.127.116.11.30 NAME 'auditContext' DESC
>>>>> auditContainer' SYNTAX 18.104.22.168.4.1.1422.214.171.124.12
>>>>> 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
>>>>> in slapd?
>>>> I've seen this when an attribute is introduced into the cn=config
>>>> that's not part of the built‑in slapd schema. It can be harmless in
>>> I grepped for the attribute in external schema files, but didn't find
>>> 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.
> would apply when starting the first time only, maybe (when the schema
> isn't populated yet by the overlay).
The contents of the file corresponding to cn=schema are always ignored, and
runtime contents of the cn=schema entry are always the actual hardcoded
schema in the
slapd process. As such, you should only trust the contents of an ldapsearch
cn=schema,cn=config entry, and always disregard whatever was stored in the
That was unexpected for me. Is there a technical reason for this design? I see
some chicken/egg problem, but for a synced config setup this seems