directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: Error: I do not know how to handle NameAndOptionalUID normalization
Date Mon, 19 Mar 2018 16:32:28 GMT
To be more specific :

when the schema partition is initialized, we read all the associated
files. Many of them

For instance, when we read the apacheDnsDomainName ldif file, which is in :

  +-- cn=apachedns
        +-- ou=attributeTypes
               +-- m-oid=

we get that entry :

m-name: apacheDnsSoaMName
m-description: The domain name of the name server that was the primary
source of data for this zone
m-obsolete: FALSE
m-equality: caseIgnoreIA5Match
m-supattributetype: apacheDnsDomainName
entryParentId: bc4ca0cc-66e5-4c8e-8f16-b0d5f77e0ac9
m-singlevalue: TRUE
createTimestamp: 20150708131906.591Z
m-nousermodification: FALSE
m-collective: FALSE
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
entryUUID: bac4890c-08a4-4957-bca3-f441674c2569
creatorsname: uid=admin,ou=system
entryCSN: 20150708131902.875000Z#000001#000#000000

At this piont, we need to process the following attributes and their
values :

m-supattributetype: apacheDnsDomainName

where the apacheDnsDomainName is not present in the SchemaManager,
because the apachedns schema is not enabled. This generates the error
you can see, which is not actually an error, but a problem with a non
existant schema element definition.

Now, the question is : should we make that a warning instead of an
error? (Note that in this very case, we continue to process the schema,
it's a non blocking error).

wdyt ?

Le 18/03/2018 à 19:11, Stefan Seelmann a écrit :
> On 03/18/2018 07:00 PM, Emmanuel Lécharny wrote:
>> Le 18/03/2018 à 17:35, Stefan Seelmann a écrit :
>>> Hi,
>>> the installers-in-docker test jenkins job shows strange errors like
>>> ERROR [] - ERR_04226 I do
>>> not know how to handle NameAndOptionalUID normalization with objects of
>>> class: sambaSID
>>> See
>>> for more of them.
>>> ``$`
>> It throws such an exception when the value is invalid or when we can't
>> find the name's OID.
>> This is a kind of weird. My bet is that it has to do with the schema file.
>> Where is the dockerfile ?
> There is no dockerfile.
> Those tests run different docker containers [1] which then excute bash
> scripts (e.g. [2]) which just install apacheds and interact with it.
> You can just reproduce by running the generated zip/tar.gz archive and
> look into the logs.
> Kind Regards,
> Stefan
> [1]
> [2]

Emmanuel Lecharny

View raw message