You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Brandon Gould (JIRA)" <ji...@apache.org> on 2013/06/20 14:44:20 UTC
[jira] [Commented] (DIRSERVER-1647) Unable to enable/modify/delete
schema
[ https://issues.apache.org/jira/browse/DIRSERVER-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689195#comment-13689195 ]
Brandon Gould commented on DIRSERVER-1647:
------------------------------------------
Hooh boy! Looks like I'm dragging up an old bug...
I have reproduced this bug, in a rather annoying fashion.
Like this user, I also accidentally specified an objectClass of "Structural" and intended to modify it to Auxilliary, but I get a similar error:
--- snip ---
# Generated by Apache Directory Studio on June 20, 2013 7:41:39 AM
# SCHEMA "CREWCORP"
#!RESULT OK
#!CONNECTION ldap://ccserver:10389
#!DATE 2013-06-20T08:34:20.383
dn: cn=CrewCorp, ou=schema
objectclass: metaSchema
objectclass: top
cn: CrewCorp
m-dependencies: system
#!RESULT ERROR
#!CONNECTION ldap://ccserver:10389
#!DATE 2013-06-20T08:34:20.388
#!ERROR [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType : MODIFY_REQUEST Message ID : 110 Modify Request Object : 'ou=attributeTypes,cn=CrewCorp,ou=schema' Modification[0] Operation : replace Modification objectclass: organizationalUnit objectclass: top Modification[1] Operation : replace Modification ou: attributetypes org.apache.directory.api.ldap.model.message.ModifyRequestImpl@1cd609ee: null]
dn: ou=attributeTypes, cn=CrewCorp, ou=schema
objectclass: organizationalUnit
objectclass: top
ou: attributetypes
--- snip ---
I don't get any other indication that there's a problem; no specific error message, just UNWILLING_TO_PERFORM.
A quick google search of this has given me no luck. In those cases, there's a specific message at least giving some direction to resolve the problem, but the only forseeable way I can see to resolve this is to completely blow away the install and reinstall, causing some significant downtime for my development team
> Unable to enable/modify/delete schema
> -------------------------------------
>
> Key: DIRSERVER-1647
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1647
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: schema
> Affects Versions: 2.0.0-M2
> Reporter: Aaron J Angel
> Fix For: 2.0.0-RC1
>
>
> Attempting to edit, enable, or delete a disabled schema fails with the following:
> Error while executing LDIF
> - [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType : MODIFY_REQUES
> javax.naming.OperationNotSupportedException: [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType : MODIFY_REQUEST
> Message ID : 22
> Modify Request
> Object : 'cn=nis,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> m-disabled: FALSE
> org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@b9bf625a: ERR_11001 Cannot load the unknown schema nis]; remaining name 'cn=nis,ou=schema'
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3105)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2978)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2785)
> at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1468)
> at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:273)
> at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:190)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$2.run(JNDIConnectionWrapper.java:454)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.runAndMonitor(JNDIConnectionWrapper.java:1272)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.checkConnectionAndRunAndMonitor(JNDIConnectionWrapper.java:1203)
> at org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.modifyEntry(JNDIConnectionWrapper.java:502)
> at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdifRecord(ImportLdifJob.java:507)
> at org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifJob.importLdif(ImportLdifJob.java:267)
> at org.apache.directory.studio.ldapbrowser.core.jobs.ExecuteLdifRunnable.run(ExecuteLdifRunnable.java:143)
> at org.apache.directory.studio.ldapbrowser.core.jobs.UpdateEntryRunnable.run(UpdateEntryRunnable.java:58)
> at org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:113)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType : MODIFY_REQUEST
> Message ID : 22
> Modify Request
> Object : 'cn=nis,ou=schema'
> Modification[0]
> Operation : replace
> Modification
> m-disabled: FALSE
> org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@b9bf625a: ERR_11001 Cannot load the unknown schema nis]
> Upon installation, the nis schema was enabled by removing the m-disabled attribute from the entry. Upon discovering that posixGroup was STRUCTURAL, I disabled the nis schema. Now, when trying to modify the objectClass entry for posixGroup, or even when attempting to delete the nis schema entirely to start over, the above error message is presented in Directory Studio.
> For my application, I need to edit or replace the default nis schema with one compatible with rfc2307bis (e.g., posixGroup must be AUXILIARY, not STRUCTURAL).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira