PaulHorowit created DIRSERVER-2282:
--------------------------------------
Summary: apacheds-2.0.0.AM25 cann't startup after import schema
using Apache Directory Studio
Key: DIRSERVER-2282
URL: https://issues.apache.org/jira/browse/DIRSERVER-2282
Project: Directory ApacheDS
Issue Type: Bug
Components: schema
Affects Versions: 2.0.0.AM25
Reporter: PaulHorowit
apacheds-2.0.0.AM25 cann't startup after import schema using Apache Directory
Studio, the steps are follows:
(1)create self schema through the Apache Directory Studio as the site
[http://directory.apache.org/apacheds/basic-ug/2.3.2-enabling-schema.html] says,
and then export it as a ldif file and the file name is sevenSeas.ldif;
(2) import the ldif file above into Apacheds server, it is ok. I can see the
ou=sevenSeas
entry in the Apache Directory Studio.
(3) stop the ds server and then restart it, the problem occurs: the ds server
can not start.
following is the stack:
[19:40:55] ERROR [org.apache.directory.api.ldap.model.entry.DefaultAttribute] -
ERR_13215_VALUE_EXPECT_STRING The value is expected to be a String[19:40:55]
ERROR [org.apache.directory.api.ldap.model.entry.DefaultAttribute] -
ERR_13215_VALUE_EXPECT_STRING The value is expected to be a String[19:40:58]
ERROR [org.apache.directory.api.ldap.schema.loader.LdifSchemaLoader] -
ERR_16009_LDIF_LOAD_FAIL Failed to load schema LDIF file
cn=sevenseas.ldiforg.apache.directory.api.ldap.model.exception.LdapInvalidAttributeValueException:
ERR_13215_VALUE_EXPECT_STRING The value is expected to be a String at
org.apache.directory.api.ldap.model.entry.DefaultAttribute.getString(DefaultAttribute.java:517)
at
org.apache.directory.api.ldap.model.schema.registries.AbstractSchemaLoader.getSchema(AbstractSchemaLoader.java:171)
at
org.apache.directory.api.ldap.schema.loader.LdifSchemaLoader.initializeSchemas(LdifSchemaLoader.java:141)
at
org.apache.directory.api.ldap.schema.loader.LdifSchemaLoader.<init>(LdifSchemaLoader.java:111)
at
org.apache.directory.server.ApacheDsService.initSchemaManager(ApacheDsService.java:288)
at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:183)
at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:152)
at
org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.start(ApacheDsTanukiWrapper.java:175)
at
org.tanukisoftware.wrapper.WrapperManager.startInner(WrapperManager.java:2831)
at
org.tanukisoftware.wrapper.WrapperManager.privilegedStart(WrapperManager.java:1815)
at
org.tanukisoftware.wrapper.WrapperManager.access$2400(WrapperManager.java:103)
at org.tanukisoftware.wrapper.WrapperManager$5.run(WrapperManager.java:1743) at
java.security.AccessController.doPrivileged(Native Method) at
org.tanukisoftware.wrapper.WrapperManager.start(WrapperManager.java:1740) at
org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.main(ApacheDsTanukiWrapper.java:57)
==============
the cause is that, after import the sevenSeas.ldif, ds serve store it as
follow, the creatorsName attribute is stored by base64 format.
But why does it happen?
dn: cn=sevenSeas, ou=schema
entryCSN: 20190821114004.660000Z#000000#001#000000
cn: sevenSeas
objectclass: top
objectclass: metaSchema
createTimestamp: 20190821114004.662Z
m-dependencies: core
m-dependencies: system
creatorsName:: MC45LjIzNDIuMTkyMDAzMDAuMTAwLjEuMT0gYWRtaW4gLDIuNS40LjExPSBzeXN0Z
W0g
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
