[DIRSERVER-2248] The server generates some errors when starting (Schema isues)

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0.AM25
• Fix Version/s: 2.0.0.AM26
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 25/Aug/18 05:50
• Updated: 13/Jun/19 17:18
• Resolved: 13/Jun/19 16:32

Description

When we start the server, we get many erros like :

[23:59:05] ERROR [org.apache.directory.api.ldap.model.entry.Value] - ERR_13725_CANNOT_HANDLE_NAME_AND_OPTIONAL_UID_NORM I do not know how to handle NameAndOptionalUID normalization with objects of class: apacheDnsDomainName

The problem is due to some schema elements can't be properly loaded, due to some missing dependencies. Typically, we are trying to load this entry :

version: 1
dn: m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
m-singlevalue: TRUE
m-obsolete: FALSE
m-description: The domain name of the name server that was the primary source of data for this zone
m-usage: USER_APPLICATIONS
creatorsname: uid=admin,ou=system
m-collective: FALSE
m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
m-supattributetype: apacheDnsDomainName
m-nousermodification: FALSE
m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-name: apacheDnsSoaMName
m-equality: caseIgnoreIA5Match

This AttributeType does have a SUP AttributeType, apacheDnsDomainName, which is not already loaded, as this schema (ApacheDNS) is not enabled, so the Registries does not know about it.

That leaves the resulting Entry with a missing attribute.

The consequence is that we can't anymore modify this entry, thus the associated LDIF file, properly when the server is running.

Issue Links

• is related to: KNOX-1718 Look at ApacheDS LDAP ERROR messages